claude-code - 💡(How to fix) Fix [FEATURE] Add /share command for allow other users see prompts and answers history.

Preflight Checklist

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

Problem Statement

Problem Statement Currently, there is no built-in way to share a Claude Code conversation (prompts and responses) with other users. This creates friction in several common workflows:

Collaboration: When working with teammates on a problem, there's no easy way to show them the full context of a debugging session, design discussion, or refactoring conversation I had with Claude. Knowledge sharing: Useful conversations (architectural decisions, complex bug investigations, learning sessions) are locked inside a single user's local session and cannot be referenced later by others. Support & onboarding: When a junior developer asks "how did you figure this out?", the only options today are manually copy-pasting messages, taking screenshots, or re-explaining everything from scratch. Code review context: Reviewers often lack the reasoning behind a change. Sharing the Claude conversation that led to an implementation would provide valuable context alongside the diff. Reproducibility: When reporting issues or asking for help (e.g., on GitHub, internal Slack), users currently have no canonical way to share what they asked Claude and what it answered.

Proposed Solution

Add a /share slash command that generates a shareable view of the current conversation history. Basic usage: /share # share the entire current session /share --last 10 # share only the last N messages /share --from <msg_id> # share from a specific message onward Behavior:

Serializes the current conversation (user prompts + Claude responses, optionally including tool calls and file edits) into a structured format (JSON + rendered Markdown/HTML). Uploads it to a configurable backend and returns a short URL, e.g.:

✔ Shared: https://claude.ai/s/abc123xyz

The recipient opens the link in a browser and sees a read-only, syntax-highlighted view of the conversation.

Configuration options:

--public / --private — control access (private = only authenticated users in the same org/workspace). --expires <duration> — auto-expire link after e.g. 7d, 30d, never. --redact — strip file paths, secrets, env vars, and tool outputs matching common secret patterns before sharing. --include-tools / --no-tools — toggle inclusion of tool calls and outputs (default: include). A config key in ~/.claude/config.json to set defaults (e.g. default expiration, default visibility, corporate share endpoint for self-hosted setups).

Privacy and security considerations:

Confirm before the first share in a session (one-time prompt explaining what will be uploaded and where). Automatic secret scanning (API keys, tokens, .env contents) with a warning before upload. Allow self-hosted share backends via ANTHROPIC_SHARE_URL for corporate/proxy users who cannot upload to a public service. /share revoke <id> to invalidate a previously shared link.

Out of scope for the initial version:

Real-time collaborative editing of conversations. Forking a shared conversation to continue it in your own session (could be a follow-up feature: /share import <url>).

Alternative Solutions

No response

Priority

Low - Nice to have

Feature Category

CLI commands and flags

Use Case Example

No response

Additional Context

No response