Sessions

1 min read·Updated 30 Jul 2026

A session is a conversation with accumulated context: the messages, the tool calls, and the permission grants made along the way. Agents run inside sessions.

Lifecycle

State	Meaning
active	Accepting runs
paused	Runs cancelled, context kept. Costs nothing
archived	Read-only. Context retained, no new runs

SHELL

arble sessions new --title "Payment retry audit"
arble sessions resume ses_3pLwRt9     # reattach, context intact
arble sessions pause ses_8kQ2mVx      # stop agents, keep context
arble sessions kill ses_8kQ2mVx       # end and release context

When to start a fresh session

This is the judgment call that most affects both cost and output quality. Continue a session when the new request depends on what came before. Start fresh when it does not.

A long session carries its whole history into every run, so an unrelated question asked in a stale session pays for context it cannot use — and is more likely to be answered as though it related to the earlier work.

Export

Exports contain messages, tool calls with arguments and results, and every permission decision. This is the artifact to attach to an incident review.

SHELL

arble sessions export ses_7nBcYs4 --format json > triage.json

Deleting a session does not delete what it wrote to memory. Memory is project-scoped and outlives sessions by design.