SESSION-FIRST COLLABORATION

Your tools are
where collaboration begins.

Bring together the findings already captured in everyone's Codex and Claude Code Sessions.
When it is time to act, hand off input to a teammate and keep going in the shared Session.

See collaboration in action Download for macOS

No cloud backendWebGUI is optionalEveryone brings their own Session material

Collaboration demoExample content

Put everyone's Agent material to work.

Choose a step, or press play to watch the current flow.

Lin, Mei, and Kai each select part of a completed Session. Findings from different Agents come together here.

Lin's SessionCodex

Sign-in redirect investigation

Start from an investigation already in progress

Earlier conversation was not selected for this share

Published range · Turns 2–3

02 · Locate the issue

Why does sign-in redirect to an external address?

03 · Check the implementation

The redirect parameter has no same-origin check.

Select this range, then preview before publishing

Personal Session stays privateYou control the published scope

Bring each finding together

Material
Citations
Discussion

Kai · CodexInternal redirect convention

Turns 1–2 selected

Mei's SessionClaude Code

External redirect reproduction

A reproduction your teammate already completed

Earlier conversation was not selected for this share

Published range · Turns 4–5

04 · Reproduce

Try an external URL and a protocol-relative URL.

05 · Check the result

Both forms reproduce the issue and need the same check.

Select this range, then preview before publishing

Personal Session stays privateYou control the published scope

Each person brings one selection into the discussion.

Selected ranges · Open to preview

You bring the investigation; teammates add a reproduction and a project convention. Start from work each person has already done.

Read-only sharing · Authors publish later turns deliberately

Reading and discussion are a complete collaboration.Selected scope · Fixed versions · Everyone contributes

One current input holder at a timeExecution: Lin's Mac

LinCan continue typing

MeiReading and discussion

Lin's collaboration SessionCodex

Fix the sign-in redirect

~/projects/checkout · New native fork

›Material and discussion are ready. Waiting for the next input.

src/auth/redirect.tsconst next = params.get('next');

Created a new collaboration fork from the selected source

›Lin can enter the next step…

Session and execution stay on this MacCurrent input holder

One collaboration Session

Native fork
Input handoff

Mei's collaboration viewCodex

Continue together after the discussion

Existing material and discussion remain available

Lin enables collaborative execution. Mei and Kai can keep reading, publishing material, and discussing.

Connected to the shared Codex Session; personal Claude Code material remains available.

Follow shared progress and keep discussing

Kai · Discussion continues

Remember to preserve valid internal redirect paths.

Reading and discussion remain openInput with Lin

Other teammates can keep reading, publishing material, and discussing throughout.

Execution stays on the host machine while everyone uses their own client.New native fork · Explicit execution access · Input handoff

A request for help can stay lightweight

“Could you take a look at
this Session?”

Collaboration should be able to start with that sentence.

Continue together from the work already in progress.

Keep your workspace and your habits.

A short collaboration should not require moving the team into a new project system. Keep the terminal, clients, and project organization you already use, and begin with one specific Session.

Put everyone's investigation to work.

Share how you tracked down the issue while a teammate adds their reproduction. Bring evidence from different Sessions together, cite exact versions, and discuss it beside the source.

Choose the depth of participation for the work at hand.

Start by sharing selected material and inviting teammates to discuss it. When you need to work together, enable execution, hand off input, and continue in a new native collaboration Session.

The Agents you already use, through the Agent clients you already use to organize them

Codex·Claude Code·T3 Code·Paseo·Lody·Warp + Tmux·Herdr

Collaborate around native Sessions that Team Cross can connect to. See the documentation for each release for the exact integration scope.

Join lightly and still make a real contribution

Choose the way to participate that fits.

Offer a review, bring your investigation, ask your Agent to help, or take over input yourself.

Bring what you found into the room.

Select a range from your own Codex or Claude Code Session, preview it, and publish it into the same space. Every teammate can contribute multiple pieces of material, turning prior investigation into shared evidence.

Authors publish later updates deliberately; existing citations keep the version they referenced.

Mei's collaboration viewMaterial and discussion

Share turns 2–3 from my reproduction.

Published Session material · scope previewed

External redirect reproduction v1 is published. The team can cite it alongside Lin's investigation.

Open the WebGUI when a shared view is useful.

Read material turn by turn, expand tool activity, and discuss it beside the source.

Change the distance, not the way you work

Collaborate directly on the same LAN.
Across networks, choose Tailcat.

Choose the connection that fits this collaboration. Your clients, the shared Session, and the way you already work all stay in place.

No cloud backendNo Tailscale account required

HostLin's Mac

Direct LAN

ParticipantMei's Mac

Both people are on a mutually reachable LAN, so the connection is established directly between their machines.

This collaboration explicitly uses the local network.

Product direction under exploration

When the work needs your judgment,
collaboration can begin.

We are exploring a future where an Agent on a hosted machine can invite a person when human judgment is needed, bring the work into the tools they know, and continue along the original Session.

Agent-initiated invitations

An Agent deciding when to invite a person remains a product direction, not a current capability.

Agent on a hosted machineWorking through a specific task

Collaboration invite · Product direction

“I need your judgment here.”

Review the context, offer an opinion, or take over this part.

Open in the client you know

A few things you may want to know first

Start with what you need to do.

Read the full documentation (Chinese)

Team Cross for Mac

Start with the next
“Could you take a look?”

Choose a Session worth discussing and invite teammates to bring what they found.

Download for macOS

macOS 14+ · Apple Silicon · v0.2.1 stable release

Or start from the terminal

Install the stable CLI

brew install YTwsy/teamcross/teamcross

Choose either distribution method when installing the App and CLI.

Installation and current support (Chinese)

Your tools are where collaboration begins.

Put everyone's Agent material to work.

“Could you take a look at this Session?”

Keep your workspace and your habits.

Put everyone's investigation to work.

Choose the depth of participation for the work at hand.

Choose the way to participate that fits.

Bring what you found into the room.

Collaborate directly on the same LAN. Across networks, choose Tailcat.

When the work needs your judgment, collaboration can begin.

Start with what you need to do.

Can I use Team Cross just to share an investigation?

Can several teammates participate together?

Will new conversation turns become public automatically?

Do we have to use the Team Cross WebGUI?

What happens when we need to change code together?

Do I need to copy my teammate's repository onto my Mac?

Which systems and native clients are currently supported?

Start with the next “Could you take a look?”

Your tools are
where collaboration begins.

“Could you take a look at
this Session?”

Collaborate directly on the same LAN.
Across networks, choose Tailcat.

When the work needs your judgment,
collaboration can begin.

Start with the next
“Could you take a look?”