Global Support

Troubleshooting

Solutions for common technical hurdles. If your issue persists, our intelligence team is always available via the GitHub repository.

Empty Diff Detection

Common Issue

Symptom Identified

GitSage exits with: No staged changes found.

Root Cause

The intelligence engine requires specific files to be staged before it can analyze your intent.

Recommended Resolution

bash

12345678

# Stage specific files
git add src/auth/middleware.py
# Or stage all modified files
git add -A
# Then run analysis
gitsage

Network Issue

Symptom Identified

ReadTimeout: GitSage API did not respond within 30 seconds.

Root Cause

Network instability or transient provider disruption. GitSage includes built-in retry logic but defaults to a 30s timeout.

Recommended Resolution

bash

12345

# Switch to localized privacy mode (Ollama)
gitsage --provider local
# Or increase global timeout threshold
gitsage config --timeout 60

Auth Issue

Symptom Identified

Error: GITSAGE_API_KEY is invalid or missing status 401.

Root Cause

The secret key provided is either malformed, expired, or has insufficient quota.

Recommended Resolution

bash

12345

# Verify your environment state
gitsage config --provider gitsage --key YOUR_KEY
# Get a fresh key from the portal:
# https://gitsage.dev/dashboard