Permissions
10. Permissions
Modes
In Settings → Permissions:
| Mode | Behavior |
|---|---|
| Ask on every site | Asks on the first action on each domain |
| Allow actions automatically (recommended) (default) | Does not ask; respects the block list |
| Block actions | Read-only; no interaction is executed |
What never asks for permission
Reading and background work: listing tabs, opening a tab, reading the page, finding an element, extracting text, reading the console, reading the network, resizing the window and recording GIF frames. Starting and stopping GIF recording also do not ask.
The permission card
When an action needs approval, the card appears over the panel and shows:
- the host in evidence, with an alert dot;
- what will be done (“Navigate from a.com to b.com”, “Click on the page”, “Fill field ref_3”, “Run JavaScript in the page”…);
- details: tab title, destination URL, value that will be typed (up to 2,000 characters), file names;
- a preview (screenshot) when one exists;
- the conversation name, if the request comes from another conversation (“Session: …”).
The options:
| Button | Effect |
|---|---|
| Allow once (Enter) | This action only |
| Allow for this session | Releases the host for as long as that conversation exists (kept in memory only) |
| Always allow for example.com | Saves the host to the allow list |
| Deny (Esc) | Refuses the action |
Cross-domain navigation and plan requests have their own buttons: Allow / Always allow for … / Refuse, and Approve plan / Refuse.
The card's footer reminds you: “You can revoke permissions in Settings. The agent must never buy, create accounts or bypass captchas without your confirmation.”
Time to answer
The default is 60 seconds. If you do not answer, the action is denied. The time can be changed in Settings (30 s, 1 min, 2 min, 5 min).
With the panel closed
The request becomes a system notification (“OpenCode Browser: pending approval”) and plays a sound alert. Clicking the notification opens the panel with the request already on screen.
Several conversations asking at the same time
Requests go into a queue: the one from the conversation you are viewing appears first; once you answer, the next one comes in — with the name of the originating conversation. Nothing is lost or expires hidden, and when you reopen the panel all pending requests reappear.
While a card is open it covers the panel, including when it comes from another conversation. To release it quickly, use Esc (deny) or answer it.
Allow and block lists
In Settings → Permissions:
- Always allowed sites (one per line)
- Always blocked sites (one per line)
The block list is evaluated before everything else: if the host is on the block list, not even the “allow automatically” mode releases it.
The format is just the host, lowercase, exactly as it appears in the address bar — no https://, no path, no port and no wildcard:
| Entry | Works? | Why |
|---|---|---|
github.com | Yes | It is the host |
docs.github.com | Yes | A subdomain is another host (it needs its own line) |
localhost | Yes | Host without a port |
https://github.com | No | The scheme is not part of the host |
github.com/repo | No | A path is not part of the host |
*.github.com | No | There is no wildcard |
GitHub.com | No | The comparison is case-sensitive |
Each line is compared by equality. Typing https://… does not show an error on screen, but it has no effect — it is worth checking after saving.