Permissions
Permissions decide whether a tool call is auto-allowed, denied, or escalated for user confirmation. They do not isolate processes, block network access, or limit credentials available to an allowed tool. See Security and Data Boundaries.
Approval Modes
- Ask Before Changes: AlphaBase reads and inspects freely, then asks before edits, commands, internet access, or work outside the project.
- Smart Approval: an independent safety review decides ordinary requests. An inconclusive review of a verified action within the project can pause for your decision; unsafe actions or unverified access can be blocked.
- Full autonomy: ordinary actions proceed without routine approval prompts. Explicit denials, protected paths, execution boundaries, and mandatory human confirmations still apply.
Ask Before Changes is the default. Explicit deny rules remain enforced in every mode. Full autonomy does not silently downgrade to Smart Approval.
New tasks and workflows capture their selected profile. Changing the default does not retroactively change running work. On desktop, use the permission selector below the composer, or Settings → Permissions for the default and saved project approvals.
Actions
allow: run automaticallyask: require user approvaldeny: block execution
Rule Shapes
You can set a single action:
{ "permission": "ask"}Or per-permission rules:
{ "permission": { "*": "ask", "read": "allow", "edit": "deny" }}Or granular pattern rules:
{ "permission": { "bash": { "*": "ask", "git *": "allow", "rm *": "deny" }, "edit": { "*": "deny", "docs/*.md": "allow" } }}Matching Semantics
- wildcard matcher supports
*and? - rules are evaluated with last-match wins semantics
- a trailing
" *"in patterns is treated as optional argument tail
Bash grants and one-time approval identity retain the command text, including
quoted whitespace, escapes and here-document content. Different command text
can require a separate approval; it is not rewritten into another shell command.
For compatibility, deny and ask rules also recognize the previous horizontal
spacing form. That fallback cannot create an automatic allow.
Permission Keys
Schema-defined keys include:
readedit(covers write/edit/patch/multiedit behavior)globgreplistbashtaskexternal_directorytodoreadtodowritequestionwebfetchwebsearchcodesearchlspdoom_loopskill- plus additional tool IDs via catch-all
Home Expansion
Permission patterns expand:
~/...$HOME/...
before evaluation.
Risk Guardrails (Hard Overrides)
Before normal rule matching, AlphaBase applies risk checks:
- catastrophic bash signatures require explicit human confirmation
- writes to protected system/security paths are denied
- mutating operations outside workspace boundaries escalate to approval
Smart Approval can resolve ordinary requests automatically or require a decision for an inconclusive review of a verified project action. Full autonomy permits ordinary actions within the applicable authority and execution boundaries. Risk policy and explicit deny rules can override an allow rule.
External Directory Boundary
Paths outside the workspace require explicit approval/allow via external_directory patterns.
{ "permission": { "external_directory": { "~/projects/personal/**": "allow" } }}Approval Outcomes
When prompted, users choose:
oncealwaysreject
always persists scoped approval rules and can unblock matching pending requests in the same session. Desktop separates one-time approval from Remember…: expand Details to review the action, safety review, environment, and scope, then check the exact matching targets before saving approval. Revoke saved project approvals in Permissions settings when they are no longer needed.
Agent-Level Overrides
agent.<name>.permission merges over global permission policy for that agent.
{ "permission": { "bash": "ask" }, "agent": { "alpha-v3": { "permission": { "bash": "allow" } } }}