claude-share

claude-share is a small command-line interface (CLI) that lets you share your Claude Code subscription access with friends through a pairing link. It is designed so the receiving machine does not get your Claude access token, and you can revoke access instantly.

The workflow is split into two parts: the sharing machine runs the claude-share proxy, and the friend connects using claude-connect with the generated pairing link.

Key Features

One-command setup: Install the CLI globally with npm install -g @0xpv/claude-share, for quick local use on macOS and Linux.
Pairing-link sharing: Generate a pairing link you send to a friend, which establishes a temporary saved connection on their side.
Token not revealed to the friend: The architecture proxies Claude CLI traffic through the sharing machine and injects the Claude API bearer token server-side, so the receiving machine does not receive an access token.
Instant revocation by stopping the sharer: Quitting the CLI shuts down the local proxy and disconnects everyone immediately.
Network routing via proxy/tunnel (with notes on mode): By default it works best on a LAN; it also mentions an experimental public mode using bore.pub for remote friends.

Install claude-share on the machine that will share access: npm install -g @0xpv/claude-share
Run the CLI to generate a pairing link and share that link with your friend.
Have your friend connect by running claude-connect, then entering the pairing link to establish the session.
Keep the sharing machine available: you need to keep the machine awake while sharing because the CLI runs a local proxy.

Use Cases

Side-by-side Claude Code usage on a shared project: Teams or pairs can use the same Claude Code subscription for short collaboration sessions by connecting each friend through a pairing link.
Temporarily granting access for onboarding: You can share access while a friend learns or validates a workflow, then revoke it by quitting the CLI.
LAN-based sharing for remote dev setups: When both machines are on the same local network, claude-share is described as working best.
Remote access for trusted collaborators (experimental): If your friend is not on the same LAN, you can use the experimental public mode via bore.pub as described.
Controlled access sessions: Because the proxy is tied to the sharing machine’s running process, you can stop sharing at any time to disconnect immediately.

FAQ

Does my friend receive my Claude access token? No. The described architecture proxies traffic to the sharing machine and injects the bearer token server-side, while the friend’s machine does not reveal an access token.
What happens if the sharing machine sleeps or the CLI stops? Friends get disconnected immediately if the machine sleeps or the process exits, since the CLI runs a local proxy.
Can I revoke access without reconfiguring anything? Yes. Quitting the CLI shuts down the proxy and disconnects everyone instantly.
Does it work over the internet? It works best on a LAN, and an experimental public mode is available via bore.pub for remote friends.
Is it safe to use with anyone? No. The project explicitly warns to only share with people you fully trust, because the sharing machine’s proxy can intercept Claude Code chats by design.

Alternatives

Use separate subscriptions/accounts per user: Instead of proxying and sharing access, each user signs in with their own subscription to avoid token-handling and trust concerns.
Other CLI-based proxy approaches: For developers comfortable with networking setups, you could look for tools that forward or proxy API traffic locally; these typically differ by how they handle credentials and what portion of traffic they can observe.
Team access via official account management (if available to you): Where available, using an official sharing or team-access mechanism (rather than a custom proxy) can reduce operational risk compared to running a local proxy that intercepts chats.