Skip to content

v0.0.3

Choose a tag to compare

@github-actions github-actions released this 15 Nov 15:46
· 27 commits to master since this release
bde6b80

[0.0.3] - 2026-11-15

Changed

  • OpenCode 2.3 is admitted: the host range is >=2.2.3 <2.4.0 (it was >=2.2.3 <2.3.0), tested on 2.2.3, 2.2.4, 2.2.5, 2.2.6, 2.2.7 and 2.3.0.
    The host and pack stages, CI and the release's install check run every one of them. A later 2.2 or 2.3 release
    starts and status calls it untested; the HOST_UNTESTED example host is now 2.4.0.
  • Apart from the status fix below, OpenCode 2.3 needs nothing else from this plugin. It does not call the subagent tool or read
    session.tool.failed; Metaview's tools are Metaview's MCP tools, which OpenCode runs and stops itself when the person presses Stop; and it has no use
    for the new session.fork hook.
  • The icon is now Metaview's own mark, Metaview's six-tile symbol in white on a black circle, as in Metaview's own app icon, in place of the family's drawn mark; opencode.vendor.mark is true, and the README says Metaview is a trademark of Metaview Labs Inc.

Fixed

  • Status, /metaview-status and the /metaview dialog read the server's source and the default rules' outcome after listing
    the servers and agents. OpenCode records them only when something reads that state, so right after start-up a status
    read could miss them.

Known limits

  • Some changes reach people. A screening or sequence message, an application-review decision that can reject a candidate and sync to your ATS, and feedback to the Metaview team (a hiring decision can email the candidate) all reach people or systems outside OpenCode. At the default access, an agent can make them without a prompt.
  • Metaview's server decides the tools. The plugin classifies the tools it knows. A tool Metaview adds later is not classed by the plugin: the access option decides whether it runs, asks or is denied, and /metaview-status counts it as unknown.
  • Role and plan limits. What you can read follows your Metaview role, and reports, AI fields and full transcripts may need a paid plan. The plugin does not change either.
  • No retries. The plugin does not retry a failed call. The error names the next step.
  • Hosts and platforms. The plugin is tested on 2.2.3, 2.2.4, 2.2.5, 2.2.6, 2.2.7 and 2.3.0, and runs on macOS or Linux. A later 2.2 or 2.3 release starts and is reported as untested.
  • Jelly's settings need a recent Jelly. The jelly settings declare their choices, which a Jelly without app#1301
    does not read: it refuses the plugin's declaration.
  • Updates are not automatic for a Git install, and opencode plugin update and opencode plugin check do not work on one: to move to a newer release, remove the old entry and add the new tag.