Claude Code Setup
Enable Claude Code to use Paragon CLI commands by adding context to your project.Why Add Context?
Claude Code works best when it knows what tools are available. By adding the Paragon CLI reference to your project’sCLAUDE.md file, Claude Code can:
- Automatically use
paragon runfor code analysis - Pipe diffs and code through Paragon for review
- Use semantic search with
paragon context - Manage branches and stacks efficiently
Setup
- Open or create
CLAUDE.mdin your project root - Copy the CLI reference below and paste it into the file
- Claude Code will now have access to all Paragon commands
CLI Reference
Copy the content below into yourCLAUDE.md file:
Code Analysis Commands
paragon run
Run a prompt in non-interactive mode. Accepts input via arguments or stdin.
| Flag | Description |
|---|---|
-q, --quiet | Hide spinner/progress output |
--feature | Use feature implementation mode (vs code review) |
--json | Output structured JSON findings |
--concise | Results-only, no reasoning |
-m, --model | Model selection (paragon-max, paragon-high, paragon-fast) |
paragon context
Specialized context-aware queries using semantic search and AI analysis.
paragon context issue
Diagnose and find root causes of problems.
paragon context search
Semantic code search across the codebase.
paragon context knowledge
Query project architecture and documentation.
Git Workflow Commands
paragon submit
Push branch and create/update GitHub PR with AI-generated description.
paragon branch create
Create a new stacked branch with optional AI naming.
Stack Navigation
Global Flags
Available on all commands:| Flag | Description |
|---|---|
-q, --quiet | Hide spinners and progress output |
-y, --yolo | Auto-approve all permission requests (dangerous) |
-d, --debug | Enable debug logging |
-c, --cwd | Set working directory |
Integration Examples
Code Review on Diff
Automated PR Review
Find Root Cause
Pre-commit Analysis
Explain Complex Code
Output Formats
Text Output (default)
Streaming markdown response to stdout.JSON Output (--json)
Tips
- Use
-qflag for cleaner output in scripts - Pipe code via stdin for targeted analysis
- Use
--jsonwhen parsing results programmatically - Use
context issuefor debugging problems - Use
context searchto find code patterns

