VibeFlock: what it means
By Soumen Sarkar · October 2026
VibeFlock is building one product with a team of people and AI agents at agent pace, where context travels with the work so nobody waits.
VibeFlock is a way of working, not a tool and not a process. The name comes from how a flock of birds or a school of fish moves: thousands turn as one, with no leader, because each one reads its neighbours and moves with them. It describes a team where each person directs several AI agents, such as Claude Code, Codex or Cursor, and dozens of changes a day land in one codebase. At that pace, context can't travel through conversation. It has to travel with the work itself.
Seven principles hold it together: keep moving, build on what's coming, fix forward, turn unknowns into calls, answer it yourself, let the work speak, and decide by doing. Each one removes a reason for work to stop. You can read them in full at /vibeflock.
In practice it looks like this:
- An agent about to change Billing · lib/billing first learns what is being changed there right now and what was decided.
- When it hits an unknown, it states an assumption and keeps going.
- When it stops, it leaves a handoff for whoever continues.
- Every change carries its reasons to its reviewer.
Take a hypothetical four-person team running twelve agents. Nobody holds a sync meeting before lunch, yet every agent knows that the checkout is being split into steps, that money is stored in cents, and that the coupon work is half done with a written plan. Campfyrr is the product built to make this happen automatically.
The principle behind this: Keep moving: The work never waits, and neither do we.
Related: Area brief · Work in progress · Handoff · Assumption
Questions that use it
Move as one at agent speed. Nobody waits. Add Campfyrr to Claude: it briefs every agent before it touches the code, keeps assumptions and handoffs where the team can see them, and never takes your code (what it keeps).