MRigboltDocumentation
Browse documentation topics
Using Rigbolt / Rigbolt for Mac

Terminal and processes

Run real developer commands with Rigbolt's native shell, and monitor long-running tasks.

Product documentation · Rigbolt v0.1.1 · Updated October 2026

01 / Using Rigbolt

Use the real shell

Select a project in Rigbolt before invoking commands.

Ask for a specific command such as git status, pnpm typecheck or npm test.

Review the output, exit status and affected files rather than accepting a model summary alone.

Important — Personal mode provides real zsh behavior, including scripts and shell composition. It is not an OS-level sandbox.
02 / Using Rigbolt

Track development processes

Start an allowed dev server or test watcher from your project.

Inspect the running process and its output through Rigbolt's process/session controls.

Stop a process you no longer need. Check for conflicts before starting another server on the same port.

03 / Using Rigbolt

Manage command risk

Avoid executing copied internet commands you have not reviewed.

Understand that a shell subprocess may access resources permitted to the logged-in Mac user.

Sensitive or host-level operations may be blocked or require explicit policy review.