pub struct Interface {
pub enabled: bool,
pub debug: bool,
pub origins: Vec<String>,
pub display: Display,
pub pairing: Pairing,
}Expand description
The display-client interface (RFC 0032): the opt-in surface a thin
TUI/web-UI client rides — the global SubscribeToEvents feed and the
interface.*/debug read ops, served on the existing A2A listener (no new
socket). Default-OFF: with enabled: false those methods answer
UNSUPPORTED_OPERATION and the core A2A surface is byte-identical. debug
additionally exposes internals (conversation transcripts, per-step run
detail, the live log ring, audit records on the feed) — operator-grade
information; leave it off in production unless you need it. origins lets a
hosted web UI (a non-loopback browser origin) through the DNS-rebind guard
with CORS; loopback origins are always accepted.
Fields§
§enabled: boolServe the interface methods (SubscribeToEvents, interface.info, …).
debug: boolExpose extra debug information (transcripts, run step detail, the log
ring, audit feed events). Clients render their debug panes only when
this is on. Runtime-togglable over the wire via config.set (operator).
origins: Vec<String>Extra allowed browser origins (scheme://host[:port], exact match) for
a hosted web UI. Loopback origins never need listing.
display: DisplayWhat the display clients render in their chrome (RFC 0032 §12) — the daemon decides; every attached client renders the same layout.
pairing: PairingPairing-code login (RFC 0032 §13): a rotating short code shown to the operator that a client exchanges for a session token — the low-friction alternative to copying a bearer.