Use the CLI
codemap docs formatsLearn the workflow in your terminal. Query commands support JSON for scripts.
CLI reference →Skip to contentSee what your
Relationship explorerExample workspace Start with a question.
The rest of your repository
Read the capability matrix ↗Useful evidence.
Your terminal.
Local code intelligence · CLI + MCP
See what your
change touches.
Explore the connections between code, data, configuration, and documentation. Give your agent source locations and explicit limits before it edits.
brew install abdul-hamid-achik/tap/codemapOne Go binary. Offline structural queries. Optional embeddings.
GoSessionService.Load
calls · code graph
GoQueries.GetSession
depends_on · sqlc mapping
SQLGetSession
codemap context GetSessionCall accuracy depends on the language and precise coverage.
Read the relationships
- Definitions
- Calls & tests
- SQL queries
- YAML keys
- Document links
- Styles
A practical working loop
Start with a question.
Leave with evidence.
Use the same graph from a terminal or a coding agent. Keep every follow-up tied to the definition you inspected.
Follow the walkthrough →- 01
Build the local map
Index structure without an embedding service. Add precise calls where the language supports them.
codemap index --no-embed - 02
Inspect what connects
Find a definition, inspect its context, or follow a specific relationship across files.
codemap context GetSession - 03
Check the change
Inspect your diff and index freshness. Review call impact and non-call dependencies separately.
codemap review --json
Beyond source files
The rest of your repository
has structure, too.
.sql.yaml.md
Queries belong in the map.
Inspect tables, views, named queries, and lexical read/write relationships. Follow configured sqlc queries from generated Go.
Configuration has dependencies.
Navigate exact key paths. Trace Task dependencies, Compose services, and GitHub Actions job dependencies.
Keep documentation connected.
Inspect sections and follow local links into indexed files. Code examples remain documentation.
Know what the answer means
Useful evidence.
Visible boundaries.
A missing edge is not proof that nothing depends on your code. Codemap reports provenance, freshness, and partial coverage so you can choose the next check.
Understand accuracy →- Exact location
- File, line, kind, and qualified name identify the definition. Follow-up selectors survive ordinary line shifts.
- Relationship confidence
- Exact references and name-based candidates remain distinguishable. SQL and configuration relationships do not become function calls.
- Local by default
- Query the stored graph offline. Use local Ollama or delegate retrieval to Vecgrep. Remote embedding endpoints require explicit configuration.
Two ways in