Skip to content

v0.0.5

Choose a tag to compare

@github-actions github-actions released this 17 Nov 19:50
· 15 commits to master since this release
5631f6c

[0.0.5] - 2026-11-17

Added

  • A shared-data source, metaview.conversations (#21):
    package.json declares source-contract sources (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 the metaview
    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; probe names the signed-in
    account from get_user_context. Metaview's retention is each organization's own setting, so the source vouches for
    the last 30 days: an older cursor or since answers a gap once 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,
    a window-truncated gap 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, and text is
    always empty. Both are reads, allowed by the default rules like Metaview's reads; jelly.tools declares
    metaview.events_list. npm run conformance runs 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-rpc module, bundled into dist/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 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 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.