Skip to main content
Named sessions let you share a filesystem between multiple agents, terminals, or runs. All participants see the same copy-on-write view of your project.

Creating a Session

Use --session to create a named session:
This creates a session called my-project. All changes are stored in .agentfs/my-project.db.

Resuming a Session

Run the same command to resume where you left off:

Multi-Terminal Collaboration

Multiple terminals can share the same session simultaneously:
All terminals share the same copy-on-write filesystem. Changes made in one terminal are immediately visible in others.

Use Cases

Iterative Development

Work on a task across multiple sessions:

Safe Experimentation

Create a session, try something risky, then decide whether to keep it:

Agent Supervision

Run an agent and monitor its work from another terminal:

Managing Sessions

List files in a session:
View session changes:
Delete a session:

Session Storage

Sessions are stored as SQLite databases in .agentfs/:
Each database contains:
  • All modified files
  • Deleted file markers (whiteouts)
  • Tool call audit log
  • Key-value store data

Next Steps

Auditing

Inspect what happened in a session

Overlay Filesystem

How copy-on-write works