From a task brief to a reviewed result

1. Define the decision or deliverable

Give the task a clear endpoint. Instead of asking for general research, specify what you need to decide and which questions the result should answer. Include the intended audience, relevant period and constraints such as using only the attached material.

An example brief is: “Compare these three proposals. Show the differences, open questions and your recommendation. Cite which proposal supports each finding, and do not contact the suppliers.” This is an illustrative instruction, not a customer result or a measured claim.

2. Supply sources and choose tools

Attach the proposals or other relevant files to the conversation. Explain any missing information rather than assuming the agents can retrieve it. Private files, captured websites and connected services can provide context when they are available and authorised in your workspace.

Choose connected tools according to the task. A comparison based on attached files may need no external connection. Research that needs a company document or email must stay within the relevant account and workspace permissions.

3. Follow and steer the work

An Agent Team can break a substantial request into a checklist and delegate bounded assignments. The workspace shows what is running, finished and next, along with agent outputs. You can inspect the work without manually driving every intermediate step.

If the brief changes, update the instructions or stop the task. Retrieving source material and drafting an output do not authorise every possible follow-up action. Sending, publishing or changing connected information requires the appropriate explicit authorisation.

4. Check the result against the brief

For the proposal example, check that all three sources were considered, that comparisons point back to the correct source, and that missing information is presented as an open question. Treat a recommendation as input for your own review, not a verified decision.

The homepage demonstration shows another illustrative workflow: customer-feedback research, a launch-issue update and a follow-up email draft. It demonstrates the work sequence; it is not a testimonial or a promise that every task returns a correct result.

5. Repeat only the work you authorise

Scheduled tasks can repeat a useful workflow and return results to the originating conversation while the browser or desktop app is closed. Set the scope and review expectations before making a task recurring. Recurring actions with external effects need prior explicit authorisation.