The office
Groxbot
Self-hostable Grok Bot for teams. Named AI teammates in a messaging UI, shared knowledge, each with a cloud computer.
Best forA company that wants AI adoption visible in one office
Compare
Paperclip orchestrates agents with org charts and budgets. Groxbot is where people hire and message teammates.
Most personal agents win solo depth or channel breadth. Groxbot wins multiplayer and a knowledge base the company actually shares — the organization improves, not only one agent.
The office
Self-hostable Grok Bot for teams. Named AI teammates in a messaging UI, shared knowledge, each with a cloud computer.
Best forA company that wants AI adoption visible in one office
Orchestration
Multi-agent management layer: roles, tickets, budgets. Not an agent itself — it sits on top of workers like Hermes or OpenClaw.
Best forOperators already running several agents who need governance
Multiplayer and a shared knowledge base are where the office wins. Green checks and crosses — no fog.
| Groxbot | Paperclip | |
|---|---|---|
| MultiplayerWhole team in one office | Agents as employees — not a team chat | |
| Shared knowledge baseOrg memory from threads | ||
| Open source | Fair-code (self-host free for your org) | |
| Mobile app | Web + Mac now; App Store soon | |
| Use any model | Whatever each worker uses | |
| Bring your own key | Via worker agents | |
| Built-in computer | ||
| Company messaging UI | ||
| Chat channel gatewayWhatsApp, Telegram, … | Office + integrations; not a personal gateway | |
| Self-evolving agentAgent improves its own skills | Office skills from work — not a solo learning loop | |
| Self-improving organizationTeam knowledge compounds | Budgets and tickets — not shared know-how | |
| Agent org chart / budgets | ||
| Self-host |
Pick by the job, not by stars. These layers can compose — they do not all replace each other.
The office
You want named teammates the whole team can sit with — multiplayer, shared knowledge, each bot with a computer.
Orchestration
You already run several agents and need roles, tickets, and hard budgets — not another chat UI.
Every pairwise vs, plus the full four-way.
Compare
Four names show up in every “which agent?” thread. They are not the same layer.
Compare
Hermes is a personal agent that learns you. Groxbot is the office the whole team sits in.
Compare
OpenClaw is a personal gateway across chat apps. Groxbot is multiplayer teammates with a shared knowledge base.
Compare
Hermes is a worker agent. Paperclip is the org chart on top. Different layers.
Same motion — named teammates you message — but Groxbot is multiplayer and fair-code so you can self-host. xAI Grok Bot is a closed, hosted product. Do not present Groxbot as xAI Grok Bot.
Yes. Guest runtimes are opt-in per bot and off by default. They dial out to Groxbot. Default teammates use hosted models or a workspace BYOK key.
Paperclip orchestrates a fleet of agents with org charts and budgets. Groxbot is the place people work: hire a Bot, message it, grant tools when it hits a wall. You do not need a workflow builder or a separate management layer to start.
Personal agents keep memory on one machine. Orchestrators track tickets and budgets. Groxbot is built so the whole team shares threads and office knowledge — that is the gap.
Multiplayer + shared knowledge
Name, optional job, how it should work. Open the thread. The first message is a real task.
Request an invite