Skip to main content
AMFS models every agent’s memory as a Git repository. Each write, outcome, cross-agent read, and brain brief is recorded as an event on the agent’s timeline — like commits in Git. This gives you full auditability, rollback capability, and branch-based collaboration.

The Mental Model

When an agent is created in AMFS, it implicitly gets a repository with a main branch. Every operation the agent performs is logged as an event on that branch:

Event Types

Every operation produces a typed event on the agent’s timeline:

Querying the Timeline

Python SDK

HTTP API

Response:

MCP


Branches (Pro)

With AMFS Pro, you can create branches from an agent’s main timeline — just like Git branches. Branches let you:
  • Experiment safely — write to a branch without affecting main memory
  • Share selectively — grant read or read/write access to specific users, teams, or API keys
  • Review changes — see the diff between a branch and main before merging
  • Merge or discard — bring branch changes into main, or close the branch

Creating a Branch

Writing to a Branch

All read/write operations accept a branch parameter:
Or via the HTTP API:

Reading from a Branch

Access Control

Branch access is enforced at the API level. When a request targets a non-main branch, the caller’s API key is checked against the branch access grants:
Requests without access receive a 403 Forbidden response.

Viewing the Diff

Merging

Pull Requests

For team workflows, create a PR for review before merging:

Tags and Rollback (Pro)

Tags

Create named snapshots of your agent’s memory at a point in time:

Rollback

Restore memory to a previous state:
Or roll back to a specific timestamp:

Fork (Pro)

Clone an agent’s entire memory into a new agent:

Architecture

The timeline is always available in OSS (main branch only). Branching, merging, tags, rollback, and access control require AMFS Pro.