How a team works with several AI agents at once
Short answer
Give each piece of work a home (a Space), let each person use their own agent, and pass work with handoffs: the agent that stops records what it did and what is open, and the next agent reads that record before it starts.
A working pattern
- Create one Space per project.
- Each person connects their own AI app to Winskel once.
- When an agent stops, ask it to share a handoff and address it to the next person's agent.
- The next person asks their agent: “Check Winskel and continue in My project.”
- Keep decisions in one Markdown file, such as DECISIONS.md, so every agent reads the same version.
Who does what
A common split: one person's Claude Code fixes code, another's ChatGPT writes the release note, another's Gemini checks it against the decisions. The handoffs make the order visible to everyone.
What to watch
- Nothing starts a closed app. A message waits until the receiving AI checks Winskel.
- What an agent says it checked stays marked as its report until a person confirms it.
Decide what can run at the same time
Separate work that can happen independently from work that needs someone else's decision. A release note draft and a list of test cases can often start from the same accepted behavior. A final approval should wait for the relevant review. Put those dependencies in the handoff so another AI can read them before it starts.
Assign a person to each outcome. That person decides which app to use, what to ask it to do, and when the result is ready to share. If two agents are editing the same note, ask them to state the file version they are working from. Compare the saved versions before choosing which result the team should rely on.
For example, Maya posts a keyboard-shortcuts change and sends Eli the exact file and the behavior to check. Noor can prepare a release note from the accepted decision while Eli investigates keyboard focus. Eli's reply names the tested version and leaves one case open. Noor uses the verified details and asks for a follow-up if the open case affects the announcement.
Check the handoff from a clean chat
Before the next person starts, try the handoff in a clean session. Ask a connected AI to name the Space, open the attached file version, and state the next action in its own words. A clean session is useful because it has none of the sender's conversation to fall back on. If it cannot answer, fix the handoff while the sender still knows what is missing.
Check for three common gaps. The recipient can see the project but cannot tell which conversation to open. The file is mentioned but the exact version is absent. Or the note gives a goal like “finish the review” with no indication of what to inspect or report back. Add the missing detail and retry the same read, so the test tells you what changed.
In a team trial, ask the recipient to post a short reply in the conversation with the version they read and anything that is still unclear. Compare that reply with what the sender intended. The useful result is that a teammate can take the next action without asking for the original chat.
Questions
- How many agents can be in one Space?
- A message can go to up to 10 people. Every plan lets as many people as you like join a Space.
Related guides
- How Winskel worksWhat is an AI handoff, and what goes in one?An AI handoff is a short record one AI shares so another can continue. What a Winskel handoff holds, and how its receipts read.
- Why one SpaceA checklist for handing AI work to a teammateSix checks before your AI hands work to a teammate's AI, so the next agent can continue without asking you to explain it again.
- Why one SpaceWhy your team needs one shared workspace for AIWhen every person uses a different AI app, the work splits into separate chats. A shared workspace keeps one record that every AI reads.