Speaker A
Well, sitting on my desk is a new Mac Mini that I set up just for the purpose of running my team of AI agents.
Brian Casel shares his experience setting up a multi-agent AI team using OpenClaw on a dedicated Mac Mini to boost his business productivity.
Ask about this video. Answers come from its transcript only — with the timestamp, so you can check them.
Generated from the transcript and can be wrong — check the timestamp.
Key Takeaways
- Autonomous AI agents can effectively fill specialized team roles to increase productivity.
- Running AI agents on dedicated hardware improves security and operational stability.
- Careful management of access permissions and data sharing is crucial for AI team security.
- API usage costs can escalate quickly; understanding subscription terms and usage policies is important.
- OpenClaw represents a new paradigm in AI collaboration, moving beyond single-session interactions to persistent autonomous workflows.
What the video covers
- Brian Casel sets up a dedicated Mac Mini to run a team of AI agents using OpenClaw, each with distinct roles like developer and marketer.
- He manages these agents via Slack, interacting with them like real team members but powered by large language models.
- Brian discusses technical and strategic challenges including hardware choice, cost management, chat tools, and security.
- OpenClaw differs from other AI tools by maintaining persistent workspaces and running autonomous agents continuously.
- He emphasizes the importance of isolating the AI environment for security, using dedicated email, GitHub accounts, and Dropbox folders.
- Brian shares his cost concerns with API token usage and the ambiguity around using subscription plans like Claude Max for agent operations.
- He highlights the potential of autonomous AI agents to fill team roles and scale business operations without traditional overhead.
- Brian positions OpenClaw as a first-generation tool in a growing paradigm of autonomous AI teammates.
- He offers insights on managing access permissions and syncing files securely between his main machine and the AI workspace.
- Brian invites viewers to follow his AI adoption journey and join his community for further training and updates.
Full Transcript — Download SRT & Markdown
Speaker A
Using Openclaw.
Speaker A
I've got a developer, a marketer, a project manager, a system admin.
Speaker A
They each have their own personality, they've got a queue of tasks tracked in this custom dashboard that I built.
Speaker A
And I'm chatting with them in Slack, just like I would with my real team members, except they're agents powered by Openclaw and various large language models.
Speaker A
What a time this is.
Speaker A
But, you know, getting this up and running was not a plug-and-play situation over the past week and many late nights, I had to figure out my answers to question after question, some technical, some strategic.
Speaker A
Like, should I order a new Mac Mini or can I run Openclaw on a VPS?
Speaker A
And what's this going to cost me in API tokens and could I use my Claude Max plan?
Speaker A
And what chat tool is best for my agents, Telegram or WhatsApp or Slack?
Speaker A
Should I have it power one agent or can I set up a team of agents?
Speaker A
And am I going to need a custom dashboard for managing them?
Speaker A
And let's not forget about security, what should my agents be able to access and how should I think about safeguards?
Speaker A
And most importantly, what's my use case here?
Speaker A
What will I have my team of agents actually do for me?
Speaker A
So, today I'll share where I've landed on all of those questions and I'll show you my setup for all of it.
Speaker A
You know, to be honest, I didn't see the appeal of Openclaw at first.
Speaker A
Back when it was called Claude Bot and then Multibot and it was buzzing around Twitter a couple weeks ago.
Speaker A
Everyone was talking about having their agent respond to their emails for them or book flights or order takeout.
Speaker A
And I don't want or need an AI agent in my personal life and I don't even want it to manage my calendar.
Speaker A
But then I started thinking about a real challenge that I've been having in my business and how setting up Openclaw could help me solve it.
Speaker A
You know, I run this YouTube channel and Builder Methods Pro and my courses and a weekly newsletter.
Speaker A
And thanks to things like Claude Code, of course, building things has never been easier.
Speaker A
But building is only half of what I do.
Speaker A
I develop training content, I manage a publishing pipeline.
Speaker A
And I oversee my membership business.
Speaker A
But lately, I've been bottlenecked, there's so much more that I want to create and deliver if only I had the bandwidth.
Speaker A
In my past businesses, I solved this by hiring real teams and building processes to help us scale.
Speaker A
And that worked, but the overhead was real too.
Speaker A
So, when I gave Openclaw another look, I asked a different question.
Speaker A
Not, do I want a personal assistant, but what if this could fill roles on my team?
Speaker A
And now I'm convinced that this paradigm, autonomous agents with defined roles running on their own machines, I think this is here to stay.
Speaker A
Now, Openclaw is just the first generation of what I think will be much bigger.
Speaker A
So, I want to be figuring this out now.
Speaker A
And maybe this video can help you get started too.
Speaker A
If you're new here, I'm Brian Casel.
Speaker A
I help builders stay ahead of the curve with AI.
Speaker A
And every Friday, I send my Builder Briefing, that's a free five-minute read where I give you my no-hype take on making this transition to adopting AI.
Speaker A
You can get yours by going to buildermethods.com.
Speaker A
And if you're serious about leveling up, check out Builder Methods Pro where you can join our community and get training for builders.
Speaker A
All right, so what actually is Openclaw?
Speaker A
It used to be called Claude Bot and then Multibot.
Speaker A
And how is this actually different from how you might use Claude Code or any other agent?
Speaker A
The core of Openclaw is what's called the Gateway.
Speaker A
That's a process running on a machine, which shouldn't be your personal machine, but we'll talk about security in a moment.
Speaker A
The Openclaw Gateway can run tools, it can use a browser, it can execute bash scripts.
Speaker A
Of course, Claude Code can do a lot of that too.
Speaker A
But what makes Openclaw different is that it's always on.
Speaker A
It maintains a persistent workspace with memory and session logs.
Speaker A
So, you can chat with your agents through Telegram or Slack and delegate tasks that they can do on their own in the background.
Speaker A
So that's a fundamentally different paradigm from you personally managing Claude Code sessions in your terminal.
Speaker A
Openclaw is closer to having teammates who do their work on their own workstations.
Speaker A
The first question is, where should this thing run?
Speaker A
Now, I don't recommend you run Openclaw on your daily driver machine.
Speaker A
You don't want to give it unfettered access to your files and your accounts.
Speaker A
And even if you isolate it with something like Docker, your machine would need to be on and awake 24/7 for your agents to work.
Speaker A
So, Openclaw needs its own dedicated machine.
Speaker A
That could be a cloud VPS starting at around five bucks a month.
Speaker A
Or it could be a physical machine.
Speaker A
Doesn't have to be a Mac Mini.
Speaker A
Any kind of computer on your network.
Speaker A
Both are valid and a lot of people are doing well with the VPS setups.
Speaker A
But I went ahead and I spent the 600 bucks on a new Mac Mini M4.
Speaker A
And call me old school, but I like to be able to screen share into it.
Speaker A
See the desktop, install things and manage it visually.
Speaker A
And I SSH in too when I just need to run a quick command.
Speaker A
And if I end up using my agent team for all the use cases that I have in mind, I'll need more storage and bandwidth than the cheap VPS tiers offer.
Speaker A
So, the cost would start to balance out anyway.
Speaker A
And hey, if none of this works out, I'll throw that Mac Mini up in my home music studio.
Speaker A
I'll use it up there.
Speaker A
So, I've got the dedicated machine.
Speaker A
But that's just the first layer, I need to think carefully about what my agents can and can't access.
Speaker A
Now, this is where the hiring metaphor really kicked in.
Speaker A
If I'm bringing someone onto my team, I wouldn't give them access to my personal laptop or let them loose on a browser where I'm logged into everything.
Speaker A
No, an employee would get their own machine, their own email, access to the files and services that they need with the right permissions.
Speaker A
Nothing more.
Speaker A
So, that's what I did, I set up a dedicated email address for my agents, I created a GitHub username that I can invite to specific repos.
Speaker A
I can grant and revoke access to services just like I would with any other team member.
Speaker A
Now, files were a bit trickier.
Speaker A
I want easy two-way syncing between my computer and the Openclaw workspace on the Mac Mini.
Speaker A
Especially since I'm developing a brain system where all my business activity gets logged into markdown files that my agents can access and work with.
Speaker A
More on the brain, maybe another time.
Speaker A
So, all my files live either in GitHub repos or my main Dropbox account.
Speaker A
But I don't want to just share my personal Dropbox with Openclaw.
Speaker A
That gives it access to way too much.
Speaker A
So, I had Openclaw set up its own Dropbox account and so the specific folders that I want to share between my main Mac and the Openclaw Mac Mini, both Dropbox accounts have access to those.
Speaker A
And so everything else stays walled off.
Speaker A
All right, let's talk about costs.
Speaker A
Because if you're not careful, you can easily run up hundreds or even thousands of dollars in token costs just chatting with your agents and running tasks.
Speaker A
I blew past $200 in the first two days of setting up my system.
Speaker A
Now, I already pay for a Claude Max plan.
Speaker A
And I was hoping that I could just use that.
Speaker A
But then I heard the stories of accounts being shut down because this type of usage might be against Anthropic's terms of service.
Speaker A
And then within a few days he upgraded to the $200 subscription.
Speaker A
Oh, euros, because he's in Australia.
Speaker A
And he was in love with that thing.
Speaker A
That for me was like a very early product validation.
Speaker A
It's like, I built something that captures people.
Speaker A
And then a few days later Anthropic blocked him because they said their rules using the subscription is problematic or whatever.
Speaker A
So there's real ambiguity there and I genuinely wish that there would be some official word one way or the other.
Speaker A
Now, I intend to play by the rules.
Speaker A
So here's where I landed.
Speaker A
My Claude Max plan stays for my personal use with Claude and Claude Code on my devices when I'm working.
Speaker A
My Openclaw agents use API tokens, completely separate.
Speaker A
I'm running those tokens through Open Router, which centralizes all my API usage and makes it easy to select from hundreds of models and providers.
Speaker A
More importantly, it lets me carefully optimize which agents use which models for which tasks.
Speaker A
You know, honestly, that optimization is probably where I spent the most time this past week.
Speaker A
Just figuring out which tasks need the power of Opus and which can run on cheaper, faster models.
Speaker A
Still, running this team of agents is not cheap.
Speaker A
And if you've been building with the frontier models, then you already know this isn't a free ride.
Speaker A
And from a business standpoint, if you compare the token costs to the cost of hiring multiple team members to do the work that can, maybe should be delegated to agents.
Speaker A
The ROI math gets pretty compelling.
Speaker A
Now, to the question of chatting with my agents.
Speaker A
Openclaw supports a wide range of chat tools.
Speaker A
I started with Telegram since that was the easiest to get up and running.
Speaker A
It worked for a few days and I was even able to set up separate Telegram bots for each agent.
Speaker A
I'll talk about my multi-agent configuration in just a minute.
Speaker A
But after a few days on Telegram, I found the interface just wasn't comfortable, especially when agents would send me markdown formatted content.
Speaker A
Which kind of works, kind of doesn't.
Speaker A
So, again, I'm working with my agents like I tend to work with teammates and my teams have always used Slack.
Speaker A
So, I set up Slack bots for each of my agents and that was super easy.
Speaker A
And Slack has great markdown support and I really like how we can use threaded replies and that makes it easy to manage multiple agents with multiple requests and responses flying around.
Speaker A
Now, here's what made Openclaw really click for me.
Speaker A
Instead of using it as a single agent, I set up a multi-agent configuration so that I can build an actual team of four agents.
Speaker A
Claw is my system admin, who I work with when I'm tinkering with my Openclaw system itself.
Speaker A
Bernard is my developer.
Speaker A
Vale works on marketing tasks.
Speaker A
And Gumbo is my general assistant.
Speaker A
Each agent runs as its own Slackbot with its own conversations.
Speaker A
And I experimented with having them all in a group chat, which kind of works, but has some quirks.
Speaker A
So, I assigned a default model to each agent, Opus for Bernard, the developer and Claw, the system admin.
Speaker A
That's where reasoning power really matters.
Speaker A
And then Sonnet for Vale, the marketer and Gumbo, the assistant.
Speaker A
That's where speed and efficiency make more sense.
Speaker A
But I often direct them to delegate parts of their work to sub-agents for tasks where I need to specify a more expensive model or a cheaper model.
Speaker A
Now, I decided to have them all share one workspace.
Speaker A
Which means they all access the same memory and I can manage configurations and agents MD directives all in one place.
Speaker A
Also, my brain folder lives in this workspace and that's where all of our work gets synced up.
Speaker A
And if you want to hear more about my productivity system with my agents, let me know in the comments and I'll make another video all about that.
Speaker A
Now, Openclaw has an identity.md file and that's typically used to define a single agent's identity.
Speaker A
But I use it to define multiple identities, one for each agent on my team.
Speaker A
I even used Claude and Gemini to develop unique personality traits and a visual avatar for each agent.
Speaker A
I wanted to have fun with it.
Speaker A
You know, my bots are characters inspired by one of my favorite bands, Gorillas.
Speaker A
Now, I did run into some challenges with Openclaw's built-in cron system for scheduled tasks.
Speaker A
It was hard to associate those tasks with specific agents on my team.
Speaker A
And so that ended up being one of the main reasons I built my own custom dashboard and task dispatching system.
Speaker A
So, naturally, I built one.
Speaker A
Any excuse to build something, right?
Speaker A
I used Claude Code and my Design OS process and I had a working app in about a day.
Speaker A
It's a simple Rails app that connects to Openclaw's Gateway.
Speaker A
And gives me a clean interface for managing everything.
Speaker A
Honestly, that HQ dashboard was just the beginning, now I'm building another app for editing and reading markdown files in my brain system.
Speaker A
So that I can easily manage what my agents have access to.
Speaker A
This is what I love about this moment for builders.
Speaker A
When a tool that I need doesn't exist yet, I just build it.
Speaker A
In a day.
Speaker A
Now, the most important question and the one that I keep hearing everywhere is, what are you actually going to use your agents for?
Speaker A
So, I've identified a few specific areas where my agents can fill real gaps in my business.
Speaker A
Let's start with the content that I publish.
Speaker A
Now, I only put things out when I have something to say.
Speaker A
And that'll never change.
Speaker A
But the truth is, so much happens inside my projects and in my conversations with other builders that never makes it to a video or a social post.
Speaker A
So, I'm building systems now that let my agents observe and capture more of that work and help me share more of it across my platforms.
Speaker A
Second is development.
Speaker A
Now, I still love to spend most of my time in Claude Code and Cursor, designing and architecting products.
Speaker A
That's not going to change.
Speaker A
But I'm having Bernard, my developer agent, pick up backlog issues and track production errors and submit PRs during times when I can't get my hands on those things.
Speaker A
Third is the glue work.
Speaker A
This is a bottleneck that I feel every single day.
Speaker A
Every minute that I spend project managing or copying and pasting or scheduling content or documenting things, that's time that I'm not thinking, creating or building.
Speaker A
And those tasks should be automated or delegated.
Speaker A
And that's exactly what my general assistant, Gumbo, is for.
Speaker A
And the use case that has me most excited is reporting.
Speaker A
So, having my agents surface trends and patterns and new ideas on a regular basis, helping me see blind spots that I wouldn't notice on my own.
Speaker A
That's the kind of insight that helps me teach ideas that actually help builders get ahead.
Speaker A
And helps me create tools that solve real problems.
Speaker A
Now, I've already started assembling the building blocks, the processes for my agents to follow.
Speaker A
The automations, the custom tooling.
Speaker A
And I'd love to report back on a future video to show you how all that's coming together.
Speaker A
So, make sure you subscribe to the channel.
Speaker A
Now, I want to be careful not to oversell Openclaw.
Speaker A
It's still very early, very raw.
Speaker A
And I spent more late nights than I'd like to admit just getting things configured.
Speaker A
But there's no denying the breakthrough as a concept that Openclaw has broken open here.
Speaker A
At least in our circles of AI-pilled builders.
Speaker A
And I see this as one of those things that's worth our extra effort to be an early adopter on.
Speaker A
Because systems like this are only going to become more commonplace as this year and next year play out.
Speaker A
And that gets at something that I think is a fundamental skill for us as builders in 2026.
Speaker A
We have to be willing to explore and tinker to figure out how new tools can help us make real progress in our business.
Speaker A
That's the value that we bring to the table and it's one of the five essential skills that I think we need to master to go from being overwhelmed by the speed of change to actually thriving in this new environment.
Speaker A
And I cover all five in my video on going from an AI skeptic to building an unfair advantage.
Speaker A
So, right after you hit subscribe on the channel, I'll see you on that one next.
Speaker A
Let's keep building.
Topics:OpenClawAI agentsautonomous agentsMac MiniBrian CaselAI productivityClaude MaxAI team managementlarge language modelsAI security
![[Full Episode]Nothing Else Compares（English-dubbed）#cdr… — Transcript](https://i.ytimg.com/vi/YYJruShKWz8/maxresdefault.jpg)
