Skip to content

v0.0.7

Latest

Choose a tag to compare

@github-actions github-actions released this 20 Nov 13:35
· 6 commits to master since this release
2f0678d

[0.0.7] - 2026-11-20

Changed

  • events_list is a tools RPC method only, like probe, and is no longer a tool in the metaview namespace or a
    jelly.tools entry. Memory still collects through metaview.workspace.tools/events_list. The default rule
    metaview_events_list is unchanged.
  • scripts/check-copies.mjs no longer names a copied src/host/tools-rpc.ts: the tools RPC is the source contract's
    module, bundled into dist/index.js.
  • The @we-the-rebel-alliance/source-contract dev dependency is v0.3.0 (it was v0.2.0): package.json and 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 a window-truncated gap 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.
  • 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, 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 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.