Last weekend I did something stupidly fun.
I sat down at the Mac Mini and gave my whole family their own OpenClaw.
Wife. Each of the kids. All of us, each with our own private AI agent running on the same little machine in the corner.
One of the kids is already glued to it. Asking it questions they would never ask me, never ask their teacher, never ask their mum. Some of it is "how do volcanoes work." Some of it is the kind of thing you only ever ask your trusted advisor when nobody else is in the room.
Watching that happen was the moment I realised something.
A Mac Mini running OpenClaw is not a gadget.
It is a private AI server.
And most people who own one are using maybe ten percent of what it can do.
The Mistake Most People Make
You buy the Mac Mini.
You install OpenClaw.
You set it up. You wire in your messaging app. You give it a couple of skills. It works. You think "this is great."
And then it just sits there.
One assistant. One memory. One job. One human using it.
Meanwhile the machine has plenty of headroom, your family could each have their own, your team could each have their own, and you could be running specialist agents for entire parts of your business.
The hardware is not the limit.
The thinking is.
What Multiple OpenClaws Actually Unlocks
OpenClaw supports running multiple isolated instances on the same machine. Each one gets its own:
- Configuration
- State and memory
- Workspace
- Gateway port
- Messaging channels
- Skills and plugins
- Tool permissions
That sounds dry until you put it into real life.
It means I can have:
- My own agent as the command centre. Strategy, research, content, reminders, the lot.
- My wife's agent with its own memory and tools, set up for what she actually needs.
- The kids' agents — locked down, kid-friendly, no shell access, no random tools, just a friendly assistant that helps them stay organised, remember things, and ask questions.
- Business agents for very specific roles. A meeting manager. An HR assistant. An ops agent that lives in the SOP channel.
Same Mac Mini.
Different brains.
Why Specialist Agents Beat One Giant Assistant
The default instinct is to keep stacking responsibilities onto one assistant.
Reminders. Calendar. Email. Research. HR questions. Meeting notes. Project follow-ups. Internal knowledge. Customer questions.
It feels efficient at first. It is not.
You would never hire one human and ask them to be the EA, HR manager, meeting coordinator, software engineer, ops lead, payroll contact, culture champion, and head of strategy. You would create roles.
AI deserves the same treatment.
A focused agent with a narrow role, clear instructions, controlled access, and persistent memory beats a giant assistant trying to remember everything for everyone.
That is the shift.
From "I have an AI assistant" to "I run a small team of governed agents."
The Family Version
Before I get to the business setup, let me say something about the family one.
Giving my kids their own OpenClaw was supposed to be a weekend nerd project. It turned into something else.
They are learning what I would call results-based computing. They do not care about the model. They do not care about the port. They tell their agent what they want, and the agent figures out how to help.
They are remembering things they would otherwise forget.
They are getting organised in a way no app ever achieved.
They are asking real questions to a "trusted advisor" that has time, patience, and no judgment. Some questions they would never ask me. Some they would never ask their teacher. The agent just answers, kindly, and they move on with their day.
For the kids, the agents are locked down hard. No shell. No browser automation. No file system access. Limited skills. Allowlist on who can message them. Their agent's job is to be helpful, safe, and theirs.
That is the whole point of running OpenClaw the way I am about to describe. You stay in control. You decide what each agent can do, what tools it has, what plugins are enabled, what channels it lives in, and who can talk to it.
That is not theoretical. It is configurable, and the rest of this post shows how.
The Business Version
Now apply the same idea to your company.
Imagine your management team each has their own OpenClaw. Or imagine specialist agents that sit inside the relevant work channels.
A sensible setup might be:
- Owner agent. Strategy, research, market scanning, inbox triage, content, reminders, decision support.
- HR agent. Onboarding, policies, role descriptions, staff FAQs, internal HR documents.
- Meetings agent. Agendas, summaries, action items, follow-ups, calendar prep.
- Ops agent. SOPs, process documentation, workflow questions, internal knowledge.
- Culture agent. Internal comms, values, rituals, morale signals, onboarding experience.
Put each one in the channel where the work already happens. The HR agent in the HR channel. The meetings agent in the leadership meeting channel. The ops agent in the SOP and process channels.
The channel becomes the interface.
People do not need to understand the architecture. They just notice that the right agent answers in the right place.
That is when AI stops feeling like an app and starts feeling like an operating layer for the business.
You Stay In Control
This is the part most people skip and shouldn't.
OpenClaw is powerful. It can use file access, browser automation, scheduled tasks, skills, plugins, and external integrations.
That is exactly why you want to be deliberate about what each agent gets.
OpenClaw lets you:
- Enable or disable specific plugins per agent.
- Allow or deny capabilities at the config level.
- Enable or disable individual skills.
- Restrict who can DM the agent in each channel.
- Sandbox agent tool execution.
- Keep gateways local-only or behind a private network like Tailscale.
So the kids' agents lose shell access entirely. The HR agent doesn't need browser automation. The meetings agent doesn't need access to payroll. The ops agent gets internal docs but not random external tools.
Each agent gets exactly the tools it needs to do its job. Nothing more.
That is the difference between a toy and a properly governed system.
How To Change The Port (The Practical Bit)
Each OpenClaw instance needs its own gateway port.
Why? Because the gateway runs an HTTP server, plus a browser control service on port + 2, plus a CDP range from port + 9 to port + 108. If two instances share the same base port, they collide.
The official guidance is to leave at least 20 ports between base ports. I leave 1000 between mine, just to be safe and easy to remember.
My layout looks like this:
main 18789
hr 19789
meetings 20789
ops 21789
culture 22789
There are three ways to set the port for an instance:
1. During onboarding (recommended).
When you run openclaw --profile <name> onboard, it asks for the gateway port. Enter the port for that profile.
2. As a flag when installing the gateway.
openclaw --profile hr gateway install --port 19789
3. Via environment variable when running directly.
OPENCLAW_GATEWAY_PORT=19789 openclaw --profile hr gateway
If you ever want to change a port later, the cleanest path is:
openclaw --profile hr gateway uninstall
openclaw --profile hr gateway install --port 22789
That re-registers the background service on the new port.
Quick sanity check on your active gateways:
openclaw --profile main gateway status --deep
openclaw --profile hr gateway status --deep
openclaw --profile ops gateway probe
The probe will warn you about other reachable gateways, which is what you want when you are intentionally running more than one.
Full Setup Guide
The rest is the detailed walkthrough. If you just wanted the concept, you can stop reading here. If you want to actually build this, expand the sections below.
A Sensible First Build
If I were doing this from scratch in a business, I would not start with ten agents.
I would start with three.
First, the owner agent. Your command centre. Briefings, research, reminders, content support, market scanning, decision prep.
Second, the meetings agent. Meetings are one of the easiest places to create immediate leverage because the pain is obvious — agendas, notes, decisions, action items, follow-ups, context retrieval.
Third, the ops agent. Every business has a pile of repeated internal questions and process ambiguity. An ops agent connected to SOPs and internal docs absorbs a surprising amount of that load.
Once those three are genuinely useful, add HR, culture, or whatever role your business needs next.
Don't scale the agent count before the first agents are properly working. More agents is not the point. Better operational coverage is the point.
The Bigger Idea
The Mac Mini is not the magic.
OpenClaw is not the magic either.
The magic is the operating model.
Most businesses still treat AI as something a person opens when they need help. A better model is AI that already lives in the work, with specific responsibilities, memory, permissions, and channels.
Not one giant assistant.
A small team of governed agents.
The first version will feel simple. A meeting summary here. A policy answer there. A reminder before something slips. A kid asking a question they'd never have asked anyone else.
Then it compounds.
The agents remember. The channels get cleaner. The repeated questions drop. The meetings get sharper. The kids get more organised. The owner gets fewer low-value interruptions. The business — and the household — start to feel like they have a nervous system instead of a pile of disconnected chats and tabs.
That is what one overpowered little Mac Mini can become.
Not a toy. Not a hobby project.
A private AI operating layer for everything that matters.