Troubleshooting
Common issues and how to resolve them.
Installation
CLI not found after install
Problem: Running intentra returns "command not found"
Solution: Add the install directory to your PATH:
export PATH="$HOME/bin:$PATH"
Add this line to ~/.zshrc or ~/.bashrc to persist.
Permission denied
Problem: Install script fails with permission error
Solution: Run with elevated permissions:
sudo curl -fsSL https://install.intentra.sh | sh
Hooks
Hooks not firing
Problem: No events captured when using AI tools
Solution:
- Check hook status:
intentra hooks status
- If not installed, reinstall:
intentra install cursor
- Restart your IDE
IDE not detecting hooks
Problem: Hooks installed but IDE doesn't trigger them
Solution: Restart your IDE after installing hooks. Some tools require a full restart (not just reload).
Authentication
Login not working
Problem: Browser doesn't open or device code fails
Solution: Use manual login:
intentra login --no-browser
Then visit the displayed URL manually.
Token expired
Problem: Commands fail with authentication errors
Solution: Re-authenticate:
intentra logout
intentra login
Sync
Scans not syncing
Problem: Scans captured locally but not appearing in dashboard
Solution:
- Check auth status:
intentra status
- Force sync:
intentra sync now
Device not showing
Problem: Device missing from dashboard
Solution: Verify device registration:
intentra status
If no device ID shown, re-login to register:
intentra logout
intentra login
Scan Aggregation
Scans split incorrectly
Problem: Single task shows as multiple scans
Causes:
- Paused >30 seconds between actions
- Tool sent explicit "stop" signal mid-task
- Switched files (detected as context switch)
Solution: If this happens frequently, contact support to adjust aggregation rules for your workflow.
Scans merged incorrectly
Problem: Two separate tasks show as one scan
Causes:
- Tasks started within 30 seconds of each other
- Same file edited twice quickly
Solution: Wait 30 seconds between unrelated tasks, or switch files to signal a new task.
Duplicate scans from same session
Problem: Seeing both "Cursor" and "Claude Code" scans for the same work session
Cause: Cursor's "Third-party skills" feature loads hooks from ~/.claude/settings.json. When enabled, Cursor fires both its native hooks and Claude Code hooks, creating duplicates.
Solutions:
- Update CLI (recommended):
intentra update
The latest CLI automatically detects and merges duplicate events.
-
Disable Third-party Skills:
- Open Cursor Settings
- Navigate to Features → Third-party skills
- Disable the toggle
- Restart Cursor
-
Uninstall Claude hooks (if only using Cursor):
intentra uninstall claude
Debug Mode
Enable debug mode to diagnose issues:
intentra -d status
Or add to ~/.intentra/config.yaml:
debug: true
Debug mode shows:
- HTTP requests:
[DEBUG] POST https://api.intentra.sh -> 200 - Local saves:
[DEBUG] Saved scan locally: scan_abc123 - Saves scans to
~/.intentra/scans/for inspection
Still stuck?
- Check status:
intentra status - Verify hooks:
intentra hooks status - Enable debug:
intentra -d status - Contact support at intentra.sh