Clanker CloudA business brief often contains three different jobs: establish the facts, write a readable argument, and check whether the argument is supported. You can give those jobs to separate Workspace Agents with distinct instructions.
Start with explicit, sequential handoffs in one Project. This makes each role and output easy to inspect before you consider a coordinated team run.
Give every role a deliverable
For a fictional supplier decision, set up these roles:
| Agent | Input | Output |
|---|---|---|
| Researcher | Brief, criteria, and current proposals | An evidence table with source locations and unknown terms. |
| Writer | Reviewed evidence table and business question | A decision brief that preserves uncertainties. |
| Reviewer | Source files, evidence table, and decision brief | Findings identifying unsupported claims and missing context. |
Create the specialists in My Agents, using the custom Agent guide. Add the relevant knowledge and Skills, and select the Tools each role actually needs.
Keeping the roles separate can make review clearer. It does not guarantee that the Agents will avoid the same mistake or that a final answer is correct. The source packet remains the basis for judgment.
Make the research handoff explicit
Begin a Session in the supplier Project with the Researcher. Ask it to save evidence-table.md with the proposal version, source location, stated term, and any uncertainty for each criterion.
Inspect that file before passing it on. If a proposal omits cancellation terms, the table should say they are unstated. The vendor comparison starter supplies a useful structure.
Then select the Writer in the next Session and name the reviewed file:
Read evidence-table.md and the current purchasing brief. Draft a decision brief from the supported findings. Keep missing cancellation terms visible. Distinguish a conditional recommendation from approval to purchase. Save decision-brief.md for review.
Naming the exact input helps the Writer avoid treating another draft or an old conclusion as the accepted handoff. Shared Project files provide the working context; private Agent memory is not assumed to synchronize between roles.
Ask the Reviewer to inspect the evidence
Give the Reviewer the original sources as well as the draft:
Review decision-brief.md against evidence-table.md and the current proposals. For each material claim, identify support or a gap. Pay attention to price, currency, dates, exclusions, and cancellation terms. Save review-findings.md. Do not rewrite or approve the brief yet.
Seed a known error in a fictional trial, such as changing a proposed date into a guaranteed delivery date. Check whether the Reviewer catches it. A vague “looks good” is not evidence that the source comparison happened.
Apply reviewed corrections and inspect the revised brief. Keep the versions and findings together so the next colleague can see what changed and why.
Use team controls when they fit the task
Workspace also supports selecting multiple eligible Workspace Agents for a coordinated team in a Browser-safe Workspace Session. Check the available controls and run mode before using that path. Connected external BYOA agents and Premium Agents currently run individually, so do not assume every Agent can join the same coordinated run.
The sequential method above can be tested with one selected Agent at each stage. If you adopt coordination, verify that each requested output is saved and that the review actually checks the sources. More participants are useful when their roles address a concrete gap in the workflow.
Sharing an Agent with a colleague is another operation. The team sharing article covers reusable definitions; sharing a role does not by itself transfer private history, credentials, or all Project access.
Sources
Give your assistant one useful job
Give each Agent a clear role and make the handoff visible through Project files you can inspect.