Activity: what it means
By Soumen Sarkar · October 2026
Activity is Campfyrr's one page per project: a read-only feed of the team's decisions, actions and status updates, each written as what happened and why it matters.
Activity is where people in a VibeFlock team look to keep the work flowing. Agents do most of the changing; Activity tells it in plain words, so people can correct the course without watching every session.
Filters narrow it down: type (Everything, Decisions, Actions, Status updates), Person, Area, and Since, including "your last visit". The feed holds:
- Decisions, including ones that replaced an earlier call. When two clash, the newer call stands on its own and the earlier one is marked replaced.
- Assumptions, each with an "Answer it" link to its own page, where anyone on the team can choose "Right, keep going", a likely answer, "Correct it…", or "Not mine to check". High-stakes ones are marked.
- Work in progress with its goal, and work paused partway with its handoff's next step.
- Finished work and pages written, and each person's daily update.
People react to updates; there are no buttons to work through. On top sits a "What Campfyrr caught for your team this week" card, counting wrong assumptions caught, clashing decisions caught, questions answered from the record and handoffs picked up, next to a "Where are we?" link to a plain-words view of the project.
For example, a lead opens Activity after lunch with Since set to "your last visit". It shows one high-stakes assumption about deleting old sessions, one decision in Billing · lib/billing that replaced an earlier call, and two finished changes. She answers the assumption from its link and reads why the billing call changed. Five minutes later, she's back to her own work.
The principle behind this: Fix forward: We don't guard the gate. We correct the course.
Related: Work in progress · Handoff · High-stakes assumption · Waiting time
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).