v0.8.5

What's Changed

• refactor(sandbox): drive sandbox context note from unified resolver (#90)

The sandbox context note that tells sessions their bash tool calls run inside a container is now sourced from the single shared SandboxContext in src/sandbox/context.ts instead of being appended to loop prompt bodies. The unified sandbox message hook (src/hooks/sandbox-message.ts) injects it into every session whose tool calls are routed into a container — sandbox loops, their Task-tool subagents, and sessions with the host sandbox toggled on — so subagents that never see a loop prompt body still receive the container context from one point of truth.

v0.8.4

What's Changed

• feat(agents): add read-only impact-reviewer subagent for audit consolidation checks

The loop auditor now launches an impact-reviewer subagent during section and final audits to scan the scoped change set for duplication of existing helpers, parallel implementations, missed callers of changed shared code, and dead code. It is read-only (no edit, write, review-write, plan-adjust, or task tools), hidden from the agent picker, and returns a text report of blocking/advisory findings that the auditor verifies before writing them as review findings.

v0.8.3

What's Changed

• feat(sandbox): make Browser Control an opt-in sandbox image feature (#89)

Chromium and Browser Control are now an opt-in feature of the bundled sandbox image instead of being baked into every build. The Dockerfile gains an INSTALL_BROWSER_CONTROL build arg, the plugin exposes sandbox.imageFeatures.browserControl config that is threaded through the build dialog and missing-template hints, and the docs describe the opt-in build/load flow.

v0.8.2

What's Changed

• feat(dashboard): redesign dashboard app shell and loop rendering (#88)
• feat(loop): gate supervision to the owning worktree instance
• feat: make plan tools file-like and fix plan-launch TUI workspace navigation (#87)

The dashboard app shell and loop detail views were redesigned around a unified visual language: 1-based section numbering throughout, a shared legend/cell component system, phase colors resolved through a --phase-color token, findings severity carried on the Findings metric cell, and responsive app-bar fixes. Loop supervision is now bound to the plugin instance whose directory matches the loop's worktree, so the watchdog and the session-abort handler never act on loops another instance is observing. Plan tooling was polished as well: plan-read gained a count argument for recent listings and a truncation notice with the next offset to continue reading, plan-edit reports only the sections it touched, and plan-launch now forwards the created session's workspace to the TUI.

v0.8.1

What's Changed

• feat(loop): route wedged auditor sessions through the fallback chain

A watchdog-detected wedged (busy-stalled, no streamed content) auditing session is now aborted and re-dispatched on the next configured fallback auditor model instead of receiving a generic continue nudge. The fallback advancement loop was extracted into a shared advanceAuditorFallback helper used by both the provider-limit path and the watchdog, so all detection paths advance the fallback chain exactly once per failure.

v0.8.0

What's changed

• feat(loop): nudge busy-stalled sessions when streamed content stops (#86)
• feat(sandbox): add per-session host sandbox toggle (#85)
• feat: support configurable loop permission overrides (#84)
• fix(sandbox): bound loop-attach sandbox wait by the sbx provisioning timeout

v0.7.9

What's changed

• feat: support per-entry variants in auditor fallback models

Auditor fallback models can now be specified as { model, variant } objects so each fallback carries its own reasoning/thinking variant; string entries still work and run with no variant (the primary auditorVariant is never inherited by fallbacks).

v0.7.8

Breaking changes

• The sandbox runtime now uses the sbx CLI instead of Docker. Sandbox execution and the container template have migrated from Docker to sbx create/sbx exec. Custom mounts now require absolute host paths, and legacy Docker sandbox configuration emits warnings.

What's changed

• feat: migrate sandbox driver from Docker to the sbx CLI (#82)
• feat: fall back to alternate auditor model on provider limit (#81)
• fix(sandbox): canonicalize paths when detecting mount overlap (#83)

v0.7.7

• feat: validate stored plan structure and gate autonomous launches on readiness (#80)

v0.7.6

• feat(dashboard): unify dashboard bind host/port config resolution (#78)
• chore: bump version to 0.7.6