Hi Product Hunt! 👋 During code reviews and bug investigations, I often want to ask a teammate: “Can I see what you discussed with your coding agent?” I want to know what context the agent had, which code it checked, whether an edge case came up, and which conclusions were actually verified. A pasted answer rarely carries all of that. Rewriting it in your own words doesn't recover the missing context, either. That led me to build Team Cross around a simple idea: your AI session can be your question, your answer, or the starting point for someone else to help. Team Cross lets you select and preview conversations from Codex or Claude Code, then share them in a collaboration space. Multiple people can contribute multiple conversations, annotate specific passages, and reply in context. References stay tied to the version being discussed, even when the shared material is updated. Take an issue with event tracking in a frontend app. It may involve how the backend passes down trace IDs, how the native app processes events, changes in a cross-platform container, and the data warehouse’s ingestion requirements. You also need to understand what the product team wants to measure. The person investigating may only have context for part of that system. With Team Cross, you can share the session where you started investigating. Backend and client engineers can contribute their own sessions, while product teammates add the business context. Each person can ask their own agent to read the shared material through MCP, check the assumptions against what they know, and bring new findings back to the discussion. When you need to work on the code together, you can start a shared native Codex session, grant execution access, and explicitly hand over input. One person controls input at a time. The same approach helps when a product colleague builds a small feature with AI and needs an engineer to check the implementation. AI lets more people contribute, and that makes access to other people's experience and judgment even more valuable. I've seen plenty of demos that connect the entire development process into an automated workflow. In everyday work, an experienced teammate noticing one missing constraint can still change the direction of an investigation. I wanted to make it easier for that person to join, with their own tools and agent. That also shaped the setup. Team Cross hosts collaboration spaces and shared execution on the initiator’s Mac. Teammates on the same local network can connect directly. For collaboration across networks, experimental Tailcat support is available where your team’s network policies allow it. There’s no separate Team Cross account to create or centralized collaboration platform to deploy. That context remains useful when you’re working on your own, too. Your personal library lets you revisit previously shared session material and annotations. You can ask your current agent to read selected context, cross-check findings and decisions across sessions, and pick up work you’ve already started. Team Cross is available for Apple silicon Macs running macOS 14 or later. https://teamx.is-a.bot/en https://github.com/YTwsy/Team-Cross

Vercel Day

Which Vercel product did you use? What new capability did it give your team, and how did that shape the product you launched?

Maker

Vercel could host a standalone Team Cross website with a landing page, setup guides, and links to the demo and downloads. Preview deployments would make it easy to review website changes before publishing.

2mo ago

📌

Team Cross

Bring teammates into your Agent sessions. Discuss & Continue

Bring teammates into your Agent sessions. Discuss & Continue