Transcript sharing fails from the Claude-initiated share prompt

Status Open
Reported on v2.1.241
Maintainer reply None cached
Activity 0 comments · opened Aug 24, 2026

What happens

When Claude asks whether I'd be willing to share the session transcript — the model-initiated prompt, not a /-command — accepting it does not result in a shared transcript. Sharing appears not to go through.

Environment

  • Claude Code 2.1.241
  • macOS 26.6.2
  • zsh

What I can't yet tell you, and why

I don't have the exact failure text. The prompt is model-initiated and appears mid-session, so it isn't reproducible on demand, and there's no local artifact to inspect afterwards — nothing under ~/.claude records a share attempt or its outcome.

That gap is itself part of the report: a failed share leaves no trace a user can find. There's no error surfaced afterwards, no entry in any log, and no way to check whether a share succeeded. If sharing writes any client-side record, pointing at it here would let people supply the detail this issue is missing.

Why it was filed by hand

The in-product path is blocked. /feedback returns 403 (#55348, open since 2026-05-01 and still reproducing on 2.1.241 — I've added a datapoint there), so a report about transcript sharing could not be submitted through the built-in flow. One broken reporting path preventing a report about another.

Possibly related, but not the same

  • #74814 and #83642 — the same consent prompt, but the opposite failure: sharing happening accidentally from a stray keypress. Both suggest this prompt's accept path has had trouble before.
  • #59248 — silent retention cleanup deleting transcripts. Worth ruling out as a cause: if the transcript has already been cleaned up, a share of it would presumably fail, and that failure would look exactly like this from the user's side.

What would help

  1. Does the share succeed silently and only the confirmation is missing, or does it genuinely fail?
  2. Is there any client-side log of share attempts? If not, adding one would make this class of report answerable.
  3. Surfacing an error on failure — currently the prompt accepts and nothing observable follows either way.

View original on GitHub ↗