TR-0184Completed · evidence attached
Acceptance verification
cursor 184 · acknowledged
The agent runtime that survives its own window.
Runne is a local-first Rust runtime for AI coding agents. Execution state is durable, completion requires verification evidence, and every dangerous action needs a capability grant. The chat window is a view. The runtime is the truth.
Rust · 40 crates · ~3,400 tests · 25 documented subsystems · one local process · no telemetry
runned daemon (Rust)
runned · liveRUNTIME AUTHORITY · CONFIRMED PROJECTIONS ONLY
CLIENTS
- Desktopconnected
- CLIconnected
- APIconnected
Event Journal
ORDERED · DURABLE · REPLAYABLE
TR-0185RecoveryBlocked
Workspace mutation
cursor 185 · explicit state
ISOLATED WORKSPACES
- workspace/alpha
- workspace/beta
- workspace/gamma
RUNNE FIELD NOTES · ISSUE 001
A coding task walks into a runtime.
Follow Runne through the moment a request becomes durable, controlled, and provably complete.
- 6 PANELS
- 1 SOURCE OF TRUTH
01 · THE REQUEST
A task arrives.
Runne turns the prompt into a TaskRun with an identity, a timeline, and a budget.
02 · THE INTERRUPTION
The window disappears.
The UI can close. The provider can stall. The authoritative run keeps its place.
03 · THE RECOVERY
Nothing is lost.
Runne replays the journal and resumes from confirmed state—not from a hopeful guess.
04 · THE BOUNDARY
Tools ask permission.
Files, shells, networks, and secrets stay behind explicit capability grants.
05 · THE PROOF
“Done” is challenged.
Tests, checks, and artifacts become verification evidence attached to the run.
06 · THE OUTCOME
Now it can ship.
You get a completed task with chronology, evidence, and an audit trail clients can trust.
The chat is a view. Runne is the continuity.
Durable execution · capability security · verification evidence
Not a character trait. A runtime contract.
THE THREE GUARANTEES
- 01DURABLE
The run survives its window.
- 02CONTROLLED
Every dangerous action needs a grant.
- 03VERIFIED
Completion carries evidence.
THE STORY GETS BIGGER · ISSUE 002
One run becomes a whole operating system.
The same runtime boundary keeps working as clients, providers, budgets, and histories multiply.
07 · MANY CLIENTS
Everyone sees the same truth.
Desktop, CLI, and API clients read confirmed runtime projections instead of inventing their own state.
09 · BOUNDED WORK
The budget has a guardian.
Token, time, and tool limits are enforced while accounting remains visible and attributable.
LIVE RUNTIME
See the run. Not just the chat.
Every step is backed by the journal: state, permissions, budget, and verification evidence live in one place.
TR-0184 · RUNNING
TASKRUN / TR-0184ACTIVE
- 01Request accepted
- 02Workspace prepared
- 03Agent working
- 04Verification queued
RUN STATE
- Capability grants
- 3 / 3
- Budget used
- 78%
- Journal cursor
- 184
runne task inspect TR-0184
UNDER THE PANELS
The simple shape behind every Runne story.
Clients request work. The runtime decides what is allowed, records what actually happened, and publishes only confirmed state.
- LOCAL-FIRST
- PROVIDER-NEUTRAL
- CONTRACT-DRIVEN
Clients
DESKTOP · CLI · API
runned
AUTHORITATIVE RUST RUNTIME
Event journal
SQLITE · ORDERED · REPLAYABLE
Read the contracts. Run the runtime.
Runne is local-first and designed to be inspected.