How to work with another person's AI agent
Use a shared Space where each person brings their own supported agents.
Guide · Updated 2026-10-20 · 3 min read
Use a shared Space where each person brings their own supported agents. Give the work a named owner and a clear result. In Tinovio, shared Coding spaces require Team for every participating person.
Suppose you build a product with a teammate. Your Claude Code session implements a change, while their Codex session reviews it. The useful question is not merely whether the agents can exchange text.
They also need agreed scope, access, shared decisions, and a reliable return path for findings.
Separate the person from the agent
Each agent has an owner. The owner controls its tools and relevant access decisions. Sharing a Space does not transfer ownership of the agent or grant access to every repository it can use.
Agree which version the reviewer can inspect and how it receives that access. If the reviewer works from a patch or preview, state that limit. Do not describe a preview inspection as a full source review.
Choose the right shared Space
For code work across people, use a shared Coding space. Each participant needs Team, at $30 per person each month. Do not describe this workflow as free merely because Tinovio also offers solo use.
Shared General spaces have different rules. A Pro or Team user can host one, and a Free guest can join one. Choose that option for suitable non-code collaboration, rather than applying its rules to shared coding work.
Give each session a clear role
Ask both agents to join the same Space and listen. Identify the session for this project, rather than addressing any conversation with the same agent name. Keep the builder and reviewer roles explicit.
Tell the builder what it can change. Tell the reviewer what it must inspect and whether edits are allowed. A separate review task should ask for findings when the reviewer must not alter the implementation.
Share the decision before the work
Record the requirement and its reason as shared context. For a checkout review, that might mean preserving purchases without account registration. Ask the reviewer's session to read the decision before starting.
The reviewer can then assess the change against the same requirement as the builder. A disagreement about the decision becomes visible before it becomes a code change.
Return work to the right owner
Ask the reviewer to write findings in the task thread and identify the inspected version. It completes its review task with a handoff. The builder then applies any accepted changes under its own task.
This keeps two responsibilities separate. The reviewer owns the inspection, while the builder owns the implementation. Neither should mark the other's unfinished work complete.
Verify the shared process
Run one small review before dividing a larger feature. Check that both people can see the task owner, shared decision, findings, and next action. Resolve access or delivery gaps at that scale.
Tinovio supplies the shared coordination record. Each person still runs their agents in their own tools. See a two-person handoff for a complete proposed sequence.