Repository navigation
Releases
v0.0.7
[0.0.7] - 2026-11-20
Changed
events_listis a tools RPC method only, likeprobe, and is no longer a tool in themetaviewnamespace or a
jelly.toolsentry. Memory still collects throughmetaview.workspace.tools/events_list. The default rule
metaview_events_listis unchanged.scripts/check-copies.mjsno longer names a copiedsrc/host/tools-rpc.ts: the tools RPC is the source contract's
module, bundled intodist/index.js.- The
@we-the-rebel-alliance/source-contractdev dependency is v0.3.0 (it was v0.2.0):package.jsonand the
lockfile, and the conformance test states why each v0.3 check that does not apply to this source is skipped. The
plugin sends no new key, and its pages, methods and descriptor are unchanged.
Known limits
- The conversations source lists by start time. Metaview's search orders and filters conversations by their start
only, with no time Metaview received them, and an uploaded recording is listed at the start its uploader gave.- Late arrivals: one that appears after the source read past its start (an upload, a conversation shared with you
later) is listed once if it started within 7 days of the cursor; one later than that is not listed, and no gap says so. - Busy accounts: the cursor de-duplicates about 200 conversations (about 28 a day over the 7 days). With more,
the lookback is shorter, and awindow-truncatedgap says so once per shortening. A de-dup key is 25 bits of a
hash of the id, so about 1 late arrival in 168,000 can be taken for one already listed and not listed. - Retention: the source vouches for the last 30 days, since Metaview's retention is your organization's own
setting and no tool names it. A workspace retention shorter than 30 days can delete recordings before the source
reads them, with no gap. - Deleted or no longer yours: one deleted, or that you lose access to (unshared, or hidden by a role change),
before a read reaches it is not listed and is not a gap; one already listed is not retracted.
- Late arrivals: one that appears after the source read past its start (an upload, a conversation shared with you
- 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, 2.2.6, 2.2.7, 2.3.0, 2.3.1 and 2.3.2, 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
jellysettings 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 updateandopencode plugin checkdo not work on one: to move to a newer release, remove the old entry and add the new tag.
v0.0.6
[0.0.6] - 2026-11-18
Changed
- Tested on OpenCode 2.3.1 and 2.3.2, so
TESTED_HOSTSnow holds 2.2.3, 2.2.4, 2.2.5, 2.2.6, 2.2.7, 2.3.0, 2.3.1 and
2.3.2. The supported range is unchanged (>=2.2.3 <2.4.0). The host and pack stages, CI and the release's install
check run on every one; the plugin is tested on 2.2.3, 2.2.4, 2.2.5, 2.2.6, 2.2.7, 2.3.0, 2.3.1 and 2.3.2. They need
nothing else from this plugin: between 2.3.0 and 2.3.2 the only API changes are thatexperimental.generate
excludes video jobs and a newcodemodesession event kind.
Known limits
- The conversations source lists by start time. Metaview's search orders and filters conversations by their start
only, with no time Metaview received them, and an uploaded recording is listed at the start its uploader gave.- Late arrivals: one that appears after the source read past its start (an upload, a conversation shared with you
later) is listed once if it started within 7 days of the cursor; one later than that is not listed, and no gap says so. - Busy accounts: the cursor de-duplicates about 200 conversations (about 28 a day over the 7 days). With more,
the lookback is shorter, and awindow-truncatedgap says so once per shortening. A de-dup key is 25 bits of a
hash of the id, so about 1 late arrival in 168,000 can be taken for one already listed and not listed. - Retention: the source vouches for the last 30 days, since Metaview's retention is your organization's own
setting and no tool names it. A workspace retention shorter than 30 days can delete recordings before the source
reads them, with no gap. - Deleted or no longer yours: one deleted, or that you lose access to (unshared, or hidden by a role change),
before a read reaches it is not listed and is not a gap; one already listed is not retracted.
- Late arrivals: one that appears after the source read past its start (an upload, a conversation shared with you
- 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, 2.2.6, 2.2.7, 2.3.0, 2.3.1 and 2.3.2, 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
jellysettings 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 updateandopencode plugin checkdo not work on one: to move to a newer release, remove the old entry and add the new tag.
v0.0.5
[0.0.5] - 2026-11-17
Added
- A shared-data source,
metaview.conversations(#21):
package.jsondeclares source-contractsources(contract version 1), so Memory, Artifacts and other consumers can
read Metaview's recorded conversations as events through the shared contract.events_list(a tool in themetaview
namespace and a tools RPC method) lists them oldest first, once they started 3 hours ago, from
search_conversations, with a cursor bound to the plugin, the source and the account;probenames the signed-in
account fromget_user_context. Metaview's retention is each organization's own setting, so the source vouches for
the last 30 days: an older cursor orsinceanswers agaponce per read and reads on from the window's edge. A
conversation Metaview adds behind the cursor within 7 days of it, such as an upload listed at its call's start, is
listed once, by a 25-bit key of its id that the cursor keeps in a Golomb-Rice coded set (about 200 fit; with more,
awindow-truncatedgap says once per shortening that the lookback is shorter; a late arrival is taken for a listed
one about once in 168,000). A burst sharing one start is walked by id; an answer the plugin cannot read
fails the call and holds the cursor; a title's email addresses and phone numbers are masked, and an actor's id is a
Metaview participant id or nothing. Each event carries metadata only: the id, start, title, link, conversation type, and
the candidates and interviewers by name. No transcript, note, score, feedback or contact detail, andtextis
always empty. Both are reads, allowed by the default rules like Metaview's reads;jelly.toolsdeclares
metaview.events_list.npm run conformanceruns the contract's conformance kit on fixtures and writes
reports/conformance-report.json, which a release attaches.
Changed
- The tools RPC is the source contract's
tools-rpcmodule, bundled intodist/index.js, in place of the plugin's own
copy of the shared module. Its methods, classes, codes and next steps are unchanged.
Known limits
- The conversations source lists by start time. Metaview's search orders and filters conversations by their start
only, with no time Metaview received them, and an uploaded recording is listed at the start its uploader gave.- Late arrivals: one that appears after the source read past its start (an upload, a conversation shared with you
later) is listed once if it started within 7 days of the cursor; one later than that is not listed, and no gap says so. - Busy accounts: the cursor de-duplicates about 200 conversations (about 28 a day over the 7 days). With more,
the lookback is shorter, and awindow-truncatedgap says so once per shortening. A de-dup key is 25 bits of a
hash of the id, so about 1 late arrival in 168,000 can be taken for one already listed and not listed. - Retention: the source vouches for the last 30 days, since Metaview's retention is your organization's own
setting and no tool names it. A workspace retention shorter than 30 days can delete recordings before the source
reads them, with no gap. - Deleted or no longer yours: one deleted, or that you lose access to (unshared, or hidden by a role change),
before a read reaches it is not listed and is not a gap; one already listed is not retracted.
- Late arrivals: one that appears after the source read past its start (an upload, a conversation shared with you
- 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, 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
jellysettings 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 updateandopencode plugin checkdo not work on one: to move to a newer release, remove the old entry and add the new tag.
v0.0.4
[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
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, 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
jellysettings 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 updateandopencode plugin checkdo not work on one: to move to a newer release, remove the old entry and add the new tag.
v0.0.3
[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; theHOST_UNTESTEDexample 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
subagenttool 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 newsession.forkhook. - 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.markistrue, and the README says Metaview is a trademark of Metaview Labs Inc.
Fixed
- Status,
/metaview-statusand the/metaviewdialog 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
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, 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
jellysettings 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 updateandopencode plugin checkdo not work on one: to move to a newer release, remove the old entry and add the new tag.
v0.0.2
[0.0.2] - 2026-11-14
Added
test/fixtures/live-tools.json, Metaview's tool list for a signed-in user, captured live on 14 November 2026, and a
test that fails when the declaration and that list disagree. The declaration already matches it: 68 tools, each
readOnlyas Metaview'sreadOnlyHintsays, eachallow.
Changed
package.jsonis"private": true, so nothing can be published to npm; an install from the release tag is
unaffected. It is kept in its canonical form, which the kit tests check innpm run check.- The release kit's plan, build and release scripts check the package's
"private": trueand canonical form, and a
buildscript is added topackage.json.
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.
- Jelly's settings need a recent Jelly. The
jellysettings 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 updateandopencode plugin checkdo not work on one: to move to a newer release, remove the old entry and add the new tag.
v0.0.1
[0.0.1] - 2026-11-13
Added
- The
jellysettings declare their choices:accessoffers Jelly's three (Allowed, Ask before changes, Read only), so
Jelly draws it as a choice instead of free text. A test reads the settings with Jelly's setting rules and checks that
the options parser takes every declared value and refuses one outside the set (needs a jelly that includes
app#1301).
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.
- Jelly's settings need a recent Jelly. The
jellysettings 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 updateandopencode plugin checkdo not work on one: to move to a newer release, remove the old entry and add the new tag.
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.