Common issues and how to resolve them.

Hooks don’t fire at all

The most common cause is the VS Code setting isn’t enabled.

Go to VS Code → Settings → Extensions → Cline → Features → Enable Hooks and make sure it’s on. Then restart Cline.

Also verify:

  • Your Cline version is v3.36 or newer (earlier versions don’t have the hook system)
  • .clinerules/hooks/ exists in your project root with scripts for each event
infinium-cline status
# "Hooks: .clinerules/hooks" should appear

If not, re-run:

infinium-cline init
# Choose [2] Reconfigure hooks

Cline appears to hang or freeze

Cline waits for every hook invocation to write a JSON response on stdout. If the hook crashes before writing, Cline will hang.

The connector is designed to always write a response, even on internal error. If you see hangs, check the error log:

infinium-cline errors

Recent errors may reveal the cause (e.g. corrupt session file, keyring access denied).

infinium-cline command not found

The infinium-cline executable is installed to Python’s Scripts directory, which may not be on your system PATH.

Quick fix — use the module directly:

python -m infinium_cline_connector <command>

Permanent fix — add Python’s Scripts directory to your PATH:

  • Windows: Add C:\Users\{you}\AppData\Local\Python\{version}\Scripts to your system PATH via Environment Variables
  • macOS/Linux: Usually works automatically. If not, check python -m site --user-base and add the bin subdirectory to your shell profile

infinium-cline test fails with authentication error

Connection failed: 401 Unauthorized

Your agent ID or secret is incorrect. Update them:

infinium-cline update-credentials

Make sure you’re using the agent secret (not your personal API key) from the Infinium platform. You can generate one at Settings > API Keys > Agent tab.

infinium-cline test fails with connection error

Connection failed: Connection refused
  • Check your internet connection
  • Verify the API URL: infinium-cline status shows the current URL
  • If using a custom base URL, make sure it’s correct

Traces not appearing in Infinium

  1. Check if tracing is paused:
infinium-cline status

If it shows PAUSED, resume with infinium-cline resume.

  1. Check if hooks are installed:
infinium-cline status
# Look for "Hooks: .clinerules/hooks"

If missing, re-run infinium-cline init and pick [2] Reconfigure hooks.

  1. Check for failed traces:
infinium-cline status
# Look for "Pending retry: N failed trace(s)"

infinium-cline retry
  1. Check the error log:
infinium-cline errors

Token usage missing from traces

The connector reads token usage from Cline’s ui_messages.json, which lives in VS Code’s global storage for the saoudrizwan.claude-dev extension:

  • Windows: %APPDATA%\Code\User\globalStorage\saoudrizwan.claude-dev\tasks\<taskId>\
  • macOS: ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/tasks/<taskId>/
  • Linux: ~/.config/Code/User/globalStorage/saoudrizwan.claude-dev/tasks/<taskId>/

If token data is missing, the file may not yet have been written, or the extension ID has changed upstream (rare). Check that the path exists for the task you’re tracing.

Wrong agent receiving traces

If you have per-project configs and traces are going to the wrong agent:

# Check which config is active in the current directory
infinium-cline status
# Look at "Config from:" line
  • Config from: project (...) — using project-level config
  • Config from: environment variables — env vars are overriding

To set up project-specific credentials:

cd /path/to/your/project
infinium-cline init

Keyring errors on Linux

If you see warnings about keyring not being available, your system may not have a secret service running.

Option 1: Install a secret service:

# Ubuntu/Debian
sudo apt install gnome-keyring

# Or use KDE Wallet
sudo apt install kwalletmanager

Option 2: Use environment variables instead:

export INFINIUM_AGENT_SECRET="your-secret"

Stale session files

If temporary session files accumulate (e.g., after crashes):

infinium-cline cleanup

This removes session files older than 30 minutes. Adjust with --max-age:

# Remove files older than 10 minutes
infinium-cline cleanup --max-age 600

Reinstalling after uninstall

pip install infinium-cline-connector
infinium-cline init
infinium-cline test

Your previous keyring credentials may still exist. The setup wizard will detect them and offer to reuse or update.

Don’t forget to re-enable hooks in VS Code if the setting got turned off.