Skip to content
HandbookTeams and collaboration

People and Agents working together: discussion, responsibilities, and handoff

Invite members, choose roles, agree on changes through discussion and mentions, then divide work across Agents using shared files and clear handoffs.

11 min read

What you will be able to do

Complete a team discussion and multi-Agent task while distinguishing shared files, discussion messages, and each conversation's context.

Who can comment, run tasks, and manage access?

Viewers can read shared work and leave text comments in member discussions. Editors can also change files and send Agent tasks. The Owner manages invitations and member roles. Commenting to people is not the same as asking an Agent to execute a task.

Shared files do not mean that every conversation knows all the background, and simultaneous edits are not automatically merged. Name the files, confirmed decisions, and permitted changes when handing work to another Agent.

For standard platform model calls, the Workspace owner's available entitlements apply. Local Agent tasks use the connected computer's login and subscription; BYOK calls are billed by the external provider. Check models, usage, and payment responsibility before inviting someone to run tasks.

The exercise below shows how to apply those boundaries.

The invitation page is almost ready. Lin notices that the rain plan is hard to find; Qing wants to know whether people can rest along the way. Invite them to the same Workspace so they can comment on the existing files and activity, without passing around multiple “final” versions.

Separate conversations, shared project files
  1. ContentWrite the agreed brief
  2. BuildUse the brief to make the page
  3. ReviewRecord findings for the next pass
Share decisions through explicit handoffs and files; conversations retain their own context.

Members and Agents share workspace files in the diagram, while each Agent conversation has its own context. Shared materials help collaboration, but agreed decisions still need to be passed on explicitly.

1. Decide which permissions each person needs

Open “Members” in the sidebar to reach “Members and permissions.” The Owner manages invitations and members; other members can inspect existing roles. Choose by responsibility. A friend does not need editing rights just to comment.

RolePurpose in this exerciseMain boundary
OwnerStart the project, invite people, manage rolesManages the Workspace; standard platform model calls use the owner’s entitlements, while local Agents use the computer owner’s login and subscription.
EditorCreate or continue Agent conversations and change filesCan invoke Agents, but cannot manage invitations on the Owner's behalf.
ViewerRead files and conversations, and join member discussionsCannot edit files or invoke Agents; can leave text comments in discussions.

Here you are the Owner. Lin will invoke the reviewing Agent, so give Lin Editor access. Qing will inspect and comment, so Viewer is enough. Role changes affect later access; having joined once does not grant permanent permission.

A key, a pencil, and a magnifying glass with a speech bubble connect to one central set of files.
Assign permissions for managing, editing, or viewing and discussing the same shared work.

2. Create and check the invitation

The Owner creates an invitation link in the relevant role section and can copy the link or share a QR code. Current invitations let multiple signed-in users join through the same link within seven days; the exact expiry is displayed. Check the role and intended recipients before sharing. The link grants entry to a shared workspace, not merely a finished webpage.

Your friends sign in with their own accounts, review the workspace name, role, expiry, and who pays, then accept. Registration preserves the invitation and returns to confirmation after verification. If joining fails, check whether the invitation expired or was revoked, or whether member capacity is full, then ask the Owner to resolve it.

Verify success concretely: both Lin and Qing can find weekend-walk/index.html and open the conversation that created it; Lin can send Agent tasks, and Qing can enter the discussion. To show only the finished work, download the webpage file and send it, or ask the Agent to create a temporary preview link with Cloudflare's official tools.

3. Discuss with people; assign tasks to the Agent

Open “Discussion” at the top of the conversation. Write something like “Should the rain note go beside the preparation list?” and mention the people who should respond. Mentioning a member in the main input and selecting a recipient also switches to discussion mode, where the Agent will not reply. Before sending, check whether the button sends to the discussion or to the Agent.

Member discussion supports text. If asked to remove attachments, file references, or annotations, do so first. Quote text from an Agent response, or use reply, to keep comments tied to their subject. Viewed and unviewed indicators report reading, not agreement or completion.

