Team sessions — shared, portable sessions developers can hand off and contribute to

Problem

A Claude Code session is bound to one machine and one person. Transcripts live as local .jsonl files, session IDs aren't portable across machines, and --resume only works against your own local store. /export is one-way and lossy — a flat text/markdown dump with no structured tool/file context and no ability to continue the thread. There's currently no way for a team to share ownership of a session.

Proposed capability

Team/org-scoped sessions that aren't tied to a single machine, supporting:

1. Handoff (sequential) — Dev A finishes, hands the session to Dev B, who reads and continues with full fidelity (tool history, file references, decisions) rather than a lossy paste.
2. Contribution (shared/async) — multiple members add to the same session thread over time, with per-message author attribution.
3. Live collaboration (concurrent) — stretch / fast-follow — multiple members in a session at once. This is a much larger lift (live sync, concurrency, conflict handling); noted here for roadmap coherence and could be split into its own issue.

Foundation (shared by all three)

• Portable session storage at the account/team level
• Identity + access scoping
• Expiring / revocable access
• Secret redaction
• Opt-in

Motivation

Common team scenario: one developer investigates a problem with Claude and lands on a recommendation (e.g. diagnosing an API timeout config and deciding on a value plus rationale). They want to hand it to the developer who'll implement it — with full context — or have several teammates contribute to the same investigation. Today that context is stranded on one machine.

Why one request

All three build on the same foundation (portable, team-scoped sessions with identity and access control). (1) and (2) are the near-term value; (3) is a natural extension. Filing them separately would duplicate the foundation discussion.