A Hermes agent office is now a real thing you can run: it's called Hermes 3D — a live 3D office on your own machine where your agents sit at desks, work, and hand tasks to each other in real time, with a built-in Kanban board and standups you can walk into. It is an open-source community project (MIT licence, version 1.0 shipped on 20 August), it runs on top of your existing Hermes setup rather than replacing it, and it fixes the biggest weakness of bot rosters: you finally see what your team is actually doing.
📺 Watch: Hermes3D Is INSANE: AI Agents Now Have a 3D Office
🔥 Get the Agent OS as a free bonus: AI Profit Boardroom members get the full Agent OS zip, prompt libraries, daily tutorials and weekly live coaching calls. → Get inside
Here's the context. Bot mode changed how people run Hermes. Instead of one assistant, you get a roster of named bots — each with its own role, model, memory, skills and avatar. They message each other, hand work over with at-mentions, share group rooms and run recurring routines. It's a real team. But a team you can't see is just ten invisible processes in terminal tabs. You don't know who's working, who's blocked, or who handed what to whom. You're managing a company through a letterbox.
Hermes 3D opens the door.
What Is Hermes 3D? The Hermes Agent Office, Explained
Hermes 3D is a 3D office for your agents that runs on your own machine. You walk through a live office where agents sit at desks and work. You see at a glance who's busy and who's blocked. You can inspect tasks, open the Kanban board, walk up to an agent and talk to it, and watch task handoffs happen in real time.
One quick disambiguation: this is not the Hermes pixel office I've written about before. That was a different, earlier office-style project. Same instinct — make the invisible visible — but Hermes 3D is a separate build, and a much bigger swing.
From Claw 3D to Hermes 3D: The Developer Story
The developer behind Hermes 3D goes by Luke the dev, and the backstory matters. He built Claw 3D first, on top of OpenClaw, and it went viral — the same community energy that gave us the Hermes paperclip agent. Then he moved his own workflows over to Hermes, so he rebuilt the idea properly. His words, not mine: Claw 3D was the prototype, Hermes 3D is the real vision.
Hermes 3D version 1.0 went public on 20 August. When I recorded my video on it, the repo had already passed 100 stars with around 20 forks — quick traction for a project this young. It's open source under an MIT licence, so you can read every line before you run any of it.
What You Can Do Inside the Office
The repo's own feature list reads like a job description for a very unusual office manager. Inside, you can:
- Watch agents work in real time in a shared 3D office
- Run standups with agents connected to GitHub and Jira
- Review pull requests from inside the office
- Monitor QA pipelines and logs without leaving the workspace
- Train agents in the gym to develop new skills
- Reset sessions and clean context with the janitor system
Read that twice. Standups with agents wired into GitHub and Jira. Pull request reviews from inside the office. A gym for new skills and a janitor for context hygiene. This isn't a screensaver with extra steps — it's a working management layer wearing a 3D costume.
Want an agent team worth watching? Inside the AI Profit Boardroom I share the exact agent setups, prompts and systems I use every day — join us here.
What Hermes 3D Is — and What It Isn't
This is the part most coverage skips, so let's keep it intact. Hermes 3D is the visualisation and interaction layer. It does not install the agent runtime for you. The repo says it plainly: the gateway is just the control plane, and the office is the product. Your agents live in the backend; the office is where you meet them.
It's also unofficial — an independent community project, not made by the teams behind the backends it connects to. That's straight from the readme, and I'd call it a good sign: projects that state their own boundaries this clearly tend to be the ones you can trust. If you just want a simple chat window rather than a walkable office, I've ranked the best Hermes web UIs separately.
What It Runs On
Hermes 3D runs on top of three backends:
- Hermes, through the bundled gateway adapter — the main event
- A direct HTTP custom runtime, for wiring in your own orchestrator stack
- A built-in demo gateway with mock agents, so you can explore without touching a real backend
📺 Watch: Hermes AI Agents Just Went Portable
What Version 1.0 Shipped
The 1.0 release wasn't a version bump — it was a proper overhaul:
- A full visual overhaul — cinematic renderer, PBR materials and a campus exterior
- A single Hermes floor plus a Hermes agent taskboard
- Perimeter walls raised to full height — a small change that completely changes how the space feels
- Direct connection to a Hermes backend with no adapter process at all — including over Tailscale, which slots straight into the Tailscale AI gateway setup I've covered before
- Conversation circles — chatting agents visually huddle together, and the chatter sounds like a real conversation
- An office bridge plugin — the office reacts to conversations you have elsewhere, so your desktop app or terminal chats reflect in the office
- A built-in Kanban board — no separate skill needed any more
Six Beginner Tips Before You Install
These are the six things I'd tell anyone trying Hermes 3D for the first time. Number five is the one most people skip — don't.
1. Start in demo mode
Do not wire up a real backend on day one. Run the demo gateway, start the app, connect, and you've got a mock office with demo agents and streaming chat. Learn the space with fake colleagues before you introduce your real ones.
2. Check the basics
You need Node 20 or newer and npm 10 or newer. Half of all setup problems come down to an old Node version, so check this before you blame the project.
3. Understand the two hops
Your browser talks to Studio, and Studio talks to the gateway. So when a setting refers to the local gateway address, that means reachable from the machine running Studio — not from whatever device you're browsing on. Keep those hops straight and most networking confusion disappears.
4. Know the two gateway settings
The gateway address lives in two places. One is a build-time variable — changing it does nothing until you rebuild. The runtime version takes effect on a server restart. If you edit a setting and nothing changes, that's usually why.
5. The security step most people skip
If you expose the app beyond your own machine, set the Studio access token. In production, set the upstream allow list too, so Studio can only proxy to gateway hosts you approve. There's a second allow list for the custom runtime route, and it falls back to the first if you leave it unset. This is your AI team's front door — lock it.
6. Learn to read the connection errors
Two errors cover most failed connections. A protocol version error means the gateway is too old — update it, or run the bundled adapter. A wrong version number error means a secure address was used against a non-secure endpoint.
📺 Watch: Grok Bot DESTROYS Hermes Agent?
The Honest Limitations
The Hermes 3D repo lists its own limitations openly, which I respect more than any feature:
- Voice transcription isn't bundled
- The immersive office and the builder are separate stacks
- The connection flow loads gateway details into browser memory — so treat your browser as part of the trust boundary
None are dealbreakers — but you'd rather know them on day one than discover them on day thirty.
The Real Takeaway: Visibility Is the Missing Layer
We've collectively spent two years making agents more capable, and almost nobody has worked on making them understandable. That's the gap this fills. Watching a task hand from one agent to another tells you more in three seconds than scrolling a terminal for three minutes.
It's the same philosophy behind Agent OS: your agent stack needs mission control — one place where you can see the whole operation at a glance. I made the flat-dashboard version of this argument in my Hermes agent command centre piece. Hermes 3D takes the same idea and turns it into a place you can walk around in.
Hermes 3D Quick Facts
Hermes 3D at a glance:
| What | Status |
|---|---|
| Licence | Open source, MIT |
| Version | 1.0 — public since 20 August |
| Developer | Luke the dev (Claw 3D was his prototype) |
| Backends | Hermes (bundled gateway adapter or direct connection), direct HTTP custom runtime, built-in demo gateway with mock agents |
| Requirements | Your own machine, Node 20+, npm 10+ |
| Traction | 100+ stars and around 20 forks at recording |
| Official? | No — independent community project |
Hermes Agent Office FAQ
What is Hermes 3D?
It's a Hermes agent office — a live 3D workspace, run on your own machine, where your agents sit at desks, work on tasks and hand work to each other while you watch, inspect and chat with them in real time.
Is Hermes 3D official?
No. It's an independent community project, open source under MIT, and not made by the teams behind the backends it connects to. The readme states this openly, which is exactly what you want to see.
Do I need bot mode set up first?
Not to try it — the built-in demo gateway ships mock agents, so you can explore immediately. But the office earns its keep once there's a real team to watch, and a bot mode roster of named agents with roles, memory and routines is precisely that.
Is it safe to expose beyond my own machine?
Only if you lock the front door first. Set the Studio access token, set the upstream allow list in production so it can only proxy to approved gateway hosts, and remember the custom runtime route has its own allow list that falls back to the first. Skip those steps and your agent team's front door is standing open.
What do I need to run it?
Your own machine with Node 20 or newer and npm 10 or newer. Remember the two hops — browser to Studio, Studio to gateway — Version 1.0 also connects directly to a Hermes backend, including over Tailscale for remote access.
My Verdict
I put a lot of agent tooling through Goldie Bench, my own testing setup, and the pattern is consistent: the winners aren't the tools that make agents smarter — they're the ones that make agents easier to trust. Hermes 3D sits squarely in that camp. It's young, it's unofficial, and the limitations are real. But as a Hermes agent office — a place where your team stops being background processes and starts being visible — it's the most convincing attempt I've seen yet. Start in demo mode this week, lock the front door before you expose anything, and go watch your agents actually work.
Ready to put a real team in that office? Join me inside the AI Profit Boardroom, where we build agent systems that actually make money — get access here.
