Skip to content

Troubleshooting Guide

Common issues and solutions for Devo CLI.

Installation Issues

Command Not Found

Problem: devo: command not found after installation

Solutions:

  1. Restart terminal:
# Close and reopen terminal
# Or reload shell configuration
source ~/.bashrc  # or ~/.zshrc
  1. Check PATH:
# Verify devo is in PATH
which devo

# Add to PATH if needed
export PATH="$HOME/.local/bin:$PATH"
  1. Verify installation:
# Check if binary exists
ls -la ~/.local/bin/devo
ls -la /usr/local/bin/devo

Permission Denied

Problem: Permission denied when running devo

Solutions:

# Make executable
chmod +x ~/.local/bin/devo

# Or reinstall with correct permissions
curl -fsSL https://raw.githubusercontent.com/edu526/devo-cli/main/install.sh | bash

Windows Execution Policy Error

Problem: PowerShell blocks script execution

Solution:

# Allow script execution for current user
Set-ExecutionPolicy -Scope CurrentUser RemoteSigned

# Then retry installation
irm https://raw.githubusercontent.com/edu526/devo-cli/main/install.ps1 | iex

AWS Credentials Issues

No Credentials Found

Problem: Unable to locate credentials or NoCredentialsError

Solutions:

  1. Configure AWS CLI:
aws configure
  1. Use AWS SSO:
aws sso login --profile my-profile
export AWS_PROFILE=my-profile
  1. Verify credentials:
aws sts get-caller-identity

Access Denied to Bedrock

Problem: AccessDeniedException when using AI features

Solutions:

  1. Enable Bedrock model access:
  2. Go to AWS Console → Bedrock
  3. Navigate to "Model access"

  4. Request access to Claude models

  5. Check IAM permissions:

{
  "Effect": "Allow",
  "Action": [
    "bedrock:InvokeModel",
    "bedrock:InvokeModelWithResponseStream"
  ],
  "Resource": "arn:aws:bedrock:*::foundation-model/anthropic.claude-*"
}
  1. Verify region:
# Bedrock is not available in all regions
devo config set aws.region us-east-1

Wrong AWS Account/Role

Problem: Using wrong AWS account or role

Solutions:

# Check current identity
aws sts get-caller-identity

# Use specific profile
devo --profile production commit

# Set default profile
export AWS_PROFILE=production

Configuration Issues

Configuration Not Loading

Problem: Configuration changes not taking effect

Solutions:

  1. Verify configuration file:
devo config path
devo config show
  1. Reset if corrupted:
devo config reset

Invalid Configuration Values

Problem: Configuration value needs to be updated

Solutions:

# Show current value
devo config show

# Fix invalid value
devo config set aws.region us-east-1

Command-Specific Issues

Commit Command Issues

Problem: No staged changes found

Solution:

# Stage changes first
git add .

# Then generate commit message
devo commit

Problem: Commit message generation fails

Solutions:

  1. Check AWS credentials:
aws sts get-caller-identity
  1. Verify Bedrock access:
aws bedrock list-foundation-models --region us-east-1
  1. Try different model:
devo config set bedrock.model_id us.anthropic.claude-3-7-sonnet-20250219-v1:0

Code Reviewer Issues

Problem: Code review fails or returns errors

Solutions:

  1. Make sure you have commits on your branch that differ from the base branch:
# Check your branch has new commits vs main/master
git log main..HEAD --oneline
  1. Use a closer base branch for large features:
devo code-reviewer --base-branch your-parent-branch
  1. Verify AWS credentials:
aws sts get-caller-identity

Upgrade Command Issues

Problem: Failed to download latest version

Solutions:

  1. Check internet connection:
curl -I https://github.com
  1. Verify GitHub access:
curl -I https://api.github.com/repos/edu526/devo-cli/releases/latest
  1. Manual upgrade:
# Download manually
curl -L https://github.com/edu526/devo-cli/releases/latest/download/devo-linux-amd64 -o devo
chmod +x devo
sudo mv devo /usr/local/bin/

CodeArtifact Login Issues

Problem: Failed to authenticate with CodeArtifact

Solutions:

  1. Check IAM permissions:
{
  "Effect": "Allow",
  "Action": [
    "codeartifact:GetAuthorizationToken",
    "codeartifact:GetRepositoryEndpoint",
    "codeartifact:ReadFromRepository",
    "sts:GetServiceBearerToken"
  ],
  "Resource": "*"
}
  1. Verify configuration:
devo config get codeartifact.region
devo config get codeartifact.account_id
  1. Use AWS SSO:
aws sso login --profile my-profile
devo --profile my-profile codeartifact-login

Performance Issues

Slow Command Execution

Problem: Commands take long time to execute

Solutions:

  1. Disable version check:
export DEVO_SKIP_VERSION_CHECK=1
devo commit
  1. Check network connectivity:
ping api.github.com
  1. Use faster Bedrock model:
devo config set bedrock.model_id us.anthropic.claude-3-7-sonnet-20250219-v1:0

Large Diff Timeouts

Problem: Code review times out on large diffs

Solutions:

# Review smaller chunks
git add specific-files
devo code-reviewer

# Or increase timeout (if supported)
# Split large changes into smaller commits

Shell Completion Issues

Completion Not Working

Problem: Tab completion doesn't work

Solutions:

  1. Reload shell configuration:
source ~/.bashrc  # or ~/.zshrc
  1. Verify completion is loaded:
# Zsh
echo $_comps[devo]

# Bash
complete -p devo
  1. Reinstall completion:
# Add to ~/.bashrc or ~/.zshrc
eval "$(_DEVO_COMPLETE=bash_source devo)"  # Bash
eval "$(_DEVO_COMPLETE=zsh_source devo)"   # Zsh

Binary Issues

Antivirus False Positive

Problem: Antivirus flags devo binary as malicious

Solutions:

  1. Add exception in antivirus software
  2. Build from source:
git clone https://github.com/edu526/devo-cli.git
cd devo-cli
./setup-dev.sh
make build-binary
  1. Use Python installation:
pip install -e .

Binary Won't Execute

Problem: Binary fails to run

Solutions:

# Check if executable
ls -la $(which devo)

# Make executable
chmod +x $(which devo)

# Check for missing dependencies (Linux)
ldd $(which devo)

Getting Help

If you can't resolve your issue:

  1. Check documentation:
  2. Installation Guide
  3. Configuration Guide

  4. AWS Setup

  5. Enable debug output:

devo --help  # Check available options
  1. Report issue:
  2. GitHub Issues
  3. Include:
    • Devo version (devo --version)
    • Operating system
    • Error message
    • Steps to reproduce

Common Error Messages

NoCredentialsError

Cause: AWS credentials not configured

Fix: Run aws configure or aws sso login

AccessDeniedException

Cause: Insufficient IAM permissions

Fix: Check IAM permissions for Bedrock/CodeArtifact

ModelNotFoundException

Cause: Bedrock model not available in region

Fix: Use supported region (us-east-1) or different model

ValidationException

Cause: Invalid parameters passed to AWS API

Fix: Check the parameters in your command (e.g., filter expressions, table names)

ConnectionError

Cause: Network connectivity issues

Fix: Check internet connection and firewall settings

See Also