Build Levels & Profiles
CURD provides tier-specific build configurations depending on your explicit needs: speed, debugging overhead, or dependency size.
Choosing a Target Profile
When deploying or building CURD, use the associated Makefile target mapping.
make release (Full Build / Everything)
The absolute maximum build of CURD. Includes the full native CLI, the REPL, the MCP server, and the experimental GPU-accelerated AST engines.
- Requirement: Performance-critical environments where GPU acceleration is available and you want zero limitations.
make mcp (Standard Build / CLI + MCP)
The recommended build for most users and agents. Includes the entire structural CLI suite (Find, Graph, Refactor, REPL, Doctor) and the MCP server, but excludes the GPU subsystem to keep dependencies light.
- Requirement: Use this for standard daily work where you need both manual terminal power and AI agent integration (Claude/Cursor).
make core (Manual Build / CLI Only)
A lean build containing the full native CLI suite (REPL, Search, etc.) but strips the MCP server and the GPU subsystem.
- Requirement: Primarily for pure coders who never use AI agents and want a minimal, deterministic structural tool for their own manual use, or for developers building custom language bindings.
Workspace Dependency Overrides
The global Cargo.toml overrides standard debug modes to maximize dependency speed (e.g., Tree-sitter, Regex) using opt-level = 3, maintaining a fast indexing speed while still leaving the CURD application code capable of outputting detailed debugging traces natively.