Capture. Resume. Handoff. Remember.

SessionFS starts with portable AI coding sessions: capture the work, resume it in another tool, hand it to a teammate or agent, then distil it into shared memory and audit.

Session Portability + Memory

The foundation is the portable .sfs session: captured from local tools, resumable across runtimes, shareable with teammates, and compiled into knowledge.

Session Capture

Background daemon captures every session from 9 local tools — Claude Code, Codex, Gemini, Copilot, Cursor, Amp, Cline, Roo Code, Kilo Code — into the portable .sfs format. Zero developer behaviour change.

sfs daemon start

Cross-Tool Resume

Start in Claude Code, resume in Codex. Auto-launch + full transcript via --append-system-prompt-file. Four-tool resume; 9-tool capture.

sfs resume ses_d20e --in gemini

Knowledge Base

Sessions distil into claims, decisions, patterns, and bugs. Auto-compiled wiki with backlinks. Agents read AND write — the next session inherits everything the last one learned.

68 MCP tools · wiki · backlinks

Project Context

Shared architecture, conventions, and key decisions — loaded into every AI session automatically. Explain once, never repeat.

sfs project init
Identity

Rules and personas follow every tool, every session, every teammate.

Rules Portability

One canonical rules document, compiled to CLAUDE.md, codex.md, .cursorrules, copilot-instructions.md, and GEMINI.md. Resume syncs the target tool's rules file before launch.

sfs rules init · 5 tools

Agent Personas

Portable AI roles per project (atlas, sentinel, scribe, …). ASCII name regex, soft-delete preserves history, server-side guard refuses delete while non-terminal tickets reference. Pro+ tier.

sfs persona create sentinel

Instruction Provenance

Every captured manifest records which persona + ticket + rules version was active. Sync propagates the tags into sessions.persona_name + sessions.ticket_id, so every audit query can trace any line of code back to the agent identity that produced it.

manifest.json · persona_name, ticket_id, instruction_provenance
Coordination

Handoffs move captured sessions between people and agents. Tickets carry the work, personas claim it, and AgentRuns enforce CI policy on the way out.

Governance

Built in. The foundation under everything else — verify, sanitise, audit.

LLM Judge

Cross-references every AI claim against actual tool outputs. When the AI says "test passes" but exit code is 1 — that's a critical contradiction, flagged with full evidence + CWE mapping.

CRITICAL "Test passes" exit code 1

DLP / Secret Scrubbing

Server-side scan of every archive file. 14 PHI patterns + 19 secret patterns. BLOCK / REDACT / WARN modes. Org-level policy via settings JSON; dashboard surfaces findings per-session.

sfs dlp scan · sfs dlp policy

Audit Trail

Every captured session carries instruction provenance, persona, ticket, and the AgentRun that signed off. The dashboard's Agent Runs tab is a queryable audit log; severity + policy verdict + findings JSON are all stored per run.

/api/v1/projects/{id}/agent-runs · dashboard Agent Runs tab

Ready to start?

Start with local memory, then add shared knowledge, tickets, and governance as your team adopts agents.