Answers
How can my team see what each other's AI agents are doing?
Claude Code's own history does not give a team that view. An issue opened on 9 July 2026 in the Claude Code repository asked for an organization-wide view of Code sessions, describing session history as private to each seat on a Team plan, and it was closed as not planned on 19 September 2026 after being marked stale. Tools built around one program show one machine: claude-code-kanban, for example, is a local board for Claude Code that listens on the machine it runs on and is described as a single-user setup. Dailybot's site describes another route, agents that post check-ins and a heartbeat the way people do. What a manager needs from a team's sessions is three things — who is working, what needs a person, what stopped and where — and not the conversations. Arroway's cockpit shows exactly that: for a project you share, a teammate's session appears with its state, the program, the project and whose it is, and never its content, and the handoff a session leaves in the project is how the work passes on. You turn the cockpit on from your account after installing; the install page is the first step.
Last updated October 16, 2026
What a manager needs to see, and what they should not
Three things: who is working right now, what is waiting on a person, and what stopped and where. A fourth looks tempting and costs trust: reading what each agent wrote. The Claude Code issue asks for the same split, suggesting as a minimum a first version that shares only titles and summaries, with a click to request access to the rest. Write down before you pick a tool which of the three you need and who may see the content; the answer to the second is usually the person who owns the session.
What each approach shows today
The Claude Code issue describes a Team plan where Recents is private to each seat, handoff takes a share link per session and a new teammate cannot browse earlier sessions, and it lists four earlier issues closed without a resolution. claude-code-kanban, as its README describes it on 16 October 2026, shows tasks as Pending, In Progress and Completed on a board served from the machine that runs Claude Code, reads the files Claude Code writes there, covers Claude Code only and has no multi-machine or team mode. Dailybot's site, last updated on 7 April 2026, describes check-ins and a heartbeat that agents post through the same system as people, with alerts for stalled work; it depends on each agent reporting. As described, none of the three is a view across several programs, for several people, with the content kept by its owner. The Arroway cockpit is built for that: the plugin in each tool reports the state of every session to your account, and the cockpit shows them together, with what needs you first.
When to use Arroway
Use Arroway when your team's agents run in more than one program — Claude Code, Codex, Cursor — and someone needs to see who is working and what is waiting without reading anyone's conversation. In the cockpit, teammates' sessions have their own section, and a teammate's session opens only with a notice that the content belongs to its owner. You can choose to be notified when a teammate's agent starts or stops. A teammate never gets access to another person's agent: when work has to pass on, the session leaves a handoff in the project, and it appears at the top of the next read until someone closes it. Turning the cockpit off deletes the content of your sessions. Notifications are browser notifications and need the cockpit open in some tab; there is no phone app today. The first step is the install page.
What it looks like in practice
Two founders and a contractor share one project. One founder runs Claude Code, the contractor runs Codex and the other founder runs Cursor. At 9 am, before a client call, the first founder wants to know where things stand. In the cockpit, their own Claude Code session sits at the top as needs you. In the team section, the contractor's Codex session shows as working and the other founder's Cursor session as stopped, each with the project and its owner's name. The founder opens neither conversation. The Cursor session stopped after leaving a handoff: where it stopped and the next step. The first founder reads it in the project's next read and picks the work up in Claude Code; they close the handoff when it lands. Nothing here was measured on a real team; the people and the situation are illustrative.
Questions people ask about this
- Can a teammate read my agent's conversation?
- No. A teammate sees that the session exists, its state, the program, the project and whose it is, and only for a project you share. The content belongs to the person who owns the session, and turning the cockpit off deletes the content of your sessions.
- Does it work if my team uses different AI tools?
- Yes for the programs the plugin covers: Claude Code, Codex and Cursor sessions appear in the same list, each with its state. For your own sessions you can allow or deny a Claude Code or Codex permission request from the cockpit; Cursor requests are not answered there.
- How do I try Arroway?
- Install it in the tool you already use — the install page has one route for Claude, ChatGPT, Codex, Cursor or any MCP tool — and sign in when the tool asks. From then on, sessions open by reading the project and close by recording what was decided. The cockpit is off until you turn it on.
Where this is verifiable
Claude Code issue 76162 (github.com/anthropics/claude-code/issues/76162), the claude-code-kanban README (github.com/NikiforovAll/claude-code-kanban) and the Dailybot website (dailybot.com, page last updated on 7 April 2026), all read on 16 October 2026 — each tool is described only as its own pages describe it on that date, and its features can change in any release. Product documentation on this site (How it works, Install), the cockpit operations description in the repository, and the answers on which of your agents is waiting on you and on who answers for an AI agent on a team. Everything described here about Arroway is behaviour the tools apply today, not roadmap. The founders and the contractor in the example are illustrative.
https://www.arroway.app/en/answers/seeing-what-your-teams-agents-are-doing