Multi-Engine Runtime
One abstraction layer to switch freely between the built-in SDK and mainstream agent engines.
Updated 2026-09-19
WorkGoa isn't locked to a single model engine. It offers a unified Runtime abstraction so you can switch between engines without changing your habits.
Why it matters
Different engines trade off long-form consistency, cost, and speed. A unified abstraction lets you pick the right one per task instead of being pinned to any single engine.
How to switch
Choose a Runtime and model provider in Settings. After switching providers, sessions and context are handled correctly, so you don't start over. For how requests go straight to your provider, see Connect a Model Provider.
Stop really stops
Pressing "stop" truly stops everything: it terminates background tasks and cancels live messages, while preemption and session-switch scenarios keep background tasks and queues alive so useful work isn't harmed.
Related
On top of Runtime sit the skill system and three-layer memory; together they decide what the agent can do and what it remembers.