Responder configuration reference

buzz.actor.set-responder decides who answers for one attached actor: its Staff configuration, DGI, or both. It is the only setting structured chat needs. Structured chat is part of DGI and is Alpha.

• Who may call it: an organization admin or owner, signed in as a person. Agents, API keys, the system and end users are refused.
• Where it is stored: on the space, per attachment. data.buzz.attachment.list returns it as each attachment's responder. Nothing in it is a secret.
• When it takes effect: on the next message. No buzz.bridge.sync is needed.
• How to undo it: call it again with responder: "staff". The DGI entry is removed and the actor answers with its Staff configuration.
• Replacing, not merging: each call stores the whole entry. Send every field you want to keep.

Fields

Suggestions

suggestions pins an actor's quick replies. Each entry has exactly two keys:

• label: 1 to 48 characters, plain one-line text, distinct from the others (case-insensitive), not starting with a bullet or wrapped in quotes.
• prompt: 1 to 200 characters. It tells DGI what the label means.

A quick reply posts its label as the person's message, never its prompt. Pick labels that read well as a message, such as "Blocked tickets".

Seat mode or organization mode

The responder decides what answers. The attachment's reply principal, set with buzz.actor.set-reply-principal, decides as whom DGI runs:

See Internal support actor for the gates of organization mode.

Hybrid: DGI first, Staff for the rest

With responder: "hybrid", every turn starts as a DGI turn. The turn is handed off to the actor's Staff configuration when DGI drew no card, did not refuse the request, and one of these holds:

1. DGI stopped at a fallback whose reason is in hybrid_handoff_reasons;
2. DGI produced no usable text and no card;
3. the DGI run failed.

Default hybrid_handoff_reasons:

Reasons match by family. A listed name also covers every reason that starts with it: jev covers jev_timeout, and chitchat covers chitchat_needs_tools. A fallback reason that is not listed is answered by DGI's own LLM, so views that only the LLM path draws still reach a hybrid actor.

On a hand-off nothing of DGI's is posted: the Staff configuration answers the same message exactly as responder: "staff" would, as the actor's seat (so a hybrid actor in seat mode must declare that it acts as the app). An answer to a card always stays with DGI.

Default inputs

default_inputs pre-fills workflow inputs. For example, a support actor that should see only support tickets in active states:

{
  "ticket.search": {
    "labels": ["support"],
    "status": ["open", "triaged", "in_progress", "blocked"]
  }
}

• Limits. Every type must be allowed by allowed_workflow_types (exactly, or under a prefix.*; a pattern itself is refused). Up to 20 types, 30 fields per type, field names like [A-Za-z_][A-Za-z0-9_]* up to 64 characters, values JSON scalars (strings up to 1,000 characters, numbers, booleans, null) or lists of up to 50 of them, and 8,192 bytes in total. Anything else is default_inputs_invalid.
• The person's own values win. A default fills a field only when the message and the form leave it empty.
• Naming a value narrows the default. When a message names a value of a defaulted filter, DGI uses that value instead of the whole default list: "show me the blocked tickets" searches status: [blocked], not the four defaults. The card's title says which filter it used.
• They grant nothing. Defaults cannot widen the scope, skip the confirm, or reach another person's data.
• Superseded entry points. When an app entry point is republished under a new version, the defaults for the old type follow it, as allowed_workflow_types do.

Troubleshooting

Ask your AI assistant

Read the responder of every actor in my chat space with data.buzz.attachment.list and explain each setting in plain words.

Draft a hybrid responder for my actor "<actor name>" that hands free-text questions to its Staff configuration but keeps low-confidence reads on DGI. Show me the hybrid_handoff_reasons you chose and why.

Add default_inputs to my support actor so ticket searches default to open support tickets, keeping every other responder field unchanged. Show me the full call first.

For AI agents