Local-first · project-scoped · written in Rust

Persistent memory
for any AI agent

Phantasm bootstraps once per project, keeps durable context attached to the repository or folder where the work actually happens, and compiles exactly what an agent needs — fast, local, and deterministic. Task-independent: any agent, any workflow.

Get started Why Phantasm?
Memory Context Compile
terminal — bootstrap 
brew install indefiniteloop/tap/phantasm
# or
curl -fsSL https://raw.githubusercontent.com/indefiniteloop/phantasm-dist/main/scripts/install.sh | sh
phantasm --version
phm --version

cd /path/to/project
phantasm bootstrap --agent-guidance
phantasm agents-plugin --dry-run
phantasm handle-request '{"operation":"describe","params":{"target":"all"}}'

FAQ

What people ask right after bootstrap

What changed recently?

Read the release changelog. It lists versioned release notes, including the current release.

How do I review memory quality?

v0.2.6 adds a bundled Hermes Agent memory provider with 8,000-character recall and no compression pipeline interference. The v0.2.5 automatic quality_json store repair, local Explorer, dashboard, init, agent plugin installer, quality metadata, freshness review, duplicate review, and canonical JSON export workflows remain available. See the command reference for the exact discovery and request shapes, or the agent installation guide for a complete setup protocol.

Do I need Rust installed to use Phantasm?

No. The public install paths use Homebrew or the published install script, so a Rust toolchain is only needed if you plan to build Phantasm from source.

Where does the runtime store project data?

Inside the repository under .phantasm/. Config lives in phantasm.toml and clients.toml, while mutable state lives under .phantasm/state/.

How do I change the default client or trust rules?

Edit the files created by bootstrap. The configuration reference explains every supported key in both runtime config files.

Can I set context length or token budget today?

Not yet. The current shipped config surface does not expose a context-length setting after bootstrap. The configuration reference calls this out explicitly so the docs stay aligned with the code.