Ask the Guide

The Guide answers questions about Zozo and the configuration of the current Stack. Open it with the Guide bubble from any Dashboard page, type a question, and keep working while the answer runs.

The Guide reads the version-matched documentation shipped with your Stack and a point-in-time snapshot. It can see allow-listed Stack and Project settings; Credential names, types, and health; the Stack health document; Attention Items; usage totals; and bounded Thread summaries. It never contains Credential values or other secrets. The Guide has no live connection back to the Stack and cannot change settings.

The Guide can report the Stack's hosting mode and Onramp state from that snapshot, but it sends you to the Onramp entry in Dashboard Settings to start, continue, or cancel an Onramp.

Thread summaries cover the 20 most recently active Threads across all Projects, plus every active Thread, every Thread represented by an Attention Item, and the Thread currently open in the Dashboard. A summary contains metadata, times, stop or failure details, the final reply, and a Digest when one exists. It never contains the Thread transcript. If another Thread falls outside that bound, the Guide says it is unavailable in the snapshot and links you to its Dashboard page.

One session across the Dashboard

A Stack has one open Guide Session. The same conversation reopens after you navigate to another Dashboard page or open the Dashboard on another device. The current route and the identifier of the Thread, Run, Map, or Issue in view are included as context with each question.

Choose Discard to end the conversation. Opening the Guide again after that starts a fresh session; the discarded Thread remains part of the Stack's history.

Permissions and Credentials

Every turn uses the Stack-level Guide Credential configured on the Credentials page and that Credential's Guide runtime profile. There is no fallback to a Project Credential Route. If the Credential is missing or unusable, or its Provider cannot enforce the read-only policy, the turn fails with an explanation instead of silently selecting another Credential.

Guide Runs can read and search their synthetic Workspace with the Provider's native file tools. They receive no MCP configuration and have no network or write permission. Images can be attached from the shared composer.

Proposals

The Guide cannot change settings itself. It can raise a Proposal that shows the old and proposed values together with its rationale. A Proposal also appears in Needs Attention until you choose Apply or Dismiss. Applying always uses your signed-in Dashboard session and the same validation and mutation path as changing that setting directly in the Dashboard.

The Dispatcher accepts Proposals only for these Stack-local settings:

• the concurrency cap;
• Auto-dispatch on or off and its interval;
• suspend or resume for the fleet Dispatch;
• default Stop Conditions;
• a named Project's configuration;
• a named Project's Intake and Dispatch Credential Routes;
• a named Credential's Runtime Profile;
• notification preferences for a registered browser; and
• the value of an existing plain Environment Variable.

Project and Credential Proposals use the exact Project id or Credential name from the snapshot. A Proposal for a name that is not present is ignored. Credential Route changes use the same validation as the Projects page, including the requirements that each activity has a Primary Credential, that a Fallback differs from its Primary, and that every named Credential exists.

Secret Variables are never Proposal targets. The Guide can explain where to manage one and link to the Environment editor, but any Proposal that names a secret-typed Variable is discarded with a warning and is never shown as a card.

Every Proposal is tied to the revision of the settings snapshot the Guide read. If that value has changed since the snapshot, Apply refuses the Proposal and shows the current value instead of overwriting it. Discarding the Guide Session removes its Proposals. Invalid Proposal data is ignored and recorded as a Run warning.

Because ordinary answers also describe a snapshot rather than live state, check the Dashboard before acting on a setting that may have changed since the turn began.