experiment
Keeping coding-agent work alive after the terminal closes.
Testing whether a persistent runtime can let TUI, Web, and CLI clients share task state and recover approvals, tool output, diffs, and verification after an interruption.
The experiment asks a narrow question. Can a coding-agent task outlive the terminal process that started it and still be resumed later?
CodeLeveler now connects its TUI, Web UI, and CLI to the same runtime contract. Sessions, approvals, tool output, diffs, and verification state are stored locally. The public beta can save and resume work, while long-running reliability remains under active testing.
A task should not disappear with its terminal
A real coding task moves through repository inspection, edits, commands, approvals, and verification. Those states need to remain reviewable after the original process ends.
Separate clients from the runtime
The TUI, Web UI, and CLI share commands, events, and snapshots. Platforms with local daemon support can reconnect to the runtime, while SQLite keeps sessions and pending state durable.
Tasks can be resumed, with longer runs still under test
The public beta supports run, resume, TUI, and Web workflows. Windows can resume saved sessions, although daemon transport still has platform limitations.