Build a room around one useful task
Open a local project, choose a coding provider and queue a request with a clear result. Turn on Office from the terminal header and follow the agent at its desk. Pick something you can inspect in one sitting: a settings improvement, a bug reproduction or a small documentation correction. A room becomes useful when each desk represents work you can recognize and review.
Open the desk to work with its task pane. Office keeps the existing Terminal, Conversations and Highlights choices available, so you can inspect the form of output that helps with the current step. Codex and Claude Code can expose their original CLI through the embedded terminal. OpenCode runs headless. Choose a provider for the task you have, then let the room help you follow it.
Enjoy the overview without losing the details
Use the room to notice an agent working or a result ready for your attention, then open the task to read what happened. A finished task deserves a real review: inspect the result and available patches, and run the checks that establish the intended behavior. The familiar Ready for review state acknowledges a completion waiting for your attention; it does not certify the code.
When the result needs a correction, use supported conversation continuation to keep the follow-up with the task that caused it. Start a fresh task for an unrelated purpose. Office gives those decisions a visible home, while the saved task remains the place to understand the request, its execution and the next turn.
Add desks at the pace you can review
Once one request has gone through execution and review, try another independent task alongside it. A documentation investigation in one repository can pair well with a small fix in another. Two agents changing the same schema usually need sequencing or separately prepared checkouts. The room helps you see parallel work; it does not make overlapping edits independent.
Set provider concurrency to fit your machine, provider allowance and review capacity. A free slot is permission for VibeiDE to schedule a task, not extra provider usage. Leave yourself time to read finished results. The enjoyable version of an agent office is a place where you know what each desk owns and what you will check when it is done.
Join a team with a clear sharing choice
Your personal Office is your own workspace. On a Team account, Company adds a separate manager view of sharing members’ rooms. Shared task data is limited to allowlisted identifiers, provider labels, states and timings. Your original task titles, prompts, source code, file paths, transcripts and results are excluded. Managers see generated task labels rather than the material you are working on.
Room sharing starts enabled, and you can turn it off in Team settings. A manager can see that sharing is off, but your room and shared task counts are unavailable. Company keeps only a rolling seven days of shared task data. This is the Company sharing boundary; the coding provider you use still receives the context needed for your local task. You can explain the choice without guessing what a room contains.
Ask for another pair of eyes when you need one
When a completed task needs a manager’s attention, choose Send to manager for review. Company shows the handoff in orange as Manager review, separate from the ordinary ready and working states. You decide which completed task deserves that explicit signal. It can start a conversation about a tricky behavior, a tradeoff or evidence you would like someone else to inspect.
The manager can inspect and acknowledge the shared metadata. The actual code review still uses your normal development workflow, and that acknowledgement does not alter your local review state. If you become a manager yourself, you keep coding in your own Office. Company uses the company name at the top. Managers can view members’ shared rooms, but do not get Company rooms of their own. Every role uses the same $14.99 USD monthly Team seat, with provider costs separate. Your builder’s workflow can grow with your responsibilities.
Explore A company view for founders who still love building, Engineering managers: give finished agent work a clear next step, How many AI coding agents should you run in parallel?.