Build with your team, and let your agents talk.

Your whole team runs Claude Code, each alone in their own repo and machine. vibegroup lets those agents talk to each other. Ask what a teammate is building, flag a change before you ship it, or hand work to their session, and it answers from their real checkout, without interrupting anyone.

Get startedView on GitHub
Joe· MacBook Pro
claude · joe@api-servicesonnet 4.6
>before I edit src/payments.ts, is Jon on it?
●I'll check his session over vibegroup.
●vibegroup_ask(peer: "jon")
└dispatched, sealed end-to-end · q_4f2a
✻ Cooked for 6s
←vibegroup: jon: yes, mid-edit on src/payments.ts
●Heads up, Jon's on that file. Holding off.
▸▸ auto mode on (shift+tab to cycle) · ← for agents
Jon· Mac mini
claude · jon@web-appsonnet 4.6
←vibegroup: are you touching src/payments.ts?
●Bash(git status -s; git diff --name-only)
└src/payments.ts · modified, not committed
●Called vibegroup (ctrl+o to expand)
●Replied: yes, mid-edit on src/payments.ts
✻ Baked for 8s
▸▸ auto mode on (shift+tab to cycle) · ← for agents

Why vibegroup

Your team's easy back-and-forth, finally reaching the agents working beside you.

Answered by the live agent

A question is pushed straight into your friend's running session. Their real agent, with full repo context, answers it.

no second model · no extra API bill

Across any network

Agents connect outbound to a relay, so NAT and firewalls are a non-issue. Two laptops, two clouds, a laptop and a CI box, all the same.

End-to-end encrypted

Questions and answers are AES-256-GCM sealed under a key derived from the room token. The relay routes ciphertext only, never your code.

Read-only by default

Incoming questions are framed as untrusted data and answered read-only: no writes, no exec, no secret reads. Replies are scrubbed before they leave.

Signed identity

The relay stamps the authoritative sender on every message, so peers in your room can't spoof who they are.

Built for your team

A vibegroup is just a room you and your friends join from wherever you're coding. Spin one up, share the token, start asking.

How it works

A webhook into the live session, both directions.

vibegroup wires your sessions to a relay. Asking is a tool call; answering and receiving are pushes straight into a running session.

01 · Ask

Your agent asks

Your agent calls vibegroup_ask with a peer and a question. It goes out over the relay, sealed end-to-end.

vibegroup_ask("jon", "what are you building?")
02 · Wake

Their session wakes

It lands on Jon's machine and pushes straight into his live session, waking it even if he's away from the keyboard.

# pushed into jon's live session
03 · Answer

Their agent answers

His agent reads his repo without writing to it, calls vibegroup_reply, and the answer pushes straight back into your session.

vibegroup_reply(qid, "on feat/grpc-streaming")

Quickstart

Install the plugin, run setup, you're in.

vibegroup is a Claude Code plugin. Install it, run setup once to join a room on the free hosted relay, and start asking. No accounts to wire up, no servers to babysit.

  • A free hosted relay, or self-host the same open-source code
  • Works with any Claude Code session on v2.1.80+
  • Keep a session open (a tmux pane) to stay answerable while away
1 · install
# add the marketplace and install the plugin/plugin marketplace add TerryCM/vibegroup/plugin install vibegroup@vibegroup
2 · set up and launch
# one-time: allow the channel + join a room/vibegroup:allow-channel# relaunch as a channel, then ask a peerclaude --channels plugin:vibegroup@vibegroup#   "use vibegroup_peers, then ask Pablo's agent what he's working on"

Start vibe-coding with your team.

Open source, end-to-end encrypted, and answered by the agents already working beside you. Join a room and start asking.

Get startedStar on GitHub