Chat and routing
Oracle looks like a chat box. Underneath it is a router that checks every prompt before anything runs. This guide shows you the four moves and how to watch your work happen.
narrated · sound on
Why this matters
Agents fail by being obedient at full speed. Routing every ask through one brain that can answer, delegate, clarify, or act is how Cronus keeps obedience from becoming the failure mode.
The walkthrough
The four moves
Every message you send gets read by the router, which picks exactly one move: answer (small talk, questions it already knows), delegate (real work, handed to exactly one agent, named out loud), clarify (one question back when your request genuinely has two readings), or task (quick actions it can do itself).
Delegations carry a definition of done
When Cronus hands work to an agent, it does not forward your chat. It writes a self-contained instruction with the context baked in, why that agent was chosen, and a checkable sentence describing what finished-and-correct looks like. The result gets judged against that sentence.
Pick the brain
The model chip in the top bar chooses which model Cronus thinks with. Local models are free and private; cloud models are faster and sharper. Click, switch, done - your history, memory, and setup do not change.
Watch it work
Delegated jobs run in the background. The Activity page shows each one as a worker at a desk, and agent windows stream raw output. If something fails, it looks like a failure - never a dressed-up success.