Firekeep Firekeep Studio
Self-hosted continuity for connected AI agents

Your agents shouldn’t work like strangers.

Firekeep gives your team and connected agents one self-hosted Keep for shared knowledge, live context, handoffs, and inspectable work history—across sessions, tools, and machines.

Claude Code, Codex, Kiro, OpenCode, and other MCP clients can work from the same durable context. Where a client exposes supported hooks, Firekeep adds automatic briefings and lifecycle guidance.

Install Firekeep See it in daily work

Firekeep StudioLatest stable desktop app

Download forWindowsx64 Download formacOSUniversal
  • Self-hosted
  • MCP-native
  • Personal + team knowledge
Connected agents / shared operating context Local gateway · self-hosted Keep
  • CL

    Claude Codeadapter + hooks

  • CX

    CodexMCP + guidance

  • KI

    Kiro CLIadapter + hooks

  • MCP

    OpenCode + MCPadapter or generic

local stdio

Local gatewayMCP · identity · routing

Your self-hosted Keep127.0.0.1default server bind

  • Knowledgedecisions + procedures
  • Working stategoals + progress
  • Coordinationtasks + handoffs
  • Evidencereplay + outcomes
Your agents keep their own interfaces. The local gateway connects them to the same Keep through MCP; automatic lifecycle behavior depends on each client’s hooks.

01 / shared progress

Every session starts
with more.

Firekeep carries selected decisions, procedures, and working state between the agents and people you connect—without replacing the tools they already use.

01

Start informed.

Bring relevant decisions, project history, and procedures into the next session before the background has to be rebuilt.

Briefings · recall · provenance
02

Stay oriented.

Goals, plans, decisions, and progress remain available through context compression, handoffs, and new machines.

Goals · plans · working state
03

Finish with confidence.

Keep a useful lesson with provenance so the next teammate or agent can use it in context.

Skills · handoffs · evidence

Less reconstruction. Clearer handoffs. Each useful session improves the starting point for the next.

Supported runtime hooks can deliver briefings and lifecycle guidance automatically; other connected MCP clients recall the same Keep through its tool surface.
Set up shared memory between Claude Code and Codex

02 / personal → shared

Your knowledge becomes
your team’s memory.

Start with your own projects and machines. Add teammates to the same complete product when context should travel across people, roles, and tools.

01 / personal

Carry less in your head.

Your decisions, active goals, selected folders, and hard-won fixes stay available across connected sessions and machines.

02 / shared

Give the team one thread.

Project context, procedures, handoffs, and evidence remain connected to the people and projects they came from.

03 / organizational

Let knowledge compound.

Chosen runbooks, internal documents, code structure, and operating history return inside everyday AI-assisted work.

One place. More contributors. A richer starting point for every connected agent.

Folders added through Docdex are member-private by default, even on a shared Keep. Share with the workspace only when you intend to.

New 03 / Firekeep Studio · latest stable

Your AI work,
in one clear place.

Firekeep Studio brings Codex, Claude Code, Kiro CLI, and Grok into one desktop workspace. Choose who leads, bring in a fresh reviewer, and turn important goals into Missions with visible checks and human acceptance.

Windows installer Universal Mac installer

Latest stable · Windows x64 · macOS for Apple Silicon + Intel

Installation and quick start
Firekeep Studio showing its multi-runtime conversation workspace, sessions, Mission panel, and agent runtime controls
Actual Studio interfaceLatest stable · Windows x64 + universal macOS
  1. 01 / resume

    Pick up the thread.

    Named local sessions and a chosen workspace make the next turn easy to find.

  2. 02 / roles

    Keep roles clear.

    One explicit primary leads. Fresh, read-only reviewers add perspective without taking over.

  3. 03 / evidence

    Finish with evidence.

    Missions pair the work with deterministic local checks, bounded repair, review evidence, and your final acceptance.

Install → first turn

From download to a working session.

Studio uses your installed Codex, Claude Code, or Kiro CLI. Grok connects directly with an xAI key protected by your operating system.

  1. 01Install and open.

    Run Windows Setup, or open the Mac DMG and move Firekeep Studio to Applications.

  2. 02Choose the workspace.

    Select the project folder every runtime should use. Studio remembers it locally for the next session.

  3. 03Pick the primary.

    Choose the agent that leads the conversation, then connect its provider account if Studio asks.

  4. 04Start working.

    Run /doctor, send your first prompt, then add a reviewer or create a Mission when the work needs proof.

