[httpsphl]

What

A bot asked again for the same command or site every time. Now the owner can allow a request for good, and the bot stops asking for it (spec 10.1; roadmap item 18.3).

What it covers. The daemon decides from the tool and its input, and sends the result as always on the approval item. It is null when the request cannot be allowed for good.

Tool	"Always" covers
Bash, PowerShell	that exact command (up to 2 000 characters; a longer one is a script, worth reading each time)
WebFetch	the site, and its subdomains, as in the browser (21.5)
Read, Write, Edit, MultiEdit, NotebookEdit	that file
WebSearch	every search
anything else (plan, suggestion, routine, browser, unknown)	nothing: it always asks

Daemon

• approvals.answer takes always: true. With it, the request is kept in allow_rules (migration 0014) and bot.rules is sent. The scope is read from the chat item, because the stored input may be cut short.
• permission_prompt checks the bot's rules after the running-tool check. A request a rule covers is allowed at once: no approval item and no needs_approval.
• rules.list and rules.delete show and remove a bot's rules. Deleting the bot deletes its rules too.

App

• The request card gets a third button that says what it covers ("Permitir sempre este comando", "Permitir sempre em example.com", "Permitir sempre neste arquivo"). Its hint says the bot will not ask again and that it can be undone in the details.
• The bot's details end with "Permitido sem perguntar". Each rule shows the action and the command, site or file, with an X that makes the bot ask again.

Checks

• Rust: cargo fmt, clippy -D warnings and cargo test --workspace pass. New tests:
  • store: rules kept once per bot, removal, and deletion with the bot;
  • unit: what each tool's scope covers, and that a site covers its subdomains;
  • tests/allow_always.rs: allowed always, the same command no longer asks and another command still does; list, delete, and it asks again; a site rule covers other pages; a plain Allow keeps no rule; a plan has no always.
• App: pnpm check passes (272 tests). allowAlways.test.tsx covers the button, the call with always, the rule in the details and its removal, the site label, and no button for Glob.
• Preview (pt-BR): "Permitir sempre este comando" on a request turns it into "Permitido: rodar um comando", and the command appears under "Permitido sem perguntar" in the details.

Still to see (real Claude Code)

Nothing new is asked of Claude Code: a request a rule covers gets the same {"behavior":"allow"} an answered one gets. To check with a real bot:

1. Ask the bot to run git status twice.
2. Answer "Permitir sempre este comando" on the first request.
3. The second run should go through without a card, and the bot should not show "Precisa de aprovação".