Conduit v0.6.0: safer updates and clearer workflows

Conduit v0.6.0 makes the application easier to keep current and makes multi-agent workflows more resilient when tools generate files, cross ownership boundaries, or report negative verification evidence.

Guided self-update

Home now checks for newer stable Conduit releases and presents the running and available versions without blocking startup. Before any installation begins, Conduit identifies the installation method, names the exact target version, and asks for confirmation.

Standalone updates download only supported release assets, verify checksums, and replace the executable atomically. Package-manager installations use fixed exact-version commands. Failed downloads, checksum mismatches, unsupported installations, and replacement errors preserve the existing executable and return bounded recovery guidance.

Role-aware workflow completion

Implementation-producing assignments retain strict completion rules: every reported verification check must pass. Research, QA, and review assignments can complete after truthfully reporting a failed product check as evidence, keeping evaluation results available to the workflow instead of misclassifying a discovered defect as an agent protocol failure.

Ownership remains an integration signal without assuming a particular project layout. Changes outside an assigned path are recorded as review warnings, while read-only and forbidden paths remain hard boundaries. Repository-root ownership now covers root and nested files consistently, including projects that begin without a commit.

Faster, safer worktree monitoring

Worktree observation excludes untracked dependency trees, caches, build output, coverage, and browser-test artifacts before fingerprinting. This prevents installs and verification side effects from flooding the monitor or being mistaken for implementation artifacts. Tracked files remain authoritative.

Changed-file and patch collection is bounded by file count, per-file size, and total preview size. The monitor renders a window around the selected path, offers direct keyboard focus for changed files, and keeps an open diff visible while moving between files.

More reliable harness output

OpenCode runs now request the CLI’s machine-readable JSON format explicitly, allowing Conduit to capture structured activity and the final AgentResponseV1 without depending on formatted terminal output. Codex continues to use JSONL and adapter-owned final-message capture.

Read the documentation for installation, configuration, and workflow commands.