Projects and Access Scope

Choose exactly which development folders your AI can work with, then confirm the scope and current project context.

Product documentation · Rigbolt v0.1.1 · Updated October 2026

01 / Workspace

Add a project

Open Rigbolt → Projects and add a folder containing your development work.
Choose a specific path; Rigbolt can remember a project alias, its stack and instructions such as AGENTS.md.
In Home/Projects, confirm the folder is registered before allowing a client to inspect it.

Important — A project is an actual path on your Mac. The example filenames in the docs are illustrative.

02 / Workspace

Projects Only is the default. It limits Rigbolt's managed filesystem/workspace operations to remembered project roots.

Full Mac Access is optional; it accepts explicit user-accessible absolute paths without registration. It does not bypass macOS permissions.

Access Scope is separate from the Personal vs Controlled policy modes and does not turn the real developer shell into an OS sandbox.

Important — Prefer Projects Only until you understand the risks of broader access.

03 / Workspace

Choose a registered test project.

Ask: Inspect the selected project, list its main files, describe the structure, and propose the next step. Don't modify files.

Confirm the results in the actual folder and Rigbolt Live Sessions.

Important — Inspect the selected project. Explain its structure and suggest the safest next step. Don't edit any files yet.