Dashboard
The dashboard is where you see every session and answer everything that is
waiting on you. A launch prints its address, https://localhost:7900/ by
default (the port is the web_port setting). It only listens on your own
machine.
Layout
Section titled “Layout”The left rail switches between five zones and is always visible, with the Gates panel (the gate-mode dials, see Approvals) and buttons for desktop alerts, theme and sign out.
The dashboard has two layouts. From 1280 px wide, the rail is on the left and every table shows all its columns; a session’s details open over the right edge of the Sessions zone instead of narrowing it. Below 1280 px (a window beside your editor, down to about 720 px), the rail moves to the top, still with the Gates panel and the buttons, and the zone is one column. A table wider than the window scrolls inside itself, never the page. Narrower than 720 px is not supported.
| Zone | Shows |
|---|---|
| Overview | What is waiting on you, with Allow once / Deny on each pending approval, and one tile per session grouped by pod. |
| Inbox | Grouped by who acts next. Needs you lists pending approvals first, then the decisions and actions waiting on you, oldest first, as cards with a preview line (the first highlighted point the agent filed, otherwise the start of its message); the Inbox count in the rail is the size of this group. Waiting on agent lists the items you have already replied to. Session ended lists open items whose session has stopped: nobody can read an answer, so there is no reply box, only a Dismiss button, on the row and in the opened item, that withdraws the item with a note saying you dismissed it. Open an item and the agent’s highlighted points show above its message as key, warning or note callouts, GitHub-style alerts in the message look the same, and options the agent grouped sit under headings with a one-line consequence each. The list shrinks to a narrow column while the item takes the rest of the width, with the reply controls pinned at the bottom; on a narrow screen the item replaces the list. Keys: j / k move between items, 1 to 9 pick the option at that position, Cmd/Ctrl + Enter sends, Esc closes. A command approval shows the command once, in a block you can read in full. Open items and closed ones are on separate tabs; Closed holds settled decisions and actions only, and a decided approval is in Activity under History; a closed item is removed when its session ends, or after 30 days for a session that keeps running; one closed after its session ended (a dismissed question) is removed after 7 days. Open items are never removed. |
| Sessions | Every running session: profile, pod, model, context used, tokens, whether it is working, idle or blocked, what it says it is doing (when it says nothing, a dimmed note of the kind of tool it is running; both clear when its turn ends), how long ago it last reported, its running sub-agents with what each was asked to do (approximate). Select one for details, per-session gates and Clear context with handoff. Below, Homes: every Claude home and overlay folder with size, last use, running sessions and status, and the total disk use, with Reset, Move and Delete per home and Prune orphans. |
| Activity | Running now: commands and connections in progress; a command has Cancel, a connection has Close. History: finished commands and connections, newest first. |
| Rules | Three tabs: egress, the private marketplaces odette may read with your GitHub login, and the command allowlist. Egress shows Allow, Deny and Inspect columns (hosts odette injects a key for sit under Inspect), with a selector for All, Every project or one project; a project also shows the every-project rules that apply to it, dimmed. A host that a deny rule covers is struck through. Add a host, delete an entry, or revoke a GitHub login; odette rules does the same from the terminal. |
Notes:
- The context bar and the clear targets appear once odette knows the model’s context size; until then the cells show a placeholder.
- What a session “is doing” (purpose, now) is written by the agent itself. Treat it as the agent’s claim, not a fact.
- Cancelling an Anthropic connection in Activity aborts the agent’s current request.
- A History egress row reads
<how> - <why>: how it was carried (tunnel,mitm,http,block) and why it was allowed or refused (global,project,once,yolo,judge,judge-escalate,judge-deny,deny-project,deny-global,deny-builtin,deny, andinspectfor a connection to an inspected host decided request by request). Two rows say why a connection failed rather than why it was decided:dial-failedis a connection that was allowed but whose destination could not be reached (the row names the error, for example a host that does not resolve), andauth-refusedis a request that sent no valid proxy credentials, so it belongs to no session and its Session column is—. A request row names what decided it, includingmarketplacefor a repository the launch declared. A command row opens its saved output. - History’s Requests filter lists each request on an inspected host: method, address, status, size, time taken, and its headers. All leaves them out, since one install can make hundreds. Requests are kept for 7 days, at most 2500.
- Clear history deletes all history, requests and saved command output. History keeps at most 2500 commands and 2500 connections, but saved output is never trimmed on its own.
- Under an organization policy, Sessions also shows a read-only Organization policy section: where the policy was read from and what it restricts. You can’t change it there; see Security.
- Rules: a manually added host covers its subdomains. Hosts odette adds your credentials to, and the built-in deny entries, can’t be deleted.
- The Sessions table shows a model without the
claude-prefix and date (haiku-4-5); hover for the full id. Homes show the project’s last two folders, plus the worktree’s name for a worktree (kzn/odette (wild-newt)); hover for the full path. - Homes list at once; sizes and last use read “calculating…” until the disk has
been measured. They refresh every minute. Reset, Move and Delete ask for
confirmation, Move also for the project’s new folder. They are greyed out
while a session uses the home, and the tooltip names the session to stop
first. Prune orphans deletes the homes and overlay folders whose project
folder is gone. They do what
odette sessions home reset,mv,rmandprune --orphansdo (Sessions).
Clear context with handoff is offered for pod sessions only; see Pods.
Dashboard or terminal
Section titled “Dashboard or terminal”The dashboard supervises and answers; the terminal configures and manages lifecycle.
| Only in the dashboard | Only in the terminal |
|---|---|
| Answering the Inbox and approvals | Starting and stopping a session (odette, odette sessions stop <name>) |
| Cancelling a running command or connection | Creating and deleting profiles, kits, marketplaces |
| Clearing history | Everything under .odette/ and config.json |
| Clearing a session’s context with handoff |
Host rules, GitHub logins and Claude homes can be managed in both.
Sign-in
Section titled “Sign-in”Sign in with the dashboard password from odette setup. Change it with
odette dashboard password, which also signs out every browser. A sign-in lasts 7
days; Sign out in the rail ends it everywhere.
Desktop notifications
Section titled “Desktop notifications”Click the bell in the rail and allow notifications in the browser. A plain bell means alerts are on; a bell with a diagonal slash means they are off. You are alerted, with a short beep, when an approval is waiting, and when a session finishes its turn or needs attention. Alerts are skipped while the dashboard tab is visible and focused. The setting is kept per browser.
Certificate
Section titled “Certificate”The dashboard uses its own self-signed certificate for localhost,
127.0.0.1 and ::1. On macOS, odette setup offers to add it to your login
keychain. Otherwise accept the browser warning, or trust it yourself:
odette dashboard cert # prints the certificate's pathsecurity add-trusted-cert -r trustRoot -k ~/Library/Keychains/login.keychain-db <path>Trusting this certificate is safe: it can only vouch for the dashboard. It is reissued about once a year; trust the new one then.
Never trust odette’s proxy certificate authority (~/.odette/ca/) on your
machine. It can issue a certificate for any website. See
Security.
Status row in the terminal (experimental)
Section titled “Status row in the terminal (experimental)”The session’s terminal can show what is waiting on you in its top two rows,
for example odette: 1 pending approval · 2 questions · 1 action. The rows
appear only while something is waiting and disappear when nothing is. Turn it
on:
odette config set feature.status_row onIt is off by default until it is confirmed to behave in every common
terminal. A session running under an organization policy
(Security) always shows the row, with
organization policy in it.