Docs / Safety / Permissions and Claude Code parity

Permissions and Claude Code parity

TiroAgents runs on your own Claude Code configuration. What is the same, what differs and what reaches you.

Written for v2.1.0 · updated 2026-11-20

TiroAgents acts like Claude Code with the same configuration. Only the integrations differ: the island and the minimalist dashboard, the configured roster of agents, the hire gate, and the surface where permission prompts are shown.

What is the same as a plain claude run

Tiro and every agent it hires start with the options built in permissions.mjs (claudeSessionOptions):

SettingValue
Settings loadeduser, project and local (so ~/.claude/settings.json, the folder's .claude/settings.json and settings.local.json)
Toolsthe full claude_code preset (Bash, PowerShell, NotebookEdit, TodoWrite, Skill, AskUserQuestion and the rest)
Permission modenot set by TiroAgents: Claude Code picks it from permissions.defaultMode, exactly as claude -p does. If your settings say bypassPermissions, the SDK's explicit opt-in is passed so that is honoured
Allow, deny and ask rules, additionalDirectoriesfrom your settings, evaluated by Claude Code
Hooks, MCP servers, plugins, skills, CLAUDE.mdfrom your settings (plus our own office MCP server and hire-gate hooks)
Model and effortnot pinned: inherited from your settings (specialists keep the model their roster entry names, such as sonnet, opus or haiku)
Environmentyour process environment; ELECTRON_RUN_AS_NODE and TiroAgents's own variables are removed; the env block of your settings is applied by Claude Code itself
Working folderyour home folder, or workDir in kiro.json, so project settings and CLAUDE.md resolve as they would from that folder

parity.test.mjs builds these options and asserts them.

What reaches you

Only a request that Claude Code itself would ask you about reaches the UI. Allow rules, deny rules, the permission mode and hooks have already been applied. The card shows the full tool input (the whole file for a Write, the edit for an Edit, the JSON for anything else) and Claude Code's reason, and offers:

Commands are never edited. An unanswered prompt waits (a log line every 10 minutes is only a reminder). Questions Claude asks with its question tool appear as a question card in the island; the dashboard shows the text and points you to the island. A terminal bridged to the office only has its ask decisions forwarded; it stands aside for the auto, bypassPermissions and dontAsk modes, and with no dashboard tab open the terminal asks in its own dialog. The bridge also honours your crossSessionInbound setting: with refuse or hold, messages typed in the dashboard are not injected into that terminal.

What differs from a plain claude run

  1. The UI. Prompts are answered in the dashboard or island, not a terminal dialog. The multiple-choice question card exists only in the island.
  2. The roster. Tiro's brief and the eight specialists (their prompts and tool lists) come from TiroAgents. A SOP note may only narrow a specialist's tool list. Roles called read-only have no Write or Edit tool in their definition; what any agent may run is decided by your permissions, not by the roster.
  3. The hire gate. Starting an agent requires your one-shot request_hire approval for that goal and prompt. The hooks only deny or adjust input, and never approve. A deny-only hook also refuses a Bash or PowerShell command that launches claude or the Agent SDK from Tiro's session.
  4. The plan-limit probe runs isolated (no settings, hooks or MCP servers) because it is a tiny internal query, not an agent.
  5. Our own MCP tools (request_hire, goals, reports, memory, scheduler_inbox) are pre-allowed for Tiro.
  6. Cost. Your hooks and MCP servers load for Tiro and for every hired agent, so each turn carries their extra tokens, as it does in a normal session.

Consequences you should know

{
  "permissions": {
    "deny": [
      "Read(~/.ssh/**)",
      "Write(~/.claude/settings*.json)",
      "Edit(~/.claude/settings*.json)",
      "Write(~/.claude/agent-office/**)",
      "Edit(~/.claude/agent-office/**)",
      "Write(~/AppData/Roaming/Microsoft/Windows/Start Menu/Programs/Startup/**)",
      "Write(~/Documents/WindowsPowerShell/**)"
    ]
  }
}