Browse documentation topics
Technical reference and limits
A concise map of what Rigbolt does, what depends on your client, and what is not included.
Product documentation · Rigbolt v0.1.1 · Updated October 2026
Architecture
Supported web AI client → authenticated Rigbolt Cloud relay → paired Rigbolt on Mac → files, real zsh, processes, Git, build/test and browser tooling.
Local desktop AI client → Rigbolt bundled stdio bridge on the same Mac.
Cloud, managed project tools, and the native macOS user account remain distinct security boundaries.
Usage and plans
Rigbolt's Personal/Owner runtime has no enforced Rigbolt tool-call quota or monthly credits.
Your AI service provider controls model usage, custom MCP feature availability and plan limits.
Rigbolt's remote usage counter is informational for Personal/Owner; local calls are not billable usage events.
Access scopes
Projects Only: remembered roots define allowed paths for managed workspace operations.
Full Mac Access: optional explicit user-accessible absolute paths, still limited by macOS permissions.
The real shell is not an OS security sandbox.
Current release notes
Documentation describes the 0.1.1 codebase. Exact installer availability and signing status must be read from the Downloads page.
Paid checkout, distribution entitlement, notarization and release availability must be tested independently before describing them as generally available.