AI Productivity

The Router

Set who handles each kind of work once, then ask for that work in any terminal without naming anyone — the host routes it for you. Reached under Advanced → Defaults, the Router is now a plain match table with one row per kind of work (plan, test, review, browser, docs, research, debug, explain, advise…), each carrying an agent picker and, once you pick one, a model picker beside it.

The Router

More Screenshots

Click any image to zoom in

Asking for a kind of work in a terminal without naming an agent
The host routing an unnamed 'advise' prompt to the configured agent

Why You Need This

How this feature boosts your daily productivity

The old Router implied a left-to-right order that never matched how routing actually works — it runs per kind of work, never in sequence. Rebuilt as a match table, it reads two ways: By work lists every kind of work and who takes it, while By agent groups the same rules under the agent that owns them so one agent's whole load reads at a glance; anything you have not assigned sits in an Auto pool rather than erroring. A guided Tutorial plays the whole thing end to end — set a default, ask for that kind of work without naming anyone, and watch the host route it, so a prompt asking an agent to "advise" lands on the agent you configured.

How It Works

Get started in 4 simple steps

1
1

Open Advanced → Defaults

Defaults is now a match table — one row per kind of work: plan, test, review, browser, docs, research, debug, explain, advise and more.

2
2

Set an agent and a model per row

Each row carries its own agent picker and model picker, so "review" and "debug" can land on different agents without you naming them at send time.

3
3

Read it "By work" or "By agent"

Switch views: "By work" lists the table row by row, "By agent" rolls it up to show one agent's whole load. Work you never assigned sits in an "Auto" pool.

4
4

Ask for the work, not the agent

Ask for a kind of work without naming an agent and the Router matches it to the row you set, routing automatically.

Without 1DevTool

The manual way vs. the 1DevTool way

The Hard Way

# every task, you name the agent by hand
# a numbered board that implied an order
# routing that never actually ran in sequence
# no way to see one agent’s whole load

The 1DevTool Way

One match-table row per kind of work
Each with an agent picker and a model picker
Read it By work or By agent
Unassigned work sits in an Auto pool

Key Capabilities

Everything included with The Router

Keep one match-table row per kind of work — plan, test, review, browser, docs, research, debug, explain, advise
Set an agent picker and a model picker on every row
Read the table "By work" or roll it up "By agent" to see one agent's whole load
Drop unassigned work into an "Auto" pool instead of forcing an assignment
Route automatically when you ask for a kind of work without naming an agent
Edit it all under Advanced → Defaults, seeded from the CLIs you have installed

Why It Matters

The productivity impact of having ai productivity built into your workspace

Decide the Routing Once

Set which agent handles review, debug or research a single time in the match table, and stop naming an agent on every prompt.

Two Ways to Read the Same Table

"By work" answers what handles this kind of task; "By agent" answers what is this agent responsible for — the same rows, the view you need.

Nothing Falls Through

Work you never assigned waits in an "Auto" pool instead of failing silently, so an unmapped kind of task still gets picked up.

Ask in Plain Terms

Request a kind of work without naming an agent and the Router matches it for you, so the intent — not the roster — drives the run.

Ready to boost your workflow?

Download 1DevTool for free and experience The Router along with 170 other features — all in one app.