Configure Runtime
Change runtime language, location, speech defaults, and blocked skills safely.
Runtime config changes the shared defaults for one skill set.
Use it when a hub group needs a different language, location, speech setup, or blocked-skill list. For most first setups, the workspace default is enough.
Before changing runtime, make sure the problem is about shared defaults. If you only need to add or remove one ability, use Skills instead. Read Runtime first when you need the model.


Before You Change Runtime
Section titled “Before You Change Runtime”Three things are worth a look first. Make sure the skill set you’ve selected is the one the hub actually uses; the name at the top of the drawer is the check. Open Assignments, because every hub on that skill set will get the change, not just the one you were thinking about. And pick your moment: saving restarts the runtime, which means a short gap in answers.
Configuration Steps
Section titled “Configuration Steps”- Open Skills. Choose the skill set you want to change.
- Check Assignments. Confirm which hubs use this skill set.
- Open Runtime config. This opens the guided config drawer.
- Set general defaults. Choose primary language, secondary languages, location, speech-to-text, and text-to-speech.
- Review blocked skills. Add only skills that should stay blocked for this skill set.
- Review the summary. Use the generated summary as a final check.
- Save. The runtime restarts so the new settings can apply.
- Return to Dashboard and Topology. Confirm health returns to the expected state.
What Each Step Means
Section titled “What Each Step Means”Use General for everyday defaults: language, location, speech-to-text, and text-to-speech. Most runtime changes belong here.
Use Skills to block skills for this skill set. This is useful when a hub group should never load a certain ability.
Use Summary as a final review before saving. It helps you see what will change for the selected skill set.
Common Runtime Changes
Section titled “Common Runtime Changes”| Change | Where to do it | What to check after |
|---|---|---|
| Main language | General | The related hub behaves in the expected language. |
| Extra languages | General | The language list matches the audience. |
| Location | General | Location-aware skills use the right city or region. |
| Voice input | General | Speech-to-text still works after saving. |
| Voice output | General | Text-to-speech still uses the expected voice. |
| Blocked skill | Skills | The blocked skill no longer loads for this skill set. |
| Source Scout age protection | Installed skill configuration | The selected under-13, under-16, under-18, or under-21 boundary is enforced. |
| Generated summary | Summary | Dashboard and Topology return to healthy status. |
Source Scout knowledge is unrestricted by topic unless its child-protection toggle is enabled. Configure that setting on the installed skill, not with a public hub’s age-guidance label. See Skills for the supported boundaries and fail-closed behavior.
Safe Change Pattern
Section titled “Safe Change Pattern”When a runtime setting is important, use this pattern:
- Create or choose a separate skill set when only one hub should change.
- Assign one test hub to that skill set before changing many hubs.
- Apply the runtime config change.
- Check the test hub.
- Move more hubs only after the result is clear.
Runtime Configuration Is Done When
Section titled “Runtime Configuration Is Done When”Runtime configuration is done when:
- the changed skill set is assigned only to the intended hubs;
- the Summary matches what you meant to change;
- runtime has restarted or refreshed successfully;
- Dashboard shows no unexpected runtime attention item;
- Topology returns to the expected connection state.