Use one Agent
One Agent works through the repository, Terminal, Preview, and Source Control inside the Session. Watch the repair →
Work that outlives one prompt.
Start with ordinary repository work inside a durable Session. Then inspect the execution choices and runtime capabilities that support harder decisions. Ways is optional; the workbench is the product.
Complete directory
Twelve concepts. Three layers.
Each film is an edited sequence of reachable product states. Its scenario contract defines the visible and durable evidence the sequence must retain.
Work in a Session
Return to accepted work
One Workspace groups named Sessions, and switching away does not erase an accepted Turn. Watch the return →
Keep honest final states
Partial output, exact Stop ownership, and a cancelled Turn remain reachable after reload. Watch the recovery →
Use the Session sandbox
Terminal identifies local Podman, runs the repository contract, and serves the checkout into Preview. Watch the sandbox →
Choose the execution shape
Hand work downstream
An architect and reviewer run in dependency order with separate durable outputs in one Custom Session. Watch the handoff →
Explore several Ways
Independent attempts run common Checks and remain separate while the decision is unresolved. Judge is optional; Keep selects one result, then completed cleanup ends the candidate record. Watch the comparison →
Review Last turn
A kept result returns as uncommitted Git changes. Last turn filters the current diff to attributed paths for ordinary review. Watch the Git handoff →
Inspect the runtime underneath
Configure one product
Agents and their provider/model assignments, Skills, MCP servers, and Automations remain configuration rather than peer work surfaces. Watch Settings →
Trigger an Automation
A Skill publishes its declared event and the matching trigger starts a durable Automation run. Watch the event →
Approve the exact call
A Session Turn pauses before a deterministic local MCP tool executes, then retains the result in History. Watch the approval →
Share one block explicitly
One Agent writes a shared block and another receives it in a separate Session after restart. Watch the recall →
Pause and resume an Automation
A top-level Interrupt retains upstream node state until an operator supplies the next value. Watch the Interrupt →
Work in a Session
The durable loop comes first.
Conversation is the Session spine. Files, Terminal, Preview, context, History, tools, and Git open around the same folder-anchored Session.
01 · Ordinary path
One Agent, one repository job
Start with a concrete behavior and repository Check. The Agent diagnoses the defect, edits the implementation, runs the command, and leaves the result for review without committing.
02 · Work units
Workspace, Session, Turn
An authorized Workspace groups named Sessions. Returning to one restores its accepted Turn instead of creating another disposable conversation.
03 · Continuity
Reconnect to the exact Turn
Accepted work does not depend on one browser connection. Reload reconnects to the active Turn, and Stop leaves an honest cancelled state in History.
04 · Execution boundary
Terminal and Preview share the checkout
The Terminal identifies the Session's local Podman sandbox, runs the repository contract, and serves the application opened in Preview through an explicitly published port.
Choose the execution shape
Use more structure only when the work needs it.
A configured team collaborates on one result. Ways produces independent candidate implementations. Git remains the final repository handoff.
05 · Configured team
Architect → reviewer in one Custom Session
The Systems Architect runs first. The Critical Reviewer receives that output and returns a separate decision. This is a dependency-ordered Session, not several Ways.
06 · Optional decision mode
Compare independent Ways
Every Way receives the same task and Check command. While the decision is unresolved, Axocoatl keeps completion states, Outcome, Route, changed files, and Check evidence separate. Judge is optional; Keep selects one result and cleanup ends the candidate record.
07 · Repository ownership
Keep is not commit
Keep returns one checked result to the primary Session checkout. Source Control → Last turn filters the current Git diff to paths attributed to the kept Turn before any optional staging or commit; it is not a frozen per-turn diff.
Inspect the runtime underneath
Configuration and durable machinery support the workbench.
Agents, Skills, MCP servers, and Automations live in Settings. Typed events, approval gates, shared memory, and operator Interrupts remain explicit instead of turning into hidden magic.
08 · Settings
Configure one product
Agents and their provider/model assignments, Skills, MCP servers, and Automations stay in Settings rather than becoming peer destinations beside the Session. Provider endpoints and credentials remain explicit in axocoatl.yaml.
09 · Typed events
A Skill can trigger an Automation
The Skill publishes its declared event. The event lattice carries it to configured observers, and the matching Automation trigger starts an inspectable durable run.
10 · MCP approval
A new permission pauses the call
With no matching saved decision, a normal Session Turn pauses before a deterministic local MCP tool executes. Deny prevents dispatch; Allow once returns bounded tool evidence and the final answer to History.
11 · Shared core memory
Share one block explicitly
One configured Agent writes a named shared block through a visible tool call. After daemon restart, another Agent receives the exact value in a separate Session whose transcript remains distinct.
12 · Operator judgment
Pause and resume an Automation
A top-level Interrupt parks the run with upstream node state intact. Operator guidance resumes from that checkpoint and the completed Result remains in run history.
Bring the repository. Keep the context.
Start one durable Session and let the work surface grow around the job.