Repository navigation
v0.2.0-beta.3
Pre-releaseThe first beta with harness mode: docket harness run executes one governed agent turn for an
external plan-of-record and reports it as a versioned NDJSON contract. It also carries the changes
below since v0.2.0-beta.2, including one exit-status change: a pod dispatch or pipeline run whose
task fails now exits 1.
Added
docket harness runanddocket harness status— a non-interactive entry point that runs
one agent for one turn, to completion, in a workspace andDOCKET_HOMEthe caller supplies.
stdout carries newline-delimited events and one versioned result and nothing else; every log goes
to stderr. The wire contract's JSON schema is published atdocs/contracts/harness-v1/schema.json,
generated from the models and pinned byte-for-byte by a test, with NDJSON fixtures for the ok,
blocked, cancelled and refused shapes attests/fixtures/harness-contract/v1/. Exit status is 0
for a completed turn, 1 for one that ran and ended badly, and 2 for a refusal before any turn
began — the one deliberate exception to docket's otherwise
flat return convention, because a program parsing stdout cannot read a printed message.- A synchronous trace subscriber seam.
core/trace.py::subscribehands each sink the exact
record about to be appended, after redaction and before the write. With no subscribers the path
is byte-identical.
Changed
- A tool call that needs approval can now be refused immediately instead of waited on. A
caller with nobody to ask gets a typed, terminalapproval_unavailableresult naming the tool,
the call and the policy that stopped it, in milliseconds rather than after a two-minute timeout
repeated up to three times. The default remains unchanged: an ordinary caller still waits. - Cancellation now reaches an in-flight
bashcommand.docket runs cancelterminalizes a run
whose hop is sitting inside a long-running shell command, killing the process group the way a
timeout already did. Every other tool handler keeps the previous rule that an already-running
handler may finish. docket gates enable/disablehelp text now says what the commands do. They record an
approval-routing posture thatdocket gates statusanddocket doctorreport; nothing on the
live path reads it, and everyaskverdict is answered the same way by the CLI, HTTP, MCP and
Telegram channels regardless of it. The previous text said the flag changed where a verdict was
delivered.docket maintain <id> sessionsno longer says sessions are never compacted. They compact on
the turn path once history exceeds the role budget.docket pod <project> dispatchanddocket pipeline runexit 1 when a task fails. The exit
status now matches the run record: a dispatch whose run endsfailedexits 1, so
docket pod x dispatch && ...no longer continues past a failed task.blockedand
waiting_approvalare expected pauses and still exit 0.- The release build pins its backend to
hatchling==1.32.0. hatchling 1.32.1 writes the
unnormalized version (0.2.0-beta.2) into wheel metadata, where earlier releases carried the
normalized0.2.0b2.
Fixed
- Pod output no longer drops task ids and roles, and model text can no longer crash it. Output
fromdocket pod,docket trace <session>anddocket models presetpassed data through
terminal markup: every[<task-id>]and[<role>]was silently erased, and a task description
or model reply containing a closing tag such as[/bold]aborted the command with a markup
error (fordelegate, after the task was already queued). All of it now prints literally. - The
localpreset's note names the real command,docket models provider add <name> <base-url>; it omittedadd, and its bracketed placeholders were erased on screen.
Removed
- The
security.gatesEnabledkey infleet.jsonis no longer read or written. Nothing had ever
read it. An existingfleet.jsonthat carries the key still loads.
Notes
-
docket harness statuson a finished run reports the outcome but cannot recover the served model
or the blocked rule detail, which existed only in the turn's in-memory result. -
The development history — every closed wave and phase section of
TODO.mdandROADMAP.md,
the roadmap decision changelog, and superseded coordinator handoffs — is archived verbatim under
docs/cycles-ended/ with a SHA-256 manifest
(scripts/maint/split_board.py check). This file remains the user-facing release changelog.
Install
# Homebrew (macOS/Linux)
brew tap yielab/docket-cli https://github.com/yielab/docket
brew install docket-cli
# Or the version-pinned installer, which verifies the tarball's SHA-256 before extracting
curl -fsSL https://raw.githubusercontent.com/yielab/docket/v0.2.0-beta.3/install.sh \
| DOCKET_VERSION=0.2.0-beta.3 bashVerify
Every asset is listed in SHA256SUMS, and the wheel, the sdist, the installer tarball, SHA256SUMS
and the SPDX SBOM carry a GitHub build-provenance attestation:
sha256sum --check SHA256SUMS
gh attestation verify docket-0.2.0b3-py3-none-any.whl -R yielab/docketdocket is beta software. Expect breaking changes between beta releases and verify consequential
outcomes yourself. Cost figures are token-based estimates, not billed spend.
Full changelog: v0.2.0-beta.2...v0.2.0-beta.3