self-hosted · open source · MIT

Share your terminal.
Keep your keys.
Revoke anytime.

Give anyone a live seat where your AI codes — share Claude Code, share Codex, share OpenCode. Links that expire. Guests you can kick mid-keystroke.

$ npm i -g second-seat && second-seat share -- --tunnel

how it works

Three moves.
Then you're sharing.

01

Run one command

npm i -g second-seat once, then second-seat share -- --tunnel starts the relay, serves every connection, and opens a free public URL. No ports. No accounts to configure.

02

Send a link

Pick an expiry — a day, a week, a month. Each share is its own revocable token. Everyone signs in; nobody sees your passwords.

03

They're in your terminal

Your guest opens the link and gets a real PTY on your box. Done with them? Revoke. They're gone instantly.

why it wins

Built like infrastructure.
Priced like air.

Everything runs on hardware you already own. There is no server bill because there is no server.

Links that die on schedule

One day, seven days, thirty days, forever — plus one-click revoke that drops guests mid-keystroke. Everyone else is unaffected.

A real terminal, not a chat box

Full PTY streaming. Claude Code, Codex, and OpenCode sessions render properly. Resize syncs both ways.

Approvals, transcripts, kicks

Gate shares behind manual approval, follow every session in the transcript view, remove guests that shouldn't be there.

Private cloud backup

Push every session's files to a private repo. Preview first, then confirm. Later pushes append — nothing duplicates.

One seat is one human. Sharing a machine is fine. Sharing a subscription gets accounts banned. Guests bring their own quotas — your keys never cross the wire.

start

Your terminal,
two minutes from shared.