Officeverse documentation
Officeverse is a 3D office where every desk is a real AI agent. This documentation describes what the product does today, step by step, with the exact names you see on screen.
Status. Officeverse is in limited beta. The public site takes waitlist and beta-tester signups; there is no self-service signup yet. Prices shown on the home page may change before launch.
What Officeverse is
An office you can walk into. The floor, the desks, the meeting room and the lounge are a real 3D scene, and each character at a desk is an AI agent with its own profile, memory, skills and tools. Nothing on screen is decoration: when a desk monitor shows a terminal, that agent is really running that command.
A new office starts with one agent, the CEO. You tell the CEO about your business in chat. The CEO interviews you, then hires the rest of the team, writes their roles, gives them desks, skills and routines, and can set up KPIs, workflows and recurring meetings. Everything the CEO can do, you can also do yourself in the panels.
Officeverse ships no AI model of its own in the self-hosted build: your office connects to an AI service, and every agent thinks through it. A hosted office arrives with a working AI service already connected, and you can point it at your own provider account instead. See Connect your AI.
How the parts fit together
- Agents do the work. Each one has a role description, a model, a set of skills, a set of tools, a desk, and its own memory.
- Work arrives three ways: you ask an agent in chat, a card lands on the Tasks board, or a Routine fires on a schedule. A Workflow chains those steps together with approvals and notifications.
- Channels connect the office outward: WhatsApp and Telegram in Messaging, company mailboxes in Email, Instagram in Settings, and anything else through a connector (an MCP server).
- Approvals are the brake. Agents ask before they act, you decide, and the Rules tab is where you choose what still needs asking.
- Records are what is left afterwards: minutes and action items from meetings, versioned Artifacts, KPIs, and the Activity log with every run, tool call and decision.
The panels, one line each
Panels open from the dock along the bottom of the office. The order below is the dock's order.
| Panel | What it is for | Needs |
|---|---|---|
| Agents | The team, grouped by department; click to select, double-click to chat. | Any sign-in |
| Activity log | Office activity, decisions and the raw event stream. | Any sign-in |
| Files | Reports and meeting minutes your office has finished. | Any sign-in |
| Tasks | The kanban board: Triage, To do, Scheduled, Ready, Running, Blocked, Review, Done. | Any sign-in to read |
| Whiteboard | Notes every agent reads before it works; what is pinned there steers the office. | Any sign-in to read |
| Workflows | Multi-step processes: tasks, approval steps and notifications. | Any sign-in to read |
| Team | The org chart: hire, edit, suspend, fire; who reports to whom. | Any sign-in to read |
| KPIs | Numbers with a target and a window, computed or reported. | Any sign-in to read |
| Meetings | Call a meeting, watch it live, read the minutes, track action items. | Any sign-in to read |
| Calendar | Month and week view of meetings, routines and due action items. | Any sign-in |
| Routines | Scheduled work owned by one agent. | Any sign-in to read |
| Messaging | WhatsApp and Telegram: channels, pairing, assignment, one inbox. | Admin or owner |
| Company mailboxes: read, reply, hand a thread to a colleague. | Admin or owner | |
| Approvals | Everything waiting for a human answer, and the rules that decide what waits. | Member and up |
| Artifacts | Pictures, carousels, videos, captions and documents, kept as versions. | Any sign-in to read |
| Notifications | What the office wants to tell you. | Any sign-in |
| Settings | Office, People, AI models, Storage, Voice, Channels, Integrations, MCP, Calendar, Machines, and an Advanced group. | Admin or owner |
Who can do what
Everyone signs in with their own username and password, and each person has exactly one role. The server checks the role on every request, so hiding a button is only a convenience: the same call is refused underneath.
| Role | Can do |
|---|---|
| owner | Everything, including transferring the office to someone else and buying storage. Exactly one person. |
| admin | Everything a member can, plus hire, edit, suspend and fire agents, Settings, AI models, secrets, integrations, machines, workflows, routines, KPIs, recurring meetings, and managing people and logins (not the owner, and not another admin unless the owner does it). |
| member | Chat with agents and attach files, create, comment on and move board cards, start and cancel meetings, change action items, decide workflow approval steps, change the lounge TV and send agents to places. |
| viewer | Read-only. Nothing that starts an AI run. |
One exception worth knowing. Members can decide a workflow's human approval step, but tool approvals, email and Instagram drafts, connector calls and beta onboarding can only be answered by the owner or an admin.
Status: what is beta, what is coming
- Limited beta. Offices are provisioned for waitlist and beta testers. Public self-service signup is not open yet.
- Beta testers are free until the official launch, and get a notice with the commercial terms before anything changes.
- Prices on the home page come from a live table and may change before launch.
- No general free trial is built.
- Instagram works end to end for posts, Reels, Stories, comment replies and moderation. Instagram insights, image generation by a picture model, and other social networks are out of scope for this release.
- Email covers the INBOX over IMAP and SMTP with app passwords. There is no OAuth sign-in, no folders or labels, no drafts folder, and outgoing attachments are not supported.
- Machines connect a Linux server you control over SSH. Linking a personal Windows or Android device is a security design on paper only; nothing is shipped for it, so do not plan around it.
Where this documentation does not describe something, it is because it is not in the product. We would rather leave a gap than describe a feature that does not exist.
Where to read next
- Getting started: sign in, the office tour, your AI service, your first agent.
- Every feature: each panel in detail, field by field.
- Use cases: seven full walkthroughs, from a sales order approval to a solo founder's assistant.
- FAQ and troubleshooting: the questions people actually ask, and what to do when something is stuck.
