Get started
Introduction
What Carrick is, the four points where it answers, and where to start.
Carrick gives coding agents, and the engineers working with them, one current index of every TypeScript service in an organisation. It compiles routes, compiler-resolved types, and semantic function intents from your repositories on main, and answers at four points: when your agent asks over MCP, right after it edits a file via local hooks, in your code editor, and on pull requests via GitHub App comments.
See the Quickstart.
Next steps
- Quickstart installs the CLI and builds your first index.
- How Carrick works covers the problem, the three layers of the index, and each delivery surface.
- Building the index details the configuration that your agent writes, the first scan, and the CI workflow.
- In your editor details editor extension features, diagnostics, and LSP configuration.
- Connecting your agent explains agent harness integration and prompt rules.
- Task skills covers the four specialised workflows installed for coding agents.
- What Carrick covers details framework extraction, protocols, and architectural limits.
- MCP tools is the complete reference for hosted agent tools.