Conduit v0.7.0: resilient workspaces and dependable handoffs

Conduit v0.7.0 makes long-running, multi-agent work safer to resume and easier to understand. Role work now survives interrupted runs with verifiable Git lineage, reviewers receive the dependencies they need, and completed work reaches the project only after an explicit approval gate.

Announcement: durable role workspaces

Every role now receives one managed workspace slot per repository identity. Conduit records its branch, commit, assignment identity, package hash, lease, and generation in project state instead of treating a directory name as proof of ownership.

When a run fails or is interrupted, Continue verifies the complete identity envelope before preserving completed roles and retrying only failed or unfinished work. Start Anew remains an explicit destructive choice: it preserves recoverable lineage, removes only the exact registered worktree, and refuses ambiguous or mismatched state.

Workspace leases use fencing tokens so stale owners cannot mutate a slot after another process claims it. Conduit never runs a repository-wide worktree prune and never infers disposable content from language-specific directory names.

Approval-gated integration and recovery

Reviewer process completion is now separate from reviewer approval. A run is complete only after an approved verdict and a clean, fast-forward-only promotion into the unchanged project checkout. Rejected or needs_changes findings can route bounded corrections to one owning implementation role before review runs again.

Failed runs expose recovery eligibility in both the CLI and TUI. Compatible work resumes in place; package, commit, assignment, repository, workspace, or lease mismatches fail before an agent starts. Promotion and lifecycle failures retain recoverable commits instead of silently discarding them.

Structured ACP response submission

ACP-backed agents now submit AgentResponseV1 through a temporary Conduit-owned MCP tool. The tool validates the complete response in the same turn and returns bounded feedback when a submission is malformed. Only accepted tool submissions become authoritative; assistant prose remains activity output.

The response tool is scoped to the native session and removed when that session closes. Codex and other verified fallback transports continue to use their captured machine-readable protocols through the same harness-neutral communication boundary.

Better dependency and verification handoffs

Downstream role workspaces can inherit dependency trees from completed prerequisite roles. This lets a reviewer reuse the environment prepared by QA without committing dependency files or polluting the project checkout.

Generated changes inside those provisioned dependency trees are treated as disposable workspace state, not as product changes or read-only policy violations. Research remains read-only and can run against dirty or not-yet-committed repositories, while implementation runs still require a clean committed starting point for safe promotion.

A clearer worker monitor

The worker monitor now gives logs and files dedicated views, uses the available terminal height for larger diffs, and reports patch-line counts instead of misleading file totals. Retry transcripts are folded back into their configured role so completed attempts no longer appear as phantom workers.

Run and feature status now follow the actual approval and promotion lifecycle. Continued runs open directly in the monitor, and successful promotion marks the feature implemented.

Upgrade

Use the guided update action in Conduit, install the latest standalone binary, or upgrade through your existing package manager after the v0.7.0 release is published.

Review the documentation for installation, configuration, recovery, and run commands.