SYCode
symbols · callers · impact
Firekeep Dexes
Your world,
indexed for agents.
Turn code, selected documents, and connected mail into precise context your agents can retrieve through one Keep.
- 3Dexes ship today
- 12Code languages
- 1Recall surface
Domain Atlas / live registry Ready
DODocuments
passages · sources · scope
MAMail
threads · people · dates
Dex registryregistered · scoped · queryable
Answer receipt3 sources
Checkout validation starts in validate_order, is called by two routes, and matches the rollout note in payments.md.
The design rule
Built to answer.
A dex structures one domain and answers from its index. Agents and their explicit tools handle action.
Three focused indexes
Three lenses.
One recall surface.
Each dex understands the shape of its own domain, then meets your agents through Firekeep.
01 / SYMDEX
Navigate code by structure.
Find symbols, trace callers, map architecture, and estimate impact without loading whole files into context.
- Local, tree-sitter-backed index
- 12 supported languages
- Available to connected MCP agents
routePOST /checkoutapi/routes.py:42
functionvalidate_orderservices/orders.py:118
callercreate_chargepayments/core.py:67
coveragetest_checkouttests/test_orders.py:31
4 symbols3 relationshipsimpact set ready
02 / DOCDEX
Bring chosen knowledge into recall.
Index the folders that matter. Firekeep turns their contents into sourced passages that appear alongside team memory.
- Selected folders only
- Member-private by default
- Optional workspace sharing
Architecture18 documents
indexedRunbooks32 documents
indexedProduct notes11 documents
indexedRECALLED PASSAGE · payments.md
Stage the schema before switching traffic. Keep the compatibility reader for one release.
03 / MAILDEX
Recall the thread behind the work.
Connect a mailbox over IMAP and make recent decisions, people, and dates recallable without giving Firekeep send access.
- Read-only mailbox connection
- Always member-private
- Credentials stored in the Keep vault
Alex Morgan · 09:14Rollout sequenceLet’s stage the schema first, then switch traffic after the compatibility check.
Jordan Singh · 09:32Re: Rollout sequenceConfirmed. The runbook and owner list are updated.
Private recall ready2 messages · 2 people · 1 decision
Published Symdex benchmark
Less context.
The code stays clear.
Across 360 pinned symbol lookups, Symdex used fewer estimated tokens than whole-file context while returning the requested symbol.
Read the full benchmark
54.8%
fewer estimated tokens
360 lookups
12 languages
100% symbol hit
Local control
You decide
what runs.
The local registry is the source of truth. Symdex and Docdex arrive ready on a fresh install; Maildex joins when you connect a mailbox. Remove a dex once and it stays removed across updates.
firekeep / dex registry workstation
$
firekeep dex listsymdexregisteredlocal code index
docdexregisteredselected folders
maildexoptionalconnect when wanted
Index locally.
Symdex builds its index on your machine. Code slices an agent requests follow that client’s configured model-provider path.
Choose the sources.
Docdex sends text from selected folders to your self-hosted Keep and keeps each source member-private unless you share it.
Keep scope visible.
Member-private content is scoped from other members; the operator of the self-hosted Keep controls its infrastructure.
Sync your way.
Supported client hooks can sync automatically. Generic MCP clients keep the same tools and sync on demand.
From context to visible work
Bring structured context
into the workflow.
Dexes deepen what the Keep can retrieve. Firekeep Studio brings that context into a visible workflow for Keep-connected runtimes.
Meet Firekeep StudioStart with the world you already have
Give your agents
a better map.
Install Firekeep, choose the document folders that matter, and connect mail only when you want it.
curl -fsSL https://firekeep.ai/latest/install | sh