Repository navigation
v0.0.0
[0.0.0] - 2026-11-10
Added
access, the plugin option every OpenCode plugin of this family has:"all"(the default),"ask-changes"and
"read-only". It generates the default permission block from the tool classes, and/metaview-statusshows it in the
Accessrow and in the status RPC'saccessfield.assets/icon-128.pngandassets/icon-256.png, withopencode.iconsandopencode.vendorinpackage.json, and
scripts/check-icons.mjs, the family icon contract's check.
Changed
-
Each Metaview skill's first line says how to sign in when the tools are absent:
/connect, or on Jellyjelly_connection_request. -
Every Metaview tool is allowed by default. The plugin's generated block allows every known tool and the
metaview_*namespace, so a tool Metaview adds later runs without a prompt too. That includes the three Metaview
marks destructive: application review decisions, candidate outreach and feedback to the Metaview team. Restrict them
withaccess, with an agent's own rules, or with a rule per tool; the README's Permissions section and SECURITY say
what an all-allow default means here. -
update_screen_outreachis classedsend, because it emails candidates and can reject them at their deadline; it was
classedwrite. -
docs/scripting.mdis the family's scripting contract: the strict envelope, the location section and its unload note,
the result wording, and the refusal table, with an example-parsing test that fails when a doc example names a method
that does not exist, omits the location header, or uses a field the tool does not take. -
PLUGIN_CODESandRPC_CODESare the one typed code table, and a test fails when a code raised insrcis in
neither or when the docs' tables drift from it. -
The CI has an
actionlintjob, andnpm run checkrunsactionlintand the icon check. -
The docs' tested-host sentences are checked against
TESTED_HOSTS, and the README prints the default block in full. -
tools RPC v2.1: every known tool is scriptable.
metaview.workspace.toolsnow has one
method per known tool, by exact name and with its class (read, send, write or destructive), not only the reads. The
rule is resolved before dispatch: only anallowruns (the default block allows every tool), and anaskis refused
with no prompt and no tool call.
describereports each method's class, a session's permission and any live tool the table does not classify. A saved
"Always allow" approval no longer authorizes an ad-hoc script: a script's grant is a rule in the agent's or the
session's config, or a Jobsjobs_run_scriptrun session.opencode apicallers must send
-H "x-opencode-directory:$PWD". The account read still records the workspace, role and plan throughshapeResult.
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
accessoption decides whether it runs, asks or is denied, and/metaview-statuscounts 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 and 2.2.6, and runs on macOS or Linux. A later 2.2 release starts and is reported as untested.
- Updates are not automatic for a Git install, and
opencode plugin updateandopencode plugin checkdo not work on one: to move to a newer release, remove the old entry and add the new tag.