Approvals
You decide what an agent may reach or run, and how much odette asks you about it. This page covers the gates, their modes, and how to answer what an agent asks.
odette checks two things an agent can do outside its container:
- Egress: any network connection. The container has no other way out.
- Commands: shell commands an agent asks odette to run on your machine. These run as you, outside the sandbox, so they can touch anything you can.
Each has its own gate, and each gate has a mode.
Gate modes
Section titled “Gate modes”| Mode | What happens to a request odette hasn’t been told about | Risk |
|---|---|---|
| manual | Held until you allow or deny it. | Lowest. You see everything; agents wait for you. |
| judge | An AI judge allows or denies it. If the judge is unsure, it is held for you, with the judge’s risk score and reasoning. | The judge can allow something you would not have. |
| yolo+judge | The judge can deny. If it is unsure, the request is allowed once without asking you. | Anything the judge doesn’t flag gets through unattended. |
| yolo | Allowed. No checks. | The agent can reach any host, or run any command on your machine. |
Both gates start in judge. The judge allows routine requests, denies clearly harmful ones, and holds the rest for you. Each request no rule covers costs one judge call, billed to the Claude subscription or API key of the session’s profile. If the judge cannot run (no sign-in, no network), the request is held for you, never allowed. A mode you have set yourself is kept.
A command runs on your machine rather than in the sandbox, so you may want manual for commands and judge for egress. Use yolo only for a session you are watching.
Some requests are never decided by the mode:
- A host on a deny list is refused in every mode, yolo included.
- A command that could write to a project’s
.odette/folder or to odette’s own data folder, or that runs anodettecommand which changes settings, gates or credentials (odette gates egress yolo,odette config set,odette kit apply, starting or building another odette session, …), is always held for you, whatever the mode or allowlist. You can only allow it once. This keeps an agent from granting itself more access through you. If such a command slips past the check, odette still refuses it unless you approved that run.
Changing the mode
Section titled “Changing the mode”- Dashboard: the Gates panel on the left has a four-step dial each for Commands and Egress. A change applies at once and is remembered.
- One session: in the Sessions zone, select the session and set
Gates for this session (
inheritfollows the global dial). From the terminal:odette gates commands judge --session <name>, and... inherit --session <name>to follow the global mode again. A session’s mode lives in the running daemon, so this needs it.odette gateslists the sessions that have their own mode. - Command line:
odette gatesshows both;odette gates commands judgeorodette gates egress judgesets one. Values:manual,judge,yolo+judge,yolo. Like the dial, a change applies at once and is remembered. - Environment:
ODETTE_JUDGE=1(judge) orODETTE_YOLO=1(yolo) sets both gates when the daemon starts, overriding the saved modes.ODETTE_JUDGE_MODELchooses the model the judge uses.odette gatesandodette config getname the ones set in your shell.
To try the judge on a single request, use odette debug judge. It is a hidden
diagnostic command, so odette --help does not list it:
odette debug judge "rm -rf build/"odette debug judge --egress example.com:443Allowing and denying hosts
Section titled “Allowing and denying hosts”Held egress requests appear in the dashboard’s Overview and Inbox.
| Choice | Effect |
|---|---|
| Allow once (Overview) / Allow Once (Inbox) | This connection only. |
| Allow In this project | Added to .odette/domains.allow. |
| Allow Every project | Added to ~/.odette/egress/global.allow, for every project. |
| Deny (Overview) / Deny Once (Inbox) | Refuses this connection only. |
| Deny In this project | Added to .odette/domains.deny. |
| Deny Every project | Added to ~/.odette/egress/global.deny. |
An entry covers the host and all its subdomains. You can also edit these files
by hand (one host per line, # for comments), add and remove entries in the
dashboard’s Rules zone, or use odette rules (below).
Rules from the command line
Section titled “Rules from the command line”odette rules lists what the dashboard’s Rules zone shows: the commands
you allowed in a folder, the egress rules (for every project and for the
project you are in), and the repositories odette may read with your GitHub
login.
odette rules egress add api.example.com # allow for this projectodette rules egress add api.example.com --global # allow for every projectodette rules egress add ads.example.com --deny # deny (add --global for every project)odette rules egress add pypi.org --inspect # inspect (always every project)odette rules egress rm api.example.com # same flags select the listodette rules commands rm "make test" # --dir <folder> if several folders allow itodette rules github rm owner/repo # in every scopeGranting a command or a login stays in the dashboard’s approvals. An agent cannot change rules on its own: its host command that runs one of these is held for you.
A request that nobody answers is denied after approval_timeout seconds
(300 by default; 0 waits forever).
Reachable without asking
Section titled “Reachable without asking”| Host | Why |
|---|---|
api.anthropic.com |
Claude itself. odette adds your Claude token. |
generativelanguage.googleapis.com |
Gemini. odette adds the profile’s Gemini key, if set. |
googleapis.com and its subdomains |
Google APIs. odette adds a Google Workspace token, if you use one. |
statsig.anthropic.com, platform.claude.ai, platform.claude.com, downloads.claude.ai |
Claude Code needs them. These are seeded into global.allow on first run; you can remove them. |
The marketplaces your launch declared, on github.com |
Claude Code fetches its plugin marketplaces from them. github.com is an inspected host: each repository is approved on its own, and the marketplaces odette declared for the session need no approval. odette reads a private marketplace you approved with your GitHub login, and nothing else (Private marketplaces on GitHub). An install from before this keeps github.com in global.allow, which lets every repository through; remove that line to approve repositories one by one. |
| Your git remotes’ hosts | Added to the project’s domains.allow by odette init. |
You can’t remove the first three from the Rules zone, but a deny entry still
blocks them. datadoghq.com and its subdomains are always blocked.
Claude’s web tools
Section titled “Claude’s web tools”Claude’s built-in WebFetch passes the network gate like any other connection: the host it fetches is allowed, held for you or decided by the judge by the current mode, and shows in History either way. It needs nothing from you. Claude’s web search is different: it runs on Anthropic’s servers, so it never touches the gate and leaves no row.
If a fetch fails with proxy refused the connection, look at History: a
dial-failed row names the error, for example a host your machine cannot
resolve.
Inspected hosts
Section titled “Inspected hosts”Some hosts serve many unrelated things: every GitHub repository, every npm or
PyPI package. odette keeps a list of these in ~/.odette/egress/global.mitm,
and decrypts their connections instead of passing them through unread.
Being on the list never makes a host reachable: it still has to be allowed.
An inspected host that you have not allowed is not blocked outright.
Instead, each request to it is held on its own, showing its method and
address. In the Inbox you pick what a saved rule covers, from the first
folder of the address down to the exact address, for example
/JuliusBrussee/caveman/ on raw.githubusercontent.com to allow one
repository and nothing else. Once decides that request only; In this
project and Every project save the rule as host/path in the same files
as host entries (raw.githubusercontent.com/juliusbrussee/caveman/). A saved
rule also settles the other requests waiting that it covers. Rules match whole
folders and ignore case, so /owner/repo never covers /owner/repo-other.
An address that could resolve somewhere else than it reads (with .., %2F
or a backslash) can only be decided once. The egress gate mode applies to
these requests as it does to hosts: the AI judge sees the method and the
address, with the values after ? hidden. An allowed inspected host lets
every request through, except paths a deny rule names: a deny rule on a path
always wins.
The list starts with github.com, raw.githubusercontent.com,
codeload.github.com, objects.githubusercontent.com, registry.npmjs.org,
pypi.org, files.pythonhosted.org, proxy.golang.org, sum.golang.org,
index.crates.io and static.crates.io. After that it is yours: add or remove
hosts in the Rules zone with Inspect, or edit the file by hand. Removing
every host does not bring the defaults back. github.com always stays, because
reading your private marketplaces needs it.
The Rules zone refuses, and the file ignores:
- a host odette already adds a credential to (
api.anthropic.com,googleapis.com, …); - a whole public suffix such as
comorco.uk, a wildcard, or a path.
The list applies to every project; there is no per-project version.
Each request to an inspected host is recorded and shown in the dashboard’s
Activity zone under Requests: the method, the address, the status, the
size, how long it took, and the headers sent and received. The content of a
request or response is never recorded. Header values are kept only for
headers that never carry a secret, such as User-Agent or Content-Type.
Every other header value, and every value in the address after ?, is
replaced by its length and a short fingerprint, like
[redacted len=40 h=1a2b3c4d]. Two requests that sent the same secret show
the same fingerprint until odette restarts, but the secret itself cannot be
recovered from it. Requests are kept for 7 days, in a file only you can read.
A plain http:// request to an inspected host is refused. A tool that pins
its certificates, or ignores the system’s trusted certificates, fails on an
inspected host; remove the host from the list to pass it through unread
again.
Allowing and denying commands
Section titled “Allowing and denying commands”A held command shows the command and the folder it runs in.
| Choice | Effect |
|---|---|
| Allow Once | Runs it this time. |
| Allow In this project | Runs it, and allows exactly this command in exactly this folder from now on. Listed under Commands in the Rules zone, where you can delete it. |
| Deny Once | Refuses it. |
A protected command (one that could write to .odette/ or odette’s data
folder, or change odette’s settings) offers only Allow once.
Questions and requests from agents
Section titled “Questions and requests from agents”Agents can also ask you things without stopping. Both kinds land in the Inbox, after pending approvals.
- Decisions: the agent describes a choice, often with options and a recommendation. Pick an option, write a reply, or both, then Send. You can reply more than once; the agent closes the item when it is settled.
- Actions: the agent needs you to do something only you can, such as run a command on your machine. odette shows the command with a Copy button and never runs it. Answer Done or Can’t do it now, with an optional note.
The agent keeps working while it waits. When you reply, odette types a short, fixed reminder into the session once it is idle, telling it to read its replies; your answer itself only reaches the agent through odette. In a pod, a member’s items go to the pod’s supervisor first (Pods).