Keep command history separate from provider sessions


- 01Recorded
- 02Recorded
- 03UncertainReconcile before another attempt
An uncertain command is not automatically replayed.
In 30 seconds
Problem
A coding-agent tool needs a durable project history even when provider sessions or execution hosts change.
My part
I develop the Rust core, SQLite persistence, HTTP services and CLI, alongside a React/TypeScript interface.
Result
The core records commands and uncertain outcomes separately from provider sessions, so recovery has a record to reconcile. An uncertain command is not automatically replayed.
Technical decisions
Give the logical conversation its own identity.
- Why
- A provider session is an execution detail, not the complete project history.
- Trade-off
- The core must maintain explicit mappings between conversation and runtime sessions.
Record an uncertain outcome instead of automatically repeating the command.
- Why
- A disconnected host may still be executing it.
- Trade-off
- Recovery may require reconciliation before another attempt.
Operation
The implemented core includes local command and artifact persistence, HTTP/CLI access and execution-admission contracts. I am extending runtime coordination and the shared interface.
Authorship
Independent software integrating official provider runtimes. My contribution covers the local core, execution-admission contracts and the shared interface.

