Approvals

Every write and shell command can pass through an approval gate. You see the path or command before it runs.

What you see

  • Divider-style code / diff previews (not heavy boxes)
  • Clear action: create, edit, delete, shell
  • Relative path inside the workspace

Choices

  • Allow once - apply this change
  • Always this session - auto-allow similar actions until exit
  • Deny - skip; the agent gets a denial result and should adapt

Modes

ModeMeaning
askAsk before changes (default)
autoTrust this workspace - fewer prompts
safeStrict / safe-oriented behavior for the workspace

Override for a single launch:

export VRITRA_APPROVAL=ask    # or auto | safe
export VRITRA_RESET_TRUST=1   # forget cached folder trust

Persistence

Trust is stored per project in .vritraai/trust.json. Central config (keys/models) lives in ~/.config-vritrasecz/vritraai/config.json.

When to deny

  • Unexpected paths or mass deletes
  • Shell unrelated to the task
  • Installers / privilege escalation you did not ask for
  • Network calls that look wrong for the objective

Dangerous shell patterns are classified and may be blocked or re-prompted even before you decide.