[FEATURE] Share Claude Code chat sessions with team members

Resolved 💬 3 comments Opened Mar 30, 2026 by sorenvedstesen Closed Apr 3, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Summary

Add the ability to share Claude Code conversations with team members — via shareable links, exportable files, or within a shared workspace/project.

Problem

When working on a codebase with a team, useful context from Claude Code sessions — debugging sessions, architectural decisions, code explanations — stays locked to the individual who had the conversation. This leads to duplicated effort, lost context during handoffs, and slower onboarding.

Proposed Solution

Support for sharing chat sessions with teammates, including:

  • Read-only sharing — so others can review the conversation
  • Optional continuation — so a teammate can pick up where the conversation left off
  • Team/org integration — works with existing team and organization structures

Use Case

Our team frequently uses Claude Code for debugging, architecture discussions, and code generation. Being able to hand off or review each other's sessions would improve collaboration — especially when someone is out or when onboarding new team members.

Prior Art

This was previously requested in #10368 (now locked). The core need remains unaddressed.

Proposed Solution

Proposed Solution

We're not prescribing an implementation — that's for the team to design — but the
desired outcome is: a way to transfer useful session context to a teammate, either
as a shareable link, an exportable file, or within a shared workspace.

Workaround (until a native solution exists)

At the end of a session, ask Claude:

"Summarize this conversation as a handoff prompt a teammate can paste at the start of a new session to pick up where we left off."

This works but is manual, lossy, and requires the original user to remember to do
it. A native solution would be far more reliable.

Alternative Solutions

_No response_

Priority

Critical - Blocking my work

Feature Category

CLI commands and flags

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