Skip to content

v0.0.0

Choose a tag to compare

@github-actions github-actions released this 11 Nov 13:18
· 35 commits to master since this release
v0.0.0
23209fd

[0.0.0] - 2026-11-10

Added

  • The jobs skill is registered with OpenCode, so a question about scheduled jobs loads it.
  • The Jelly declaration has an access setting (default all), so Jelly can show and change the access option.
  • The script action: a job can run a confined program instead of a model prompt. Its uses manifest names the tools
    it can call, /jobs-approve re-approves it, and the run record keeps what each call did, never a payload.
  • The script runtime: QuickJS compiled to WebAssembly (MIT, bundled as dist/quickjs.wasm and in NOTICE), one VM per
    run, with no direct filesystem, network, process, environment or timers; 100 calls, 64 MB of VM memory and 64 KB of
    output by default, the job's timeout for wall time, and the kill switch mid-call.
  • Declared files: a script can read a snapshot and buffer writes to named files. Writes commit after a successful run,
    with path checks, conflict detection and rollback on failure. scriptFilesRoots permits paths outside the job's
    directory; files outside the project also need the agent's external_directory permission.
  • The access option: all allows every Jobs tool by default, ask-changes asks for changes and read-only denies
    them. The namespace rule covers tools added later; explicit later agent rules still win.
  • Script approval follows the manifest's worst class and includes declared file writes: all approves automatically,
    ask-changes approves all-read scripts automatically and asks for changes, and read-only denies changes. The digest
    binds the source, sorted manifest, file declarations and resolved paths. Eligible file jobs are approved at load.
    Every run re-checks approval, permissions and access; a changed or revoked approval can skip the slot.
  • jobs_approve, /jobs-approve, and jobs_run_script (one run, nothing kept).
  • A status row for script jobs, script approval facts in the job list, and per-call facts in run records.

Changed

  • The tools RPC is v2: every known tool is a method with a class, the rule is resolved before dispatch (an ask is
    refused with no prompt), shapeInput runs beside shapeResult, and describe reports classes and a session's
    permission. Jobs exposes all fourteen tools as methods; a run session still denies the state changes.
  • An ad-hoc script no longer inherits a saved "Always allow": a script's permission is a config rule or a Jobs approval.
    This is the one deliberate v2 break.
  • ctx.agent.get is called without a location, where the job runs in the leader's own directory (a location passed back
    could fail for a project-level plugin on 2.2.4).

Known limits

  • Runs happen only while OpenCode runs. Nothing runs while OpenCode is closed. A slot due in that time runs when OpenCode next starts if it is no later than the job's maxLate (one hour by default); a later slot is skipped as expired.
  • Scripts have fixed limits by default. A script runs in a QuickJS VM with 64 MB of memory, 100 tool calls and 64 KB of output. A job can raise each one up to the maximum in docs/scripting.md.
  • A changed declared file is re-approved under all. The run record names the script's digest, but not yet the declared-file set (its paths, modes and caps), so the record alone does not show which file declaration a run used.
  • Declared files are read on the host. Each one is read up to its size limit, before the VM starts, and that memory is outside memoryMb.
  • A restore can fail. When a file cannot be put back after a failed commit, its run records rollback_failed and the error names the kept original, which a person must restore by hand.
  • An agent without the default rules still runs its jobs. Status warns with JOBS_AGENT_UNGUARDED and the block to paste; nothing blocks the run.
  • 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.