Shared AI sessions
The defining primitive of withvibe. Most AI coding tools give each user their own session; withvibe puts a team into one session and treats the AI as a shared collaborator.
One agent, many humans
An env hosts a single Claude Agent SDK session. Every prompt — from any teammate — flows into the same conversation. The agent sees the whole context: who said what, what it already tried, what worked, what got rolled back.
Turn-taking
Humans don't need to coordinate explicitly. The session uses soft turn-taking:
- While the agent is working, new prompts are queued.
- Each prompt is attributed to the human who sent it; the agent sees the author.
- Anyone can interrupt with Stop; the next prompt becomes the new direction.
Steering vs. driving
Two postures map to two styles of collaboration:
- Driving — sending prompts. Anyone with developer-or-above role can drive.
- Steering — watching, course-correcting, sending small clarifications. Devs typically steer while a stakeholder drives.
Memory
The session keeps three layers of memory:
- Short-term — current chat. Auto-summarized as it grows.
- Env memory — durable notes scoped to this env (decisions, preferences).
- Workspace memory — durable notes scoped to the team (style, conventions).
What this enables
A single shared session is what makes the cross-functional flow real. The PM's clarification two messages ago is part of the agent's context when the dev intervenes five messages later. Nothing has to be re-explained because the artifact and the conversation are shared.