[FEATURE] Teams/Enterprise: org-wide shared view of Code sessions (Recents) with default-share policy

Problem

On a Claude Team plan, the Code tab's session history ("Recents") is private to each individual seat. There is no way — no admin setting, no user setting, no org policy — for an organization to have a shared, team-wide view of Code sessions and the work done in them.

For a team account this is a major functionality gap. We run a web agency (WebJIVE) where Claude Code sessions are the work log: client site builds, SEO work, migrations, bug fixes. Today:

• The owner/admin cannot see what sessions exist across the org, only usage metadata.
• Teammates cannot see each other's sessions at all, even ones done for the same client project.
• Handing off work means manually creating a share link per session — nothing is discoverable.
• New teammates can't browse prior sessions to learn how the team works.

The "Team" plan effectively covers billing and seat management, while the actual work product stays siloed per person.

Prior issues

This has been requested before, but every prior issue was auto-closed by the triage bot without resolution:

• #10368 — "Chat Package Export/Import: Git-compatible format for team collaboration" (closed, autoclose)
• #40981 — "[FEATURE] Share Claude Code chat sessions with team members" (closed as duplicate of #10368, which is itself closed)
• #11455, #18230 — related, also closed

So the request currently has no open representation despite recurring demand. Filing fresh per the bot's instruction ("please file a new issue and reference this one").

Proposed solution

An org-level capability for Team/Enterprise plans:

1. Org-shared Recents view — an admin-enabled mode where Code sessions created under the org are visible (at least title + metadata, ideally full transcript) to other org members, in a "Team" section of the Code sidebar.
2. Default-share policy — an org setting: sessions default to private, team-visible, or admin-choice, with per-session override (mark a session private for sensitive work).
3. Project/repo grouping — team-visible sessions grouped by repo/project so a teammate can open "Helena Hospital site" and see every session anyone ran against it.

Even a v1 that only shares session titles + summaries org-wide (with click-to-request-access) would be a huge improvement over total invisibility.

Why this matters commercially

Agencies and dev teams evaluating Team/Enterprise expect "team" to mean shared visibility of work, the way it does in every other team SaaS (Figma, Linear, Notion). Right now the collaboration story is: share links one at a time, or push artifacts to git and reconstruct context manually. That undersells what Claude Code is actually doing for teams.

Environment

• Claude Code desktop app (macOS) + claude.ai/code, Claude Team plan
• Org: multiple seats, mixed Claude Code CLI/desktop and claude.ai users