Things to ask for

Agent Team listens to plain language. Here are requests that work well — change the names and details to fit.

Split a job

Split this refactor across the team. Codex takes the API layer, another Claude takes the UI, and you handle the shared types. Tell me when everything passes.

We need tests for these four modules. Give each one to a different worker.

Get a second opinion

Have codex and grok review this diff independently, then tell me where they disagree.

Before I merge, ask kimi to look for edge cases you might have missed.

Hold a roundtable

Roundtable: SQLite or Postgres for the sync service? Ask claude, codex and opencode for one round each and summarize the trade-offs.

I'm not sure about this API design. Get two independent opinions before we commit to it.

Research in parallel

Compare three PDF rendering libraries in parallel — licence, size, maintenance, API — and give me one table.

Have one worker read the old implementation and another read the new spec, then explain what changed.

Pick the right agent for the job

Open a codex with high effort to investigate the memory leak while you keep working on the docs.

Let devin write the migration script, then have codex review it.

Stay in control

Give me a progress update after each worker finishes.

Keep the worker panes open when you're done — I want to look through them.

Give each worker its own worktree so they don't step on each other.

Tips

• Say what "done" means. "Tests pass", "a table I can paste into the doc", "a one-paragraph recommendation" — your agent puts it in each task and checks against it.
• Name agents when you care, skip it when you don't. Your agent picks sensibly on its own.
• You won't be asked to referee. Your agent comes back to you only for decisions that are genuinely yours — a preference, a permission, or missing information.