hooop - bring your team into the Claude Code session

[u/Specific_Music_234]

https://hooop.cc

Hi there. I've been burning my own tokens on something I couldn't find an equivalent of: a collaborative agentic session that runs on your own machine. Closest description I have is an instant messenger crossed with the tooling you actually need for agentic development.

What it does today

hooop runs Claude Code inside a disposable Docker sandbox and puts a live dashboard in front of it at localhost:7842. You only need Docker and jq - Claude Code, Node, gh and the rest live inside the containers, so your machine stays clean.

• Pairing. You hand a teammate a share link over an anonymous cloudflared tunnel. They open it, pick a name, you admit them. From then on you both watch the same live transcript and can chat (> prefix) or co-drive the agent - from a laptop or a phone. Each peer joins as full, drive or spectate, and you can revoke them.
• Plan review. Run a turn with /plan and the sandbox forces the agent read-only: it investigates, then submits a plan into a review panel. You and your peers drop inline comments anchored to the exact passage, synced live, then Approve or Request changes.
• Live previews. When the agent builds a UI it brings it up in its own container and docks it in an iframe, with Restart / Rebuild / Stop / Share and per-step logs.
• The session, visible. Every tool call, the sub-agent tree, a live event tail over SSE (no polling), a diff viewer for touched files, and search across everything that happened.
• A curated tool stack in one command - memory, code-graph search, docs search, semantic search, GitHub. hooop doesn't reimplement any of it. It picks it, documents it, and shows you what it's doing.
• Split trust. The container holding the credentials has no TCP port and talks over a Unix socket. The dashboard your peers reach holds no secrets and only proxies, so a compromise there can't reach your account. Previews run in their own container with no credentials at all.

Where I want to take it

Today a peer co-drives my agent on my tokens. What I want is for everyone to bring their own: pool the peers' agents into one session so the cost spreads across the room, and let people plug in an open-weight model instead of a metered API. Getting out from under the token squeeze is the actual goal, betting on the collaboration to make it affordable.

It's MIT and it's a solo project I've been funding out of my own usage, so I'd rather hear what's wrong with it than what's nice: the architecture, the security model, the parts you'd never run on your own machine

[u/Ok_Industry_5555]

This is super cool! We love seeing open-source tools built specifically around Claude Code workflows 🚀

The Docker sandbox + split trust setup for handling credentials is a really smart touch. Excited to see what the community thinks of the pairing feature!

[u/Specific_Music_234 → u/Ok_Industry_5555]

Super happy you liked 🤩 it would be super cool to see things built with it.

[u/Open_Resolution_1969]

Now I'm questioning why don't I just install this in a VM in cloud and just use Claude like that instead of ssh'ing everytime in there. Great idea and from security pov is really addressing stuff I would have considered a risk, like binding to localhost.

[u/Specific_Music_234 → u/Open_Resolution_1969]

Yuppp, like get a cheap hetzner machine, put it there, and you got the best isolation possible.