Approvals & Guardrails

TheGitAI is built so that nothing happens to your files or shell without your say-so.

Approvals

• TheGitAI asks before running shell commands or applying file edits.
• At each prompt: y approves once, a approves the rest of the session, n denies.
• -y / --yes at startup auto-approves every shell command and file edit for the whole session — use it with care.

Password prompts

If an approved sudo command needs a password, the terminal UI shows the exact command and keeps the password masked and local. The password is never sent to the model or the server.

Guardrails

• Repo containment — file and shell operations are confined to the target repo root.
• Ignore rules — vendor, generated, and sensitive directories (like .git, node_modules, and build output) are never indexed.
• Command safety — shell commands require confirmation unless -y is used, and managed background jobs remain visible and controllable through /jobs.
• Write freshness — edits are checked against freshly read file content so the agent cannot silently overwrite a newer version it did not inspect.
• Recovery — assistant edits are journaled, and checkpoint restore refuses to overwrite unknown current content.

Long-running commands such as dev servers and watchers run as managed background jobs. They require the normal command approval in Default mode and are unavailable in read-only Plan mode.