Start the day with a walk through the team
Picture a product team preparing its next release. One developer has an agent working through a fix. Another has finished a task and asked for a manager’s review. Someone else has work waiting to run. Open Company mode and those different moments have a place: each sharing member has a room, with agent desks showing recent task states. Open a room and move between people to find the next useful conversation.
The company name becomes the mode’s label, with Company as the default. Floors keep a growing team navigable, starting with ten people per floor. This gives your morning check a clear shape. See the current work, notice a review request, then decide where your attention can help. You still need the person’s context to understand the change itself.
Give review a visible place in the day
An agent finishing a task is a good moment. A teammate explicitly asking for your review is a different moment. Members can choose Send to manager for review on a completed task. Company gives that request an orange Manager review state, visibly distinct from ordinary ready and working states. A developer can signal a handoff without relying on you to spot a completion count.
Set aside a short review window after your company check. Open the requested task’s metadata, speak with the teammate when context is needed, and inspect the actual patch and checks through your usual development process. Mark metadata seen acknowledges the shared record. It does not approve the code or deploy a release. That leaves the handoff clear and the engineering decision in the right place.
Use the week to ask better questions
Finished today puts a clickable completion count beside each member. Weekly review lets you open a day and inspect the recorded completions for that date. The shared view retains a rolling seven days of data, with days grouped in UTC. It is a compact window into recent execution, useful for preparing a team conversation while the work is still fresh.
Treat these as completed execution attempts, not features shipped or a ranking of people. A small copy change and a difficult migration can each produce one completion. A follow-up can produce another attempt. If the week shows finished work collecting around a review request, ask what decision or evidence is still needed. The interesting outcome is a better next step, not a larger number.
Make the sharing boundary easy to explain
Company shares an allowlisted set of task identifiers, provider labels, states and timings. Task titles, prompts, code, file paths, transcripts and results are excluded from that shared task feed. Rooms use generated task labels. You get a view of the workflow without copying the member’s working material into a central company task archive.
Room sharing starts enabled, and members can turn it off. Managers can see who has sharing enabled and who has opted out; a private member has no shared room or task counts. Explain that choice when people join. This boundary applies to Company sharing. Coding providers still receive the context their local CLI needs to carry out a task.
Keep your builder’s seat
A manager account can code. Switch back to your personal Office and work with your own agents at their desks, then return to the company view for the next handoff. Owners and managers are excluded from Company rooms, including when the team has several managers. The shared floor stays focused on member rooms while your own coding workspace remains available.
The Team plan is $14.99 USD per seat per month, including owner and manager seats. Choose the seat count for the people who need access. An owner, one additional manager and six members use eight seats, or $119.92 per month before tax. Provider subscriptions remain separate, and an existing personal VibeiDE subscription continues until you cancel it in billing. Start with a team size you can support and a review routine you will actually use.
Explore Engineering managers: give finished agent work a clear next step, Your AI coding agents deserve an office, Move from an AI coding idea to a reviewed implementation.