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.
Recorded evidence
One interruption.
A trace you can inspect.
The released run will appear here only after its checkpoint and independent checks are recorded.
- Managed worker interruptionWaiting for released run evidence
- Checkpoint validationNo result published yet
- Independent verificationUnknown until checks run
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