# Firekeep Dexes — your world, indexed for agents

Dexes turn code, selected documents, and connected mail into precise context
your agents can retrieve through one Keep.

- **Symdex** maps code structure.
- **Docdex** brings selected document folders into recall.
- **Maildex** adds read-only mail context when you connect a mailbox.

[Explore the dex CLI](https://firekeep.ai/docs.html#dexes) ·
[Install Firekeep](https://firekeep.ai/docs.html#server)

## Built to answer

A dex structures one domain and answers from its index. Agents and their
explicit tools handle action.

## 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

Across 360 pinned symbol lookups, Symdex used **54.8% fewer estimated tokens**
than whole-file context while returning the requested symbol. The benchmark
covered all 12 supported languages with 100% symbol hit.

Symdex builds its index on your machine. Code slices requested by an agent
follow that client’s configured model-provider path.

[See Symdex tools and benchmark details](https://firekeep.ai/docs.html#symdex).

## Docdex — bring chosen knowledge into recall

Select 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

Docdex sends text from selected folders to your self-hosted Keep. Member-private
content is scoped from other members; the operator of the self-hosted Keep
controls its infrastructure.

[See Docdex controls](https://firekeep.ai/docs.html#docdex).

## Maildex — recall the thread behind the work

Connect a mailbox over IMAP and make recent decisions, people, and dates
recallable.

- Read-only mailbox connection
- Always member-private
- Credentials stored in the Keep vault

[See Maildex setup](https://firekeep.ai/docs.html#maildex).

## You decide what runs

The local registry is the source of truth. Symdex and Docdex arrive registered
on a fresh install; Maildex joins when you connect a mailbox. Remove a dex once
and it stays removed across updates.

```console
$ firekeep dex list
```

Supported client hooks can sync automatically. Generic MCP clients keep the
same tools and sync on demand.

## 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 Studio](https://firekeep.ai/#studio).