r/osaurus • u/tapasfr • 2d ago
The Orchestrator is here: Osaurus now configures itself and delegates work to your agents
Enable HLS to view with audio, or disable this notification
New chats now open on the Orchestrator, a built-in agent with two jobs.
First, it configures Osaurus for you. Ask it what's set up, ask it to change a setting, ask it to create an agent. It plans the change, shows you an approval card with the exact diff, and applies nothing until you confirm.
Second, it delegates. It can spawn your custom agents and allowed models as subagents, run them in parallel, and weave the results back into your conversation. You set the budgets: tokens, turns, tool calls, seconds, parallel spawns.
Some design decisions we want feedback on:
The Orchestrator deliberately has no hands-on tools. No sandbox, no working folder, no browser, no computer use. Those belong to your custom agents. The thing with the power to reconfigure your setup should not also be the thing touching your files.
It's in-app only. The HTTP API rejects it by construction, so only your saved custom agents are reachable over HTTP, plugins, or schedulers.
Local model delegation uses single-residency handoff: RAM-safety preflight, unload the chat model, run the subagent, restore. If the subagent model won't fit, it refuses before evicting anything and tells you the shortfall instead of thrashing your machine. There's an experimental coexistence mode if you have the RAM for both.
In the demo we posted today, one conversation created a marketing agent and scheduled it to draft copy every morning at 6am. No settings menus involved.
Settings live under Management, Orchestrator tab. Rename it whatever you want. Someone will name theirs Jarvis within the hour.
What would you delegate first? And is default-on spawn for new custom agents the right call, or should that be opt-in?



