Agent Harness v0.10.0 — reliable continuity and safe connector actions

Highlights

Agent Harness v0.10.0 makes long-running channel work and connector actions safer and easier to understand.

• Queued follow-ups remain visibly queued until they actually start.
• Timeout and continuation handoffs retain one logical task and one final-reply owner across restarts.
• Temporary provider overloads use durable bounded retry timing and do not blindly replay attempts that may have changed external state.
• Unfinished OperationPlan work can continue from a versioned checkpoint only while the same conversation and active plan item still authorize it.
• Connector approval requests pause as Waiting for approval, with expiring approve/deny capabilities and connector-specific readback before an ambiguous write can be retried.
• Provider error diagnostics no longer retain absolute request URLs or credentials.

Compatibility and configuration

The connector approval policy defaults to needs-user; optional connector/action rules can select denial or explicit action-token approval. New state schemas are additive. The runtime normalizes the one supported legacy duplicate-account continuation shape and quarantines other identity mismatches instead of guessing.

The deployment-owned Codex CLI remains pinned to version 0.144.5. Existing operators should retain their normal binary-and-state rollback pair when upgrading.

Verification

The release passed 119 CLI tests, 1,211 core tests, all integration targets and documentation tests, cross-platform continuity and connector-effect replays, formatting, all-target compilation, fixture integrity, and an exact-commit public-export hygiene scan. A guarded live rollout was followed by ten consecutive healthy observations with no runnable runtime, cron, or worker work and no retryable provider delivery.

See the changelog for the complete user-facing change summary.