Skip to content

v0.0.1

Choose a tag to compare

@github-actions github-actions released this 14 Nov 10:25
· 43 commits to master since this release
455ef1c

[0.0.1] - 2026-11-13

Added

  • The jelly settings declare their choices: access offers 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 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 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 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.