Delegation
Delegation is a Labs feature. It is built into nightly builds and switched off until you turn it on in Settings → Labs.
Celeris is built for the two-second task. Some tasks are not two-second tasks. A refactor across forty files, a migration, an afternoon of test failures. Those want a different kind of agent, one that will grind at a problem for twenty minutes.
Delegation hands that work to a coding agent already installed on your computer. Celeris stays the place you start from and the place the result comes back to; the long job runs somewhere better suited to it.
What gets used
Open Settings → Tools → Delegation. Celeris looks for the coding agents installed on this machine and lists what it finds, with the models each one can reach. Nothing is installed for you, and nothing you have not ticked is ever used.
If the list is empty or wrong, Refresh re-checks. An agent installed after Celeris started will not appear until you do.
Two strategies
Fixed model. Every delegated task goes to the one model you pick. Cost and behaviour are predictable and you always know what ran. The trade is that a small task pays for a large model, and a large task is stuck with a small one.
Smart routing. Tick several models you are happy for Celeris to use, ready for per-task routing. Be aware of what this does today: the routing itself is not built yet. Celeris saves everything you tick, but for now every delegated task runs on the first ticked model whose agent is installed, and the page marks which one that is. Nothing is chosen per task, and cost does not vary run to run.
We would rather say that plainly here than have you discover it from a bill.
Effort
Each ticked model has a reasoning-effort setting. Lower effort is faster and cheaper and thinks less; higher effort is the opposite. It is per model, because what counts as sensible effort on a small fast model is not what counts on a large one.
What delegation does not change
- Approvals. A delegated job runs under the agent's own permissions on your machine, and Celeris does not hand it a wider grant than you gave. Read Approvals & safety, and read your agent's own settings too. It has its own rules and they apply.
- Where things run. Delegated work runs locally, on the machine that started it, unless you deliberately sent the session to another device with Remote sessions.
- Cost. Delegated tasks bill against whatever account that agent uses, not your Celeris account. A twenty-minute job on a large model costs what a twenty-minute job on a large model costs.
When not to delegate
If the task is small, do not. The hand-off has overhead, and Celeris finishes a small task before a larger agent has finished reading the repository. Delegation is for the work that is genuinely long, not for the work that merely feels annoying.