Troubleshooting Guide
Common issues and solutions when using the Radium CLI.
Workspace Issuesβ
"No Radium workspace found"β
Problem: Command requires a workspace but none is found.
Solution:
rad init
"Failed to discover workspace"β
Problem: Workspace structure is corrupted or missing.
Solution:
# Reinitialize workspace
rad init --use-defaults
# Or check workspace structure
rad doctor
Plan Execution Issuesβ
"Plan not found"β
Problem: Plan identifier doesn't match any existing plan.
Solution:
# List available plans
rad status
# Use correct REQ ID or folder name
rad craft REQ-001
"Plan manifest not found"β
Problem: Plan directory exists but manifest is missing.
Solution:
# Regenerate plan
rad plan spec.md --id REQ-001
Execution hangs or loopsβ
Problem: Plan execution gets stuck in a loop.
Solution:
# Use bounded execution instead of YOLO
rad craft REQ-001 # Default bounded mode
# Or specify iteration limit
rad craft REQ-001 --iteration I1
Agent Issuesβ
"Agent not found"β
Problem: Agent ID doesn't exist in configuration.
Solution:
# List available agents
rad agents list
# Check agent discovery
rad agents validate <agent-id>
"Failed to create model"β
Problem: Model/engine configuration is invalid.
Solution:
# Check engine status
rad engines status
# Verify authentication
rad auth status
# Use mock engine for testing
RADIUM_ENGINE=mock rad step <agent-id>
Authentication Issuesβ
"Missing credentials"β
Problem: Authentication required but not configured.
Solution:
# Login to provider
rad auth login <engine>
# Check status
rad auth status
"Authentication failed"β
Problem: Credentials are invalid or expired.
Solution:
# Logout and login again
rad auth logout <engine>
rad auth login <engine>
Source Detection Issuesβ
"Source detection failed"β
Problem: Source format is not recognized.
Solution:
- File: Ensure file path is correct and file exists
- Jira: Use format
PROJ-123(uppercase, dash, digits) - Braingrid: Use format
REQ-YYYY-NNN(year and 3+ digits)
# Check file exists
ls spec.md
# Use correct format
rad complete RAD-42 # Jira
rad complete REQ-2025-001 # Braingrid
"Source not found"β
Problem: Source exists but cannot be accessed.
Solution:
# For Jira/Braingrid: authenticate first
rad auth login jira
rad auth login braingrid
# For files: check permissions
ls -l spec.md
Extension Issuesβ
"Extension not found"β
Problem: Extension doesn't exist or isn't installed.
Solution:
# List installed extensions
rad extension list
# Install extension
rad extension install <source>
"Extension installation failed"β
Problem: Extension package is invalid or corrupted.
Solution:
# Validate extension before install
# Check extension manifest structure
# Try with overwrite
rad extension install <source> --overwrite
Monitoring Issuesβ
"Failed to open monitoring database"β
Problem: Monitoring database doesn't exist yet.
Solution:
- This is normal if no agents have been executed yet
- Execute an agent first to create the database
rad step <agent-id>
"Agent not found" in monitoringβ
Problem: Agent hasn't been tracked yet.
Solution:
- Agents are tracked during execution
- Run an agent first:
rad step <agent-id>
rad monitor list
Checkpoint Issuesβ
"Workspace is not a git repository"β
Problem: Checkpoints require git.
Solution:
# Initialize git repository
git init
git add .
git commit -m "Initial commit"
# Now checkpoints will work
rad checkpoint list
"Checkpoint not found"β
Problem: Checkpoint ID doesn't exist.
Solution:
# List available checkpoints
rad checkpoint list
# Use correct checkpoint ID
rad checkpoint restore <checkpoint-id>
Performance Issuesβ
Slow executionβ
Problem: Execution is taking too long.
Solution:
# Use specific iteration/task instead of full plan
rad craft REQ-001 --iteration I1
# Check agent performance
rad monitor telemetry
# Use faster engine/model
rad craft REQ-001 --engine mock
High token usageβ
Problem: Token usage is higher than expected.
Solution:
# Check usage
rad stats usage
# Use more efficient models
rad step <agent-id> --model gpt-3.5-turbo
# Review agent prompts for verbosity
JSON Output Issuesβ
"Invalid JSON"β
Problem: JSON output is malformed.
Solution:
# Ensure --json flag is used
rad status --json
# Parse with jq for validation
rad status --json | jq .
General Issuesβ
Command not foundβ
Problem: rad command is not in PATH.
Solution:
# Build and install
cargo build --release -p radium-cli
# Add to PATH
export PATH=$PATH:/path/to/target/release
Permission deniedβ
Problem: Insufficient permissions for workspace operations.
Solution:
# Check directory permissions
ls -ld .radium
# Fix permissions if needed
chmod -R u+w .radium
Out of memoryβ
Problem: Process runs out of memory.
Solution:
# Use bounded execution
rad craft REQ-001 # Not --yolo
# Execute smaller chunks
rad craft REQ-001 --iteration I1
Getting More Helpβ
Enable verbose loggingβ
RUST_LOG=debug rad <command>
Check workspace healthβ
rad doctor
View command helpβ
rad <command> --help
rad <command> <subcommand> --help