Build together
with Claude Code.

What each teammate needs

• Claude Code with their own Claude account and quota.
• Node.js 22 or newer, Git, and a separate local checkout of the project.
• Access to the shared Git repository. Task branches need push access; GitHub operations use the developer’s own GitHub identity and configured tooling.

The plugin is prebuilt. Installing it does not require building this repository or running a package manager. See the repository’s installation instructions for the full runtime requirements.

1. Install the Claude Share plugin

Run these commands in Claude Code, once on each machine:

/plugin marketplace add cyber1443/session-share
/plugin install ss@session-share

The product is called Claude Share. Its repository, plugin marketplace, and command names remain session-share and /ss:.

2. Connect to hosted sessions

Sign in with GitHub, choose a plan on the account page, then run:

/ss:login https://claudeshare.space

A browser opens to connect the plugin to your account. Check the displayed device code and approve your machine. Back in your project checkout, start a session:

/ss:host

Share the session invite with your teammate. In their own checkout, they run:

/ss:join <invite>

Starter is 19 € per month for one session and up to three people total. Team is 19 € per seat per month with multiple sessions. Each developer’s Claude Code access is separate.

Hosted plan prices include 17% VAT. Secure checkout is hosted on teka.management and invoices are issued by Obrt "SHUSHKA" Cazin. Billing support: info@shushka.tech.

Or host the coordination session yourself

The plugin and coordination server are MIT licensed and free to self-host. In peer mode, one teammate runs /ss:host and shares the invite over a reachable LAN address or tunnel. The host machine needs to stay online for the coordination server to remain reachable.

Peer invites are access credentials: share them only with trusted teammates. For a persistent server with GitHub sign-in, follow the self-hosted OAuth configuration.

How a team works in Claude Share

1. Plan: turn an issue into a shared contract and focused tasks. The validator checks overlapping file paths, dependencies, and acceptance commands.
2. Build: agents claim tasks and lease their file paths while developers work from separate checkouts. The live board shows shared progress.
3. Verify: run task acceptance checks and test the assembled application. Reopen work that needs changes.
4. Review: bring the result into a shared integration pull request for human review.

Claude Code and GitHub are supported today. Jira, Slack, and Linear integrations are in development and are not yet available.

What stays on your machine

Claude Share does not share Claude accounts, resell subscriptions, or proxy inference. Each agent runs on its developer’s machine using that developer’s account and quota. The coordination server stores session state and room messages; code follows your normal Git workflow.

Hosted sessions keep the coordination state available while a laptop sleeps. They do not keep that laptop’s AI agent running. Other teammates with connected agents can continue working.

File leases reduce accidental edit collisions. They are not a security sandbox: shell writes can bypass the checks, and lease checks fail open when the server cannot be reached. Read the security notes before choosing a deployment model.

Next step

Open your hosted account or explore the source repository. The product FAQ answers common setup and collaboration questions.