XCB keeps presentation, optional extensions, and execution authority separate. Inspect your current setup before changing it:
xcb config
xcb panes
xcb pluginsMove between sessions
Inside the terminal, use /sessions to open a saved session or /new to start another. /accounts and /model open the account and model pickers. Finish the current turn before changing its account or model.
Arrange your terminal
Open the pane picker with /pane, switch to the built-in focused view with /pane focus, or edit the current declaration with /pane edit. To describe a new view, use /pane generate <description>, replacing the placeholder with what you want to see. Generation uses the selected account and model; if that session is busy, it waits for the account’s next idle boundary.
Panes describe what the terminal displays. They are bounded presentation data, not executable plugins, and cannot grant a provider new tools or permissions.
xcb panes show focus
xcb panes check /absolute/path/to/pane.json
xcb panes install /absolute/path/to/pane.jsonUse the built-in pane as a starting point and validate a declaration before installing it. The terminal’s /help lists the interactive controls.
Continuation and context
Auto-continue and Gobstopper context management are enabled by default. Continuation is bounded and requires a safely settled turn. Context management reduces retained context according to the configured policy.
xcb plugins disable auto-continue
xcb plugins disable gobstopper
# Enable them again:
xcb plugins enable auto-continue
xcb plugins enable gobstopperOne provider turn has a 30-minute default deadline, including initialization. The private state root’s config.json accepts turn_timeout_ms from 1,000 to 3,600,000 milliseconds. xcb config displays the effective settings; continuation has its own separate limits.
Local usage and explicit opt-ins
Usage measurement stays local. Automatic aiCharts upload is unavailable. Local exports, executable hooks, and external judgment require separate opt-in; enabling a presentation pane cannot enable them.
Hooks execute code and need their own trust decision. Review the optional behavior reference and xcb hooks --help before adding one.
An optional external judge
The TypeSafe System One judge can advise routing, continuation, and context retention. It sends bounded task and response context to that service; it cannot qualify a provider or bypass deterministic checks. It is disabled by default.
xcb judge token < /secure/path/to/judge-key
xcb judge status
xcb judge enable
xcb judge test
# To stop using the judge:
xcb judge disable
xcb judge logoutThe input is an existing private credential file. Keys are stored outside the workspace; do not put a key in a command-line argument. See the complete reference for environment and custom-endpoint behavior.