Start here /doctor /workspace choose /reviewer add claude /mission new See every step

04 / under the hood

Your knowledge.
Your infrastructure.

Connected MCP agents call one local gateway. Behind it, your self-hosted Keep carries working knowledge, session state, procedures, coordination, and evidence across the tools you already use.

Explore the self-hosted MCP memory server
01Your agentsexisting tools
CLClaudeCode + Desktop
CXCodexApp Server + MCP
KIKiroCLI / ACP
OCOpenCodenative adapter
··Any MCP clientgeneric configuration
02Local gatewayon each machine
one firekeep gatewaystdio · identity · routing
Client Kitconfig + lifecycle
Symdexlocal code intelligence
Decision Boardlocal human input
Studioseparate optional console
03Your Keepself-hosted server
C

Cortexmemory · RAG · skills

B

Bridgesessions · replay

R

Relaytasks · coordination

S

Sentinelenvironment events

QdrantNeo4jRedisOllama
01 / you choose where it lives

Self-hosted core. Server, datastores, embeddings, and default inference run on infrastructure you control.

02 / you choose what connects

Your connections. Model providers and optional integrations follow the services you configure.

03 / one shared doorway

Connected by MCP. Supported client hooks add automatic briefings and lifecycle guidance.

What your Keep carries

Knowledge, state,
practice, and proof.

Each part stays connected to its project and provenance, so the right context can return without becoming a pile of disconnected notes.

FIREKEEP / SYSTEM CUTAWAYSix connected layers · one self-hosted Keep
  1. 01
    Knowledge

    Keep what the work has learned.

    Decisions, facts, proven fixes, and selected documents stay connected to their source and relationships.

    memory · provenance · Docdex
  2. 02
    Working state

    Return to where the work stands.

    Goals, plans, decisions, progress, and file notes carry through compression, handoff, and tomorrow’s session.

    briefing · shadow · resume
  3. 03
    Procedures

    Reuse the way a problem was solved.

    Reusable Skills and document-derived drafts turn hard-won fixes into reviewable team practice.

    skills · drafts · runbooks
  4. 04
    Coordination

    Give shared work clear ownership.

    Tasks, messages, presence, handoffs, and fenced resource leases help agents and teammates coordinate.

    relay · leases · presence
  5. 05
    Evidence

    See what happened and why.

    Firekeep-mediated replay, declared outcomes, and evaluation receipts make important work inspectable.

    replay · outcomes · evals
  6. 06
    Domain context

    Bring the world around the prompt.

    Docdex covers selected documents, Symdex maps code, and Maildex adds member-private, read-only mail recall.

    Docdex · Symdex · Maildex · explore ↗

05 / evidence

We publish the passes.
The misses. The unknowns.

Firekeep is measured in real work across development and operations. Baselines stay baselines, uncertainty stays visible, and the methods and result data are open to inspect.

LongMemEval-S benchmarkEvidence Recall@10
97.7%

Relevant evidence found in the first 10 results

Firekeep retrieved an evidence-bearing session for 459 of 470 scored questions. This measures retrieval, not generated-answer accuracy.

459 found470 scoredAug 2026 run
Read the benchmark report
Five-month case-study snapshotEngineering + operations
90

Tracked sessions in the study’s latest month

Weeks after a difficult deployment fix, the relevant procedure returned in a pre-flight briefing to an agent that had never seen the original incident.

45 active skills12 internal docs845 commits
Read the five-month case study
Published instruction baseline32 production sessions
56%

Recalled before answering

18 of 32 sessions met the frozen recall predicate. A newly shipped action-declaration instruction began at 0 of 32 and later moved to 1 of 35; exposure receipts now separate exposed, not exposed, and unknown sessions.

18/32 recall0/32 → 1/35 rolloutunknown stays unknown
Read the instruction study

06 / install Firekeep

Install Firekeep.
Make tomorrow easier.

Give your decisions, documents, procedures, and working context a durable place to live—then connect the agents and teammates who should build on them.

macOS / Linux curl -fsSL https://firekeep.ai/latest/install | sh
Windows irm https://firekeep.ai/latest/install.ps1 | iex
Open the installation guide Read the technical docs

Free for self-hosted internal use by individuals and teams during early access. No Firekeep account or licence key required.

Source-available under BUSL-1.1. Each release converts to Apache-2.0 four years after publication.