From download to
your first real task.
Install Rigbolt on your Mac, connect the AI client you already use, and confirm that it can inspect your own project. This is a real setup guide, not a feature tour.
Install Rigbolt on your Mac.
Use the official macOS installer. Keep the app running while your AI client uses local tools.
- Open the Rigbolt Downloads page ↗, or the verified download link provided with your purchase.
- Download the release that supports your Mac. If supplied as a DMG, open it and drag Rigbolt.app to Applications.
- Open Rigbolt from Applications and follow the first-run screens. Only approve macOS permissions that you understand and need.
Choose a project AI can access.
Rigbolt works inside a workspace on your Mac. Start with one folder you recognize—do not grant broader access than you need.
- In the first-run setup, choose Add a project (or Try the safe demo project).
- Select your development folder, such as a project containing
package.json,.git, or WordPress source. - Leave the default Projects Only access scope unless you deliberately need Full Mac Access. Continue to the workspace/Home screen.
Connect your AI client.
Web chat and desktop AI clients use different connection paths. Choose yours below. You only need to complete one.
ChatGPT Web → Rigbolt Cloud → Your Mac
Read the complete ChatGPT connection guide ↗
ChatGPT accesses your paired Mac through Rigbolt's public HTTPS MCP endpoint. Custom MCP connection options depend on your ChatGPT plan and workspace permissions.
- Keep Rigbolt open. In Rigbolt Connections or Settings → Connections & Remote, choose the managed Rigbolt Cloud connection and complete pairing/authorization.
- Verify that your device shows connected or online in Rigbolt.
- In ChatGPT, if your plan/workspace allows custom MCP apps, enable Developer Mode, create a custom MCP app, and enter Rigbolt as the name with the endpoint below.
- Complete the authentication flow, review the requested access, and make the Rigbolt connection available in your chat.
https://rigbolt.tophive.dev/mcpOfficial ChatGPT connection instructions ↗
Claude Web → Rigbolt Cloud → Your Mac
Read the complete Claude Web guide ↗
- Keep Rigbolt open and connect it to Rigbolt Cloud in the app. Complete pairing and confirm that it is online.
- In Claude, go to Customize → Connectors and add a custom Web connector.
- Name it Rigbolt, paste the HTTPS endpoint, choose the provider's supported authentication option, and authorize the connection.
- Enable the connector for your conversation; inspect the available tools before using them.
https://rigbolt.tophive.dev/mcpClaude Desktop → Rigbolt local bridge
Read Claude Desktop setup and checks ↗
For the local MCP connection, Cloud is not required.
- Install Claude Desktop and launch Rigbolt on the same Mac.
- In Rigbolt, open Connections and locate the Claude Desktop local client entry.
- Choose Rigbolt's Configure / Connect action and follow its on-screen status messages. The application updates the local MCP configuration.
- Restart Claude Desktop and open a new chat. Check that Rigbolt tools are available.
Cursor or Codex → Rigbolt local bridge
Cursor setup ↗ · Codex setup ↗
- Install and launch your chosen local client on your Mac.
- Keep Rigbolt open, then go to its Connections area.
- Choose Cursor or Codex and run the dedicated configuration action.
- Restart the client or start a new session, then inspect its available MCP tools.
Run a safe first task.
Start in read-only mode. This confirms the connection works without changing files.
- Open a new conversation in the AI client you connected.
- Make sure Rigbolt tools or its custom connector are available to that conversation.
- Copy the prompt below and send it to your AI assistant.
- Review the results against the actual project in Rigbolt. Ask for changes only after inspection succeeds.
Using Rigbolt, inspect my selected project. Tell me its root folder, detected stack, and key files. Do not modify any files or run destructive commands.Understand changes and approvals.
When you're ready for writes, Rigbolt follows its local access and approval settings. Its dedicated Git commit action requires explicit review.
- Open Rigbolt Live Sessions or History to see recent operations.
- For code changes, review files and diffs in Code Review.
- When Rigbolt requests approval, inspect the exact operation before accepting.
- After execution, verify the result using a build/test or direct inspection. Execution success alone is not verification.
Having trouble?
Start with these practical checks. You don't need to reset or delete Rigbolt data to troubleshoot a connection.
My AI client can't see Rigbolt tools
Confirm Rigbolt is running. For local clients, reopen Rigbolt Connections, check the client configuration status, restart the client, and try a new conversation. For web clients, verify Cloud pairing and that your AI plan supports the custom connector.
Cloud says the Mac is offline
Keep your Mac awake and Rigbolt open, verify the app's Cloud status, internet connection, and device pairing. The remote endpoint alone does not mean your Mac is reachable.
AI can connect, but can't access my project
Open Rigbolt Projects and confirm the folder is added. With Projects Only scope, unregistered folders are outside the allowed workspace. Also check macOS filesystem permissions.
An operation asks for approval
That can be intentional. Check the operation in Rigbolt, review the exact requested action, and approve only if it matches what you wanted. If the operation failed verification, inspect the failure before retrying.
I got the app but don't have an installer or activation details
Use your official product/download channel. The purchase receipt, licensing workflow, and installer distribution must be verified against the shipping release before final publication of these docs. Do not use a random third-party DMG.
Now build something real.
You have a connected Mac, a chosen project, and a verified first task. Start with a small change, review the diff, and confirm the result.
Prototype guide. Screens and purchase/entitlement steps require final release validation.