What you control here
The console is where you inspect providers, tokens, channels, Skills, memory behavior, and active tasks. It turns the runtime into something observable and steerable.
- Provider and model configuration
- Channel status and adapter health
- Task activity, usage, and memory behavior
Routine operations
Most people return to the console when they need to diagnose channel issues, rotate a provider, update a Skill, or check whether a scheduled workflow actually fired.
- Open the dashboard and verify the active runtime.
- Inspect providers and ensure the default route is healthy.
- Check channels and task logs after any change in behavior.