Your machine.
Your boundaries.
Rigbolt bridges AI clients to local developer tools without moving your entire workspace into a hosted IDE. Learn which permissions are yours to control.
Choose what AI can reach.
Projects Only is the default. Rigbolt uses the folders you add as allowed workspaces. Full Mac Access is optional and accepts explicit paths within the macOS account's existing permissions.
AI request → Mac policy → Execution
Cloud authenticates and relays remote client traffic. Rigbolt on your Mac decides what to allow, checks permissions, runs operations and records the observed outcome.
Four principles
Personal mode01 / Your access scope
Choose Projects Only or Full Mac Access. Neither choice bypasses macOS permissions, grants root privileges or automatically exposes secrets.
02 / Your AI client
Authenticate remote clients through OAuth when using Cloud. Local MCP clients can connect directly where supported. Cloud is optional for local-only development.
03 / Permission-aware work
Routine Personal-mode developer actions are intentionally low-friction. Sensitive capabilities can still require explicit approval under local policy.
04 / Results are verified
Finishing a command is not proof of the desired outcome. Rigbolt records execution and verification separately where supported.
Understand the limits
Does Projects Only isolate every shell command?
No. An unrestricted developer shell is not an operating-system sandbox. The Mac user account and existing macOS permissions remain the boundary. Review commands and scripts before running untrusted code.
Does connecting Cloud give it control over my Mac?
Cloud provides authenticated routing for supported clients. Local Rigbolt retains the capability checks, policy, execution, activity and applicable approval flow. Keep pairing details and tokens private.
Do I have to approve every tool call?
No. Routine Personal mode work is designed to be low-friction. More sensitive actions may require explicit approval depending on tool policy and mode.
What information should I never share?
Passwords, access tokens, OAuth credentials, private keys and device-pairing secrets. Do not include them in screenshots, logs or support requests.
Need help with a permission prompt?
Start with the connection and approval guides.