Notebooks

Event-sourced notebooks for tracking tool execution.

Notebooks

Notebooks are event-sourced execution contexts within a project. Every tool call, result, and state change is recorded as an immutable event. The current state of a notebook is the replay of all its events from the beginning.

Event Sourcing Model

Traditional systems store the current state and discard history. Notebooks take the opposite approach:

state = replay(events)

Every action appends an event to the log. The notebook's current state is always derived by replaying the full sequence of events. This means you can:

• Inspect any past state by replaying events up to a given point
• Rewind to undo recent actions without losing the event history
• Fork a notebook at any event to explore alternative paths

Note: Events are append-only and immutable. Even a rewind does not delete events — it moves a cursor back in the sequence. See Events for details.

Creating Notebooks

Create a new notebook from the project view. The notebook inherits the project's default trust level and starts with an empty event log.

Forking at Any Event

You can fork a notebook at any event in its history. The new notebook starts with a copy of events up to the fork point, giving you a clean branch to explore different approaches without affecting the original.

Tip: Forking is useful when you want to try an alternative resolution for an issue without losing the work done in the original notebook.

Trust Override

Each notebook can override the project's default trust level. This lets you run exploratory work in confirm mode while keeping the project default at gated for production workflows.

See Trust for a full explanation of trust levels and how they interact with tool tiers.