Qing might write, “I look for the meeting point first; place it beside the time.” Lin adds, “Keep the rain-postponement note.” You reply, “Both agreed; retain the current colors.” The Agent will not start editing automatically.

Once agreed, a member with execution permission can select discussion messages to give to the Agent and quote them into the input box. Review what will be included with the discussion, and add a clear instruction:

text
Update weekend-walk/index.html using the included discussion.Agreed: Keep the time and meeting point together, and retain the rain-postponement note.Only rearrange information this turn. Keep the existing colors and do not publish publicly.Tell us where you saved it and what you actually checked.

Members can continue an existing conversation; it is not limited to its creator. Messages sent directly to the Agent become tasks and may use model allowance or credits. Even “Discuss first, do not edit files” is a model task when sent to the Agent. If several people send while it is busy, check the shared queue before repeating a request.

4. Divide work between Agents and define writing boundaries

Different conversations in one workspace can run in parallel. You can revise the page in the original conversation while Lin starts another with an available Agent and compatible model to review the content. They need not use different brands. The task and permitted files define the division of work.

ConversationResponsibilityFiles it may write
Page creationApply agreed changes to the invitationweekend-walk/index.html
Content reviewIdentify gaps from a first-time participant's perspectivereview.md at the workspace root

Copy this task for the reviewing Agent:

text
Read the current weekend-walk/index.html.This is a fictional “Weekend Walking Club” invitation.We are adjusting the time, meeting point, and rain note.Check whether the time, location, route, breaks, and joining instructions are clear.Write at most three specific suggestions to review.md at the workspace root.For each, state the issue, recommendation, and evidence. If there is no issue, say so.Only write review.md. Do not change the webpage, add registration forms, or publish publicly.If you have not actually opened the page, do not claim to have checked its appearance.

Keep review notes outside the website folder so internal material is not accidentally included when sharing the whole directory. To watch both conversations, see the current workbench options in Dynamic views.

For an existing code change rather than a webpage-copy review, see asking Codex to review Claude Code's work. Define the diff and keep review separate from permission to modify files.

5. Shared files do not merge themselves

Both conversations operate on the same current files. They do not get automatically isolated private copies, and conflicting edits are not reliably merged for you. One Agent edits the page while the other writes only review notes to avoid simultaneous rewrites.

The review may happen before page edits finish. Wait for the relevant tasks to complete, then read the current files again before acting on suggestions:

text
Read the current weekend-walk/index.html and review.md.List which suggestions are already resolved and which still apply. Do not edit yet.Clearly identify decisions we need to make.

People decide which suggestions to adopt. The page conversation then applies them together. Qing opens the result to check the narrow layout and button.

6. Leave a handoff someone can use tomorrow

Members can browse shared conversations, but a new Session's Agent has not automatically read other conversations. When changing Agents, conversations, or owners of the work, provide at least the goal, files, settled decisions, and next step.

A shared folder sits between separate conversations, linked by a handoff note with a goal and checklist.
Shared files hold the work; an explicit handoff supplies the background the next Agent needs.
text
Handoff: We are refining a fictional event invitation.Page: weekend-walk/index.html. Review notes: review.md.Agreed: Keep the example label, current colors, and rain-postponement note; do not add registration forms.Checked: The desktop button jumps to the joining instructions.Still to check: Whether the full meeting point is visible at phone width.Read both files and confirm the current state first. Report before acting; do not publish the site.

If someone can view but not edit, check their role. If a file is missing, confirm you are in the same Workspace. If the Agent repeats a rejected proposal, check whether that decision was included in the handoff. Approval requests belong to the task initiator; the Owner can also stop tasks. Ordinary members cannot approve every request for someone else.

At the end, you should know who owns changes to the current file, which feedback is agreed, and where the next person should resume. That lets more people and Agents reduce omissions instead of increasing guesswork.