“Where is retry backoff implemented?”
Search by behavior or identifier, then retrieve the implementation with file and line attribution.
Built for coding and code review agents · Self-hosted · MCP-native
Give your agents the what, where, and why of your codebase. Search code, explore dependencies, and understand the changes behind it. Persistent repository context for Codex and other clients through MCP.
// Core Capabilities
From the first investigation to the next code review. Bring code, relationships, and history into the same conversation.
Dense embeddings plus BM25 keyword search, fused for conceptual questions and exact symbol hits. Semantic when you need meaning; precise when you need a name.
Graph traversal over callers, callees, and imports. Ask what breaks if you change a function. Get a structured answer with source locations and relationship evidence.
Commit history is first-class. Optional LLM summaries turn “who changed this” into “why it looks like this now” for agent investigations.
Detect changed files, update affected code, and reuse compatible parsing and embeddings. Keep context current with real-time file watching and Git URL synchronization.
11 core read-only tools for Codex and other clients through MCP. Search, investigate, retrieve source, and inspect index health.
Qdrant + ArangoDB + Redis under your control. Your indexes stay on your infrastructure. Bring your own embedding and LLM providers.
Search related repositories together. Follow supported cross-repository dependencies while retaining the repository, file, and source location of each result.
Trace directed paths, inspect impact, and discover related file groups. Export a graph or explore it in an interactive HTML view.
Save progress as batches finish. Recover compatible work after an interruption and activate a completed generation for retrieval.
// Pipeline
Point Alligator at a local checkout or Git URL. Language-aware extraction builds searchable code and relationships in your own stack, with workspace support for related repositories.
TREE-SITTER · QDRANT · ARANGOOptionally summarize commits and embed history so agents can reason about intent, not only the latest snapshot of the code.
LLM SUMMARIES · COMMIT GRAPHRun the MCP server over stdio or HTTP. Connect Codex and other clients in a few lines of configuration. Agents retrieve context from your published repository or workspace indexes.
FASTMCP · STDIO / HTTPFind an implementation, trace its dependencies, and inspect the changes behind it. Give coding and code review agents source-backed context in one flow.
SEARCH · GRAPH · HISTORY// Code with context. Review with perspective.
Ask Codex and other clients to use Alligator. Follow an answer back to its source.
Search by behavior or identifier, then retrieve the implementation with file and line attribution.
Explore callers and dependency paths to give your code review the surrounding context.
Bring source history and optional commit summaries into the same investigation.
Your index runs on your infrastructure. Local models run locally; API-backed embeddings and summaries send selected content to your chosen provider.
// Early access
Apache-2.0 licensed. Public CLI release coming to PyPI. Join the list for launch notes, installation guides, and release updates.
A persistent context engine for Codex and other clients, running on infrastructure you control. Choose local or API-backed models to fit your workflow.
// Public CLI distribution. The source repository remains private.
// Build status
Private alpha. These bars track the named launch checks below, not a percentage of all possible features. Updated 18 September 2026.