Permissions

Tarsk includes permission gates that keep the agent from running dangerous or unexpected operations without your approval.

Shell Command Approval

When the agent calls the bash tool, Tarsk may pause and show an approval prompt before executing the command. Review the full command, then choose Allow or Deny.

Shell commands run in the branch’s working directory with the project’s environment variables applied.

Web Fetch Approval

When the agent calls the fetch tool to retrieve a URL, Tarsk may show a permission prompt listing the URL and domain. Pre-approved domains may skip the prompt.

You can allow or deny each fetch individually. Denied fetches return an error to the agent so it can try an alternative approach.

Confirm Commands (Project Setting)

Each project has a Confirm Commands toggle in Project Settings:

Setting	Behaviour
Off (default)	Bash, skill scripts, and browser shell calls run without per-command approval
On	Each command requires explicit approval before running

When confirm commands is enabled, define allowed command patterns — commands matching these patterns (e.g. npm test, git status) run automatically without prompting.

You can also toggle Confirm commands temporarily from the chat mode selector menu (hammer icon next to the input). This updates the project setting for the current session.

Sandbox (macOS)

When Sandbox is enabled in app-wide settings or the mode selector menu, bash and skill script execution runs inside a macOS seatbelt sandbox. See General Settings.

Skill Script Permissions

Scripts in skill scripts/ directories run through the same approval gate as bash commands when confirm commands is enabled.

Related

• Project Settings — confirm commands and env vars
• Chat — where approval prompts appear
• Skills — skill scripts subject to the same gates