Overview
Parsaa’s agent works by calling tools — to read code, edit files, run builds, and more. You control this on two independent axes:- Permissions — whether a category of action runs freely, prompts you, or is blocked.
- Enabled tools — which individual tools are available at all.
Capabilities
Every tool belongs to a capability bucket. Permissions are set per capability, not per tool.Permission Modes
Each capability is set to one of three modes:Defaults are safe: Read & search is Allow (read-only runs freely), and every mutating capability (edit, git, run commands, build) defaults to Ask.
The approval prompt
When a capability set to Ask is invoked, Parsaa pauses and shows an inline approval card with a preview of the exact action (e.g. the shell command or file path). You choose:
“Allow for session” upgrades Ask → Allow for that capability until the session ends.
Enabling & Disabling Tools
Separately from permissions, you can turn individual tools on or off in Settings → Extensions → Tools:- Built-in tab — toggle each built-in tool; a
?shows its description. New tools appear automatically. - MCP tab — tools grouped by server (see MCP Tools).
- Bulk Enable All / Disable All, plus search.
Built-in Tool Reference
Sub-agents get their own tool allowlist and their own per-capability permission matrix, so you can make a sub-agent stricter than the main agent. See Sub-agents.