Troubleshooting

1. Fully quit the AI app (⌘Q) and open it again. Closing the window isn't enough.
2. In RADIQ, open Connections → AI tools and check the app shows as connected. If not, click Connect (or Retry). Claude Code isn't listed there; connect it with one command.
3. Start a new chat or session. Existing ones keep the tools they started with.

Reconnect from RADIQ (Connections → AI tools → Connect) and restart Claude. Connecting from the app uses the copy of Bun bundled with RADIQ and includes your key, which avoids the slow first start that causes this error. If you set it up by hand, make sure Node.js is installed and RADIQ_LOCAL_API_KEY is in the config.

Open the RADIQ app. The tools talk to RADIQ on your computer, so it must be running. Check the RADIQ icon is in your menu bar.

Your RADIQ key changed, for example after Regenerate key.

• Claude Desktop, Cursor, OpenClaw, Windsurf: quit and reopen RADIQ, which writes the new key into them, then restart the AI app.
• Codex, Hermes: in Connections → AI tools, disconnect the app and connect it again, then restart it.
• Claude Code or anything you connected by hand: copy the new key from Settings → Privacy and replace the old one. See Claude Code.

The ChatGPT chat app can only use connectors hosted on the internet, not ones running on your computer. Use Codex with your ChatGPT sign-in instead. See Connect your AI.

Make sure Node.js is installed (node -v in Terminal) and RADIQ is running. Then run /mcp in Claude Code to see the error. If your key changed, remove and re-add the server as described in Claude Code.

1. Click the RADIQ menu bar icon. If you see Fix permissions, click it.
2. Otherwise open System Settings → Privacy & Security → Screen Recording and check RADIQ is on.
3. Quit and reopen RADIQ. macOS only applies Screen Recording after a restart.

Check it isn't excluded in Settings → Privacy → Content filters, either directly or through a category such as personal messaging. Private and incognito browser windows are skipped on purpose.

Open Settings → Disk & retention to see what's using space, and set a storage policy that drops video and audio after a number of days while keeping the text. See Delete your history.

• Check recording is on: the RADIQ menu bar icon shows whether it's recording.
• Check permissions in System Settings → Privacy & Security: Screen Recording, Accessibility and Microphone must be on for RADIQ.
• Ask your AI to run RADIQ's health-check. It reports whether screen and audio capture are working.
• Be specific: give the app, a time window, or a distinctive word.

Make sure microphone permission is on, and check the meeting appears under Meetings in the app. To record one RADIQ didn't detect, click new meeting there. If a transcript came out wrong, open the meeting and use retranscribe meeting. See Meetings.

Add the RADIQ skill. It tells your AI to keep "seen on screen" apart from "done" and to link the moments it used, so you can check.

• RADIQ must be running and your computer awake at the scheduled time.
• Ask your AI: "list my RADIQ automations". Check it shows on and the schedule is what you expect.
• If you wrote a cron schedule with weekday numbers, switch to names, for example 0 9 * * MON-FRI.
• Ask: "show the logs for my daily recap automation" to see the last runs and any error.

The AI provider was overloaded for a moment. RADIQ already retried once. Run it again in a few minutes, or ask your AI to. Scheduled runs try again at their next time.

Automations run with the AI model chosen for that automation (RADIQ Cloud by default). Make sure you're signed in to RADIQ, or pick another AI preset on the automation's card under Automation.