Browse documentation topics
Permissions and safety
Understand access scope, Personal policy, approvals and what Rigbolt cannot guarantee.
Product documentation · Rigbolt v0.1.1 · Updated October 2026
Access boundaries
Projects Only is the default; remembered roots define allowed workspace paths for managed operations.
Full Mac Access is opt-in and cannot exceed the logged-in macOS user's existing rights.
macOS privacy/Accessibility prompts and filesystem permissions remain authoritative.
Personal vs Controlled policy
Routine Personal-mode developer operations are low-friction and should not request repeated Rigbolt approval ceremony.
Special or higher-risk tools can require a deliberate review. Dedicated commit review asks once.
Controlled-mode compatibility protections may require stricter approvals; access scope and execution policy are separate.
Remote security
Cloud authenticates and relays web MCP requests. It does not replace local execution authority.
Only pair devices through Rigbolt's trusted managed flow. Never paste access tokens or pairing secrets into chat.
Production mobile approvals require a separately enabled, passkey-protected workflow and exact local approval.
Limits of an unrestricted shell
Real developer shells can invoke scripts and descendant programs with Mac-user permissions.
Project scope is not a complete OS sandbox for arbitrary shell commands.
Review risky commands and untrusted repositories before executing them.