Config sets
Reusable bundles of variables, recognition hints and pronunciations that several agents share.
A config set is a named bundle of settings that belongs to the workspace rather than to one agent. Attach a set to an agent and it inherits everything in it. Edit the set once and every attached agent picks the change up on its next call.
What a set holds
| Entry | What it is |
|---|---|
| Variable | A named substitution, {{name}}, used in a tool's URL, headers or body. Plain or secret. |
| Recognition hint | A word or phrase the speech engine is told to expect |
| Pronunciation | A word plus a respelling of it |
Attaching a set
Attach from the agent's Variables section. The library where you create and
edit sets is at /<your-workspace>/config-sets.
An attachment is a live reference, not a copy. Edits reach the next call with no publish step. Attachments are agent-scoped, so publishing and rolling back a version does not change them.
Ordering
When an agent attaches several sets and two define the same variable name:
- The agent's own variable wins, always.
- Then attached sets, in the order shown on the Variables panel. Top wins.
Hints and pronunciations merge rather than override. The agent's own entries come first, then each set's in attachment order, deduped case-insensitively.
When to use one
- A base URL or credential shared by several agents, so rotating it is one edit.
- A vocabulary that belongs to the business, not one agent: suburb names, product ranges, staff names.
A value used by exactly one agent belongs on that agent.