You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
[0.0.4] - 2026-11-15
Added
For jelly:jelly.admin, the step jelly shows on the plugin's review after "Before anyone signs in, your admin
needs to": "turn on MCP integration in Metaview's Workspace settings, and MCP for non-admins so members can sign in
too".
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.