Coding work, kept in motion.
Keep the work.
Change the agent.
Dovet saves the useful state of a coding task, hands interrupted work to an authorized worker, and checks the result before calling it finished.
Codex integration. Strands recovery. Your rules.
Build evidence
The local recovery path is already measurable.
The Bedrock handoff remains blocked until the build account authorizes Nova Micro. Local evidence stays separate from that missing cloud proof.
- Managed Codex interruptionOwned turn stopped through the supported SDK
- Immutable checkpoint restoreSelected files restored byte for byte
- Core and browser checksIndependent local tests plus desktop and mobile UI checks
- Live Strands recoveryNova Micro account authorization is not yet available
Actual product UI
Every green state has a receipt behind it.
Dovet accepts only a validated PASS receipt for this view. The release recorder uses the same gate and refuses to capture a simulated cloud success.
- Durability
- An independent launchd service survives the Codex bridge exiting.
- Portable recovery
- A sanitized bundle verifies every path and hash before restore.
- Install proof
- The built wheel passes in a fresh Python 3.12 environment.
- Evidence labels
- Observed, reported, inferred and independently verified facts stay distinct.
The problem
The interruption is only the first problem.
After a coding agent stops, you still have to work out what changed, what passed, what failed, and what the next worker needs to know. Dovet keeps that recovery work attached to the task.
- Task brief
- Scoped changes
- Verified checks
- Next action
How it works
Recovery with an audit trail.
- 01
Save the working state.
A checkpoint records the approved task, selected files, evidence and last verified result.
- 02
Recover within your rules.
A Strands supervisor recommends the next move. Policy, budget and workspace ownership determine whether it can proceed.
- 03
Check before calling it done.
Independent verification runs against the recovered snapshot. Failed or unavailable checks stay visible.
Automatic recovery applies to Dovet-managed runs. Existing desktop sessions can be observed and handed off with your involvement.
Boundaries
Autonomy with an edge you can see.
Dovet does not rotate ChatGPT accounts, merge code for you, or let a worker approve its own permissions. It pauses when the next action needs a decision.
- Approved paths
- The worker sees only the configured project scope.
- Authorized workers
- Recovery choices come from an explicit provider list.
- Explicit budget
- Policy denies dispatch without an approved bound.
Local-first
Your workspace stays yours.
Project state and checkpoint history are stored locally by default. Your approved coding providers receive the context needed to do the task. Cloud evidence sharing is explicit, and the public demo uses synthetic code.
Read the data boundaries