jaynlabs/jaynshare

Share your claude subscriptions ! multi-account claude code router - jaynlabs/jaynshare

13 stars · 0 forks

README

jaynshare You can share your Claude subscriptions! jaynshare is a self-hosted proxy for Claude Code (or third party hosted if you have trust to spare). After hosting a server, connecting several accounts to it and enrolling a client, replace claude by jaynshare claude and you will be able to choose from which account to draw for your session. Server works on Linux and Docker, client works on macOs and Windows. WarningPooling Claude subscriptions conflicts with Anthropic's published terms and can lead to suspension or termination of every account involved, without a refund. Whether a particular deployment also raises legal issues depends on its facts and jurisdiction; this project does not claim that it is legal or authorized. Read the subscription-sharing risk summary, the security and privacy model, and the operator obligations before deploying.

Short demo

This demo was v1. Pretty much still the same but v2 is now in Rust and CC config changes are less invasive. Purpose and disclaimers This is a project by Jayn Labs started by my friend and I cause we were sick of getting rate limited while the other had plenty leftover quota. PLEASE, yes this was GREATLY done with AI. No matter your opinion on the matter, feel free to give us feedback. Reworking everything from the ground up is not something frightening us. So truly feel free to give any feedback (even to roast us), as long as it helps us improve. Oh, and yes, we've seen Team Claude on github. We were inspired by their project. To be fair, our v1 was mostly a fork of their code, that's why we've done v2 in Rust to make this codebase our own and not just a fancy fork. This was not made by, endorsed by, or affiliated with Anthropic; Claude Code is a product of Anthropic. Importantjaynshare is a "trusted" intermediary, not an E2E encrypted relay. The server receives EVERYTHING in plaintext so it can route and retry them. A server operator—or anyone who compromises the server—can read or alter that traffic. Only use a server whose operator and deployed code you trust.

Highlights

OAuth subscription and API-key accounts An account picker at launch and a Claude Code status line naming the serving account Private client enrollment for macOS and Windows, with a secret per client, rotation and revocation Private-network listeners only, optional TLS, and an audit log that never holds a body or a credential Signed releases, a native systemd install and a rootless Docker Compose kit One Rust binary for the server and the client

Requirements for self hosting

A Linux server with systemd, or rootless Docker Engine 28 (or newer) for the Compose kit A private network between the engineers and the server, such as a tailnet (but I'm sure you can make it work with other clever solutions) Claude Code already installed on each engineer's machine

Quick start Server From the releases page, download and extract the archive for the server's platform, and download the client kit (jaynshare-2.0.0-client-kit.zip) beside it. As root, in the extracted directory: ./jaynshare release fetch 2.0.0 --out ./release ./jaynshare config new --out ./jaynshare.toml $EDITOR ./jaynshare.toml ./jaynshare server preflight --config ./jaynshare.toml --from ./release ./jaynshare server install --config ./jaynshare.toml --from ./release The install puts jaynshare on the search path. Operator commands run on the server as its service account: alias js='sudo -u jaynshare -H jaynshare' js account login --name alice js status

One engineer's enrollment bundle:

Extract the enrollment bundle from your operator into an empty directory. Run its installer with the one-time code sent through a separate channel. Run jaynshare claude wherever you would have run claude.

jaynshare claude opens a picker when the pool cannot choose for you; --account <name> names the account, --auto lets the pool pick, and --direct runs Claude Code outside the pool under your own login. Arguments after -- go to Claude Code unchanged. jaynshare status checks enrollment and connectivity, and jaynshare alias prints a shell alias so that claude itself goes through the pool. The bundle's README.txt documents installation in detail. Roadmap / Ideas

Rust v2 jaynshare codex API-key subscriptions from other providers, like OpenCode Go Account features (settings, plugins, skills, MCP servers) when you draw from your own account (the pool refuses them for everyone today) Owner limits: cap what the pool draws from you, and pause it yourself Draw credits: what you can draw from others' accounts follows what you give the pool Linux client installer

Documentation

Is subscription sharing safe? Security and privacy model Server installation and operator obligations Release tooling jaynshare help and jaynshare help <verb>: every verb, its options, exit codes and examples

Development Rust 1.95 (rust-toolchain.toml pins it). Nothing in the build or the tests needs credentials or network access to Anthropic. cargo build --release cargo test --bins # unit tests JAYNSHARE_BIN=target/release/jaynshare cargo test --release --test acceptance cargo clippy --all-targets -- -D warnings cargo fmt --all -- --check CI runs the above and the platform image build; see .github/workflows/ci.yml. The acceptance tests that need Linux run in Docker and are skipped where no Docker daemon answers. Where things live:

src/ — the server, the client and the CLI deploy/ — the reference Compose deployment, the server notes, the release key (release-key.pub) and the client-kit installers (kit/) tools/release/ — cross-builds, packaging, signing and publishing Dockerfile — the minimal platform image

Issues and pull requests are welcome; open an issue before a large change. Report security issues privately as described in SECURITY.md. License MIT, © Jayn Labs. See LICENSE, and NOTICE.md for the Rust crates Jaynshare links.

source