Skip to content

Team collaboration for coding agents

Team collaboration for AI coding agents lets teammates, and their agents, build on each other’s work. That means the same rules for every agent, a view of each other’s sessions, and the history of what was tried. Most coding agents share work only inside their own product and cloud.

Hansard Teams share whole conversations from chosen repositories across harnesses, through storage your team controls. Each member’s agents can search what teammates’ agents did, whichever agent they use.

What is the best way for a team to collaborate with AI coding agents?

Section titled “What is the best way for a team to collaborate with AI coding agents?”

It depends on what your team needs to share. Most teams combine these:

  • Shared rules: commit instruction files to the repository. AGENTS.md at the repository root is read by Codex, Cursor, GitHub Copilot, Amp, and Devin, and by Claude Code when the folder has no CLAUDE.md. Every member’s agent then follows the same rules, with no plan or account.
  • Sessions in one vendor’s cloud: if everyone uses the same agent product, its team plan lets teammates open each other’s cloud runs. Cursor cloud agents, GitHub Copilot cloud agent, Amp threads, and Devin sessions work this way.
  • Requests from chat: Slack apps from Anthropic, OpenAI, Cursor, and Devin start agent runs from a thread, so the team sees the request and the result.
  • History across harnesses: when teammates use different agents, or run them on their own computers, share the conversations themselves. Hansard Teams do this, and each member’s agents can search the shared history.
Option What teammates share Where it lives Plan Other vendors’ agents
Instruction files Rules in AGENTS.md, CLAUDE.md, .cursor/rules, or .github/copilot-instructions.md The repository None AGENTS.md is read by most coding agents
Claude Code Read-only links to Claude Code on the web sessions, and Claude Tag runs and channel memory in Slack. Agent teams coordinate one person’s sessions, not a team of people. Anthropic’s cloud. Agent teams run locally. Team visibility for shared sessions, and Claude Tag, need a Team or Enterprise plan Claude only
Codex Read-only snapshots of a thread, and shared cloud environment setups, not tasks OpenAI’s cloud Snapshots on every Codex plan. Environment sharing is documented for Enterprise workspaces. Codex only
Cursor Team Rules, cloud agents teammates can view, and steer when an admin allows team follow-ups, shared transcripts, and Slack Cursor’s cloud Team Rules and shared transcripts on Teams and Enterprise. Cloud agents on Premium and higher. Cursor only
GitHub Copilot cloud agent Session logs and pull requests, visible to anyone with access to the repository, and repository facts in Copilot Memory GitHub Paid Copilot plans Claude and Codex agents run from the same Agents tab in preview, without steering
Amp Threads shared with the workspace or by link, and several people prompting one live thread Amp’s cloud Team sharing at no extra charge. Group visibility on Enterprise. Amp only
Devin Organization playbooks, skills, and environment snapshots, and sessions that follow a Slack thread Devin’s cloud A Teams plan to invite members Devin only. A handoff plugin passes tasks from Claude Code, Codex, or Cursor to Devin.
Hansard Teams Whole conversations from chosen repositories, shared project boards, and optional messages between teammates’ agents A bucket or shared folder your team controls Free Every harness Hansard imports

Each row was checked on 2026-11-08 against the vendor’s own documentation. Plans and features change often, so follow the links under Sources for current details.

  • A manager creates a Team with rules that name repositories, repository owners, or folders, and picks the storage: a Google Drive, Dropbox, OneDrive, or iCloud Drive folder, or an S3-compatible bucket such as Cloudflare R2 or Amazon S3.
  • Each member’s Hansard uploads every matching conversation whole, with its tool calls, and receives the others’ conversations read-only, labeled with the person and device.
  • Each member’s agents can search the conversations teammates shared with the same recall tools they use for their own history.
  • A shared project board keeps the threads agents and people post about a project. Teammates see each other’s live sessions in shared projects: the agent, the project, the git branch, and whether it is busy.
  • With agent messages allowed, a teammate’s agent can send your agents a request. By default nothing starts until you approve it.

See Teams and Slack.

  • Hansard runs no hosted service for Teams. Your team provides the storage, and agent messages need a relay your team runs.
  • A Team shares conversations, not memories. Memories stay on each computer.
  • Received conversations are read-only. A teammate cannot type into your running session.
  • Every member installs Hansard. Agent messages also need the desktop app for macOS on each computer.
  • A Team uploads full transcripts. Message text and tool output can hold paths or material outside the Team’s rules, and redaction replaces only known secret patterns.

How do I share coding agent context with my team?

Section titled “How do I share coding agent context with my team?”
  1. Commit shared rules to AGENTS.md at the repository root.

  2. In Hansard, open Teams in the dock, select Create a team, and add the repositories to share under What should the team share?.

  3. Select Copy invite and send the invite to each teammate. Each teammate opens Teams, selects Join a team, and pastes it.

  4. Install recall in each member’s agents, so they can search the shared conversations:

    Terminal window
    hansard integrations add-to claude

    Replace claude with codex, cursor, or another agent.

See Teams for the CLI, storage access, and the rules each member accepts.