[BillyOutlast]

Note

Original Pull Request: awesome-opencode/awesome-opencode#429
Original Author: @iamironz
Submitted At: 2026-06-13T12:54:01Z
Original Branch: docs/add-opencode-sessions-explorer

---

Submission Type

• Plugin
• Project
• Theme
• Agent
• Resource

Details

Name: OpenCode Sessions Explorer
Repository: https://github.com/iamironz/opencode-sessions-explorer
Tagline: Search, recall, grep, and cost-analyze every past OpenCode session

Exposes the local OpenCode SQLite session database as 18 LLM-callable tools for session recall, full-text search, grep, cost/usage analysis, tool-failure analysis, and session unarchiving. Published on npm as opencode-sessions-explorer@0.1.2 with provenance.

Not to be confused with opencode-sessions (a different, simpler package by a different author).

Checklist

• Relevant to OpenCode
• Repository is public and accessible
• Actively maintained
• Not a duplicate
• YAML file in correct folder (data/plugins/)
• Filename is kebab-case (opencode-sessions-explorer.yaml)

Summary by Sourcery

New Features:

• Add the OpenCode Sessions Explorer plugin to the plugin catalog for session search, recall, cost analysis, and related tooling.

[sourcery-ai]

Sorry @BillyOutlast, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 23 hours and 23 minutes by commenting @sourcery-ai review. Upgrade to get a review now.

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR registers OpenCode Sessions Explorer in the plugin catalog by adding a four-field YAML entry that links to its repository and describes its session search, recall, cost analysis, tool-failure analysis, and unarchiving capabilities.

File-Level Changes

Change	Details	Files
Adds a new plugin entry for OpenCode Sessions Explorer to the plugins catalog.	Creates the kebab-case YAML metadata file in the plugins data directory. Records the plugin name, public repository, descriptive tagline, and capabilities. Documents its 18 LLM-callable tools for SQLite-backed session search, recall, analysis, and unarchiving.	data/plugins/opencode-sessions-explorer.yaml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: a7f264bb-15ca-4ffa-a540-2fe94b8ed24f

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[BillyOutlast]

Thank you for the submission! The concept fits the catalog, but the implementation targets the legacy OpenCode V1 plugin API (OpenCode Sessions Explorer (@opencode-ai/plugin)) with no Plugin.define/stable id and no @opencode/plugin dependency, so it will not execute in OpenCode V2. Please migrate to @opencode/plugin with Plugin.define({ id: "...", async setup(ctx) {...} }), modern ctx domain objects, and current install docs (no V1 plugin config array). Once V2-compatible, this is a strong approve candidate.

[BillyOutlast]

@iamironz thanks for submitting this to awesome-opencode (originally awesome-opencode/awesome-opencode#429). This PR mirrors it in the actively maintained Heretek-AI fork.

It is on hold because the plugin targets the legacy V1 plugin API. The catalog only accepts new plugins built for OpenCode V2.

What the check found:

• data/plugins/opencode-sessions-explorer.yaml: package.json: @opencode-ai/plugin@1.18.16, @opencode-ai/plugin@>=1.15.0; source (45 files): @opencode-ai/plugin

To migrate:

1. Depend on @opencode/plugin instead of @opencode-ai/plugin 1.x.
2. Export Plugin.define({ id: "your-plugin", async setup(ctx) { … } }). Keeping the V1 export alongside it for dual support is fine.
3. Move hooks to the ctx domain APIs (ctx.event, ctx.session, ctx.storage, …).

You don't need to touch this PR. A bot re-checks the repository every night; once it detects V2 it unblocks this PR and pings you. If it is still on V1 on 2026-12-16 (60 days), the PR is closed, and you can resubmit any time through the Add an entry form.

_{Catalog policy}

[github-actions]

@iamironz the nightly check now detects OpenCode V2 support. Thank you for migrating!

• data/plugins/opencode-sessions-explorer.yaml: v2 (package.json: @opencode/plugin)

The entry was updated with kind, topics and compat so it matches the current schema.

A few metadata items still need fixing; see the checks on this PR.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sourcery-ai]

Sourcery assessment

Approved.