Skip to content

v0.9.0

Choose a tag to compare

@github-actions github-actions released this 22 Jul 06:14

lever 0.9.0 — fixes + QOL sweep

Prebuilt binaries are attached below (darwin/linux × amd64/arm64) — no go install needed. A Go toolchain is still required at runtime (Scion is compiled at apply time).

Added

  • Configurable Lima guest disk (disk:, default 24GiB) — the guest disk was a hardcoded 100GiB sparse file that could wedge a constrained host. (#14)
  • lever doctor reports the agent image's baked Claude Code version, read from an image label — no container run. (#6)
  • Per-tool supervisor logs — each supervised tool writes its own .lever-state/tool-logs/<tool>.log, plus logrotate guidance. (#10)
  • lever worker purge <name> — host-side deletion of a worker's scion record + staged bootstrap so it can be redispatched fresh. Never touches the worker's workspace; requires --force. (#7)
  • Prebuilt release binaries via GoReleaser, wired to a tag-triggered workflow. (#1)

Fixed

  • A supervised tool command that doesn't resolve on the supervisor PATH (or is a directory / non-executable) is now rejected loudly at config-load instead of failing opaquely at spawn; lever doctor now probes every tool backend. (#9)
  • Broker denials on /msg/send, /msg/list, /request now return the specific policy reason instead of a bare forbidden (scion-runtime errors stay opaque); the CLI surfaces it. (#4a)
  • Worker start/resume now verifies the worker is actually live (running phase + live container) before reporting success. (#7)
  • lever stop's scion-suspend failure is surfaced as a warning instead of silently swallowed, so the Lima conversation-loss gap is diagnosable. (#3)

Changed

  • Behavior change: dispatching an existing worker with a new task now returns HTTP 409 instead of silently resuming its original creation-time task. Resume with lever-manager agent resume, or lever worker purge <name> to start fresh with a new task. (#7)

Full changelog: CHANGELOG.md.