Troubleshooting

Rigbolt will not open

Confirm the installer source and checksum.

Check the supported Mac architecture and version.

For ad-hoc development builds, macOS may warn that the application is not notarized. Do not bypass a warning on an untrusted file.

If a release is not published, do not assume a download button is broken; check the official Downloads page.

AI client says Rigbolt is offline

Check that Rigbolt is running and the Mac is not asleep.

For web clients: confirm the device is paired to Cloud, connected, OAuth authorized and the connector enabled.

For local clients: confirm Rigbolt's configuration status and restart the client.

Check Rigbolt Live Sessions/History for a specific error rather than repeatedly re-pairing.

Tools do not appear

Verify whether your AI account/workspace permits custom MCP tools or write tools.

Confirm the app/connector was enabled for this conversation.

For Claude Desktop/Cursor/Codex, check the local config status and restart the client.

Try listing capabilities before requesting edits.

Permission denied or project not found

Open Projects and confirm the exact folder is added.

Check Settings → Access Scope; Projects Only does not expose unregistered folders.

Check Mac permissions and the selected project identity.

Do not work around blocked secret files or denied protected operations.

Command, build or Git operation failed

Read the exact exit code and stderr.

Verify the current directory, dependencies and runtime versions.

Inspect changed files and Code Review; fix the specific failure and rerun.

For commit errors, recheck the staged snapshot and dedicated approval request.

Contact support

Include macOS version, Rigbolt version, AI client, the step that failed, and a sanitized error message.

Never send passwords, API tokens, OAuth data, signing keys, pairing codes or private source files.

Contact Rigbolt support ↗