[FEATURE] Live, read-only share link for a running session, with comments

Status Open
Maintainer reply None cached
Activity 0 comments · opened Oct 11, 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

Pairing on work that Claude is doing today means screen sharing. The person watching can't:

  • scroll back
  • open a diff
  • comment on a specific step

Reviewers who come later only see the final PR, not the decisions that led to it. For teams adopting Claude Code, seeing how a teammate works with it is also how people learn.

Proposed Solution

  1. /share creates a link scoped to the org, which can be revoked, to a live view of the session: the transcript, tool calls and diffs as they happen. Existing secret redaction applies.
  2. Viewers can comment on a specific turn or edit. Comments appear in the owner's session, and are only sent to the model if the owner forwards them.
  3. Optional approver role. The owner can let a teammate approve permission prompts, for example a senior engineer approving a migration.
  4. Sharing ends when the owner stops it or the session ends. A read-only snapshot can be kept to link from the PR.

Alternative Solutions

  • Screen sharing: live only, no history, no comments.
  • Exporting or pasting the transcript afterwards: not live, and loses the diffs and tool structure.
  • Related, closed: #27702 (live shareable session view) and #86666 (sharing a session with teammates).

Priority

Medium - Would be very helpful

Feature Category

Other

Use Case Example

  1. I'm about to let Claude refactor our payment module and run /share for my tech lead.
  2. They follow along between meetings and leave a comment on turn 14: "don't change the retry policy here, finance depends on it".
  3. I forward the comment to Claude, which adjusts. The tech lead approves the final migration prompt from their own machine.
  4. The snapshot link goes into the PR, so later reviewers can see why each decision was made.

View original on GitHub ↗