Name: 我的多智能體團隊：OpenClaw 實測！ (My Multi-Agent Team with OpenClaw)
Uploaded: 2026-02-26T04:19:48.000Z
Duration: 14 min 29 s

程度副詞

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 using OpenClaw.

好的，我桌上放著一臺新的 Mac Mini，我特地設置它來運行我的 AI 代理程式團隊，使用 OpenClaw。

I've got a developer, a marketer, a project manager, a system admin.

我有開發者、行銷人員、專案經理、系統管理員。

They each have their own personality, they've got a queue of tasks tracked in this custom dashboard that I built.

他們每個人都有自己的個性，他們有一系列的任務，這些任務都記錄在我建的這個客製化儀錶板裡。

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.

我在 Slack 上跟他們哈拉，就像跟我的真實團隊成員一樣，只是他們是透過 OpenClaw 和各種大型語言模型驅動的代理程式。

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, like should I order a new Mac Mini or can I run openclaw on a vps?

過去一週，熬了好多個夜晚，我得一一找出問題的答案，有些是技術性的，有些是策略性的，像是該不該買一臺新的 Mac Mini，或者我能不能在 VPS 上運行 OpenClaw？

And what's this gonna cost me in API tokens?

這會在 API 令牌上花我多少錢？

我能不能使用我的 Claude Max 方案？

And what chat tool is best for my agents?

哪個聊天工具對我的代理程式最好？

Telegram or WhatsApp or some should I have it power one agent or can I set up a team of agents?

Telegram 或 WhatsApp，或者我應該讓一個代理程式來處理，還是可以設定一個代理程式團隊？

And am I going to need a custom dashboard for managing them?

我需要一個自訂的儀錶板來管理它們嗎？

What should my agents be able to access and how should I think about safeguards?

我的代理程式應該能存取什麼，我又該如何考慮安全措施？

And most importantly, what's my use case here?

最重要的是，我的使用情境是什麼？

What will I have my team of agents actually do for me?

我的代理程式團隊實際上會為我做些什麼？

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.

所以今天我會分享我對這些問題的最終決定，並向大家展示我所有的設定。

You know, to be honest, I didn't see the appeal of openclaw at first.

說實話，一開始我不太懂 OpenClaw 的吸引力在哪裡。

Back when it was called claudebot and then Multbot and it was buzzing around Twitter.

以前它叫做 Claudebot，然後是 Multbot，在 Twitter 上引起熱議的時候。

A couple weeks ago, everyone was talking about having their agent respond to their emails for them or book flights or order takeout.

幾週前，大家都在討論讓代理程式幫忙回覆電子郵件、訂機票或訂外賣。

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.

而且我個人生活不需要、也不想要 AI 代理程式，甚至不希望它來管理我的行事曆。

But then I started thinking about a real challenge that I've been having in my business and how setting up Open Cloud could help me solve it.

但後來我開始思考我事業上一個真正的挑戰，以及設定 Open Cloud 能如何幫助我解決它。

You know, I run this YouTube channel and builder Methods Pro and my courses and a weekly newsletter and.

你知道的，我經營這個 YouTube 頻道、Builder Methods Pro、我的課程，還有每週的電子報。

And thanks to things like Claude Code, of course, building things has never been easier.

當然，多虧了 Claude Code 這類東西，開發東西變得前所未有的容易。

I develop training content, I manage a publishing pipeline and I oversee my membership business.

我開發訓練內容、管理發行流程，並且監督我的會員業務。

There's so much more that I want to create and deliver.

我還有好多好多東西想創作和交付。

In my past businesses, I solved this by Hiring real teams and building processes to help us scale.

在我過去的事業中，我透過聘請真實的團隊並建立流程來幫助我們擴大規模，以此解決這個問題。

So when I gave openclaw another look, I asked a different question.

所以當我再次審視 OpenClaw 時，我問了一個不同的問題。

But what if this could fill roles on my team?

而是如果這能填補我團隊中的職位呢？

And now I'm convinced that this paradigm autonomous agents with defined roles running on their own machines.

現在我確信，這種由具有明確角色的自主代理程式在其自己的機器上運行的模式。

Now, OpenCloud is just the first generation of what I think will be much bigger.

現在，OpenCloud 只是我認為會變得更大的第一代產品。

And maybe this video can help you get started too.

也許這支影片也能幫助你開始。

如果你是第一次來，我是 Brian Castle。

I help builders stay ahead of the curve with AI.

我幫助創作者們透過 AI 保持領先。

And every Friday I send my builder briefing.

每週五我都會寄送我的創作者簡報。

That's a free 5 minute read where I give you my no hype take on making this transition to adopting AI.

這是一份免費的 5 分鐘閱讀，我會給你我對採用 AI 的真實看法，沒有誇大其詞。

You can get yours by going to buildermethods.com and if you're serious about leveling up, check out Builder Methods Pro, where you can join our community and get training for builders.

你可以到 buildermethods.com 領取，如果你真的很想提升自己，可以看看 Builder Methods Pro，在那裡你可以加入我們的社群，並獲得創作者的訓練。

It used to be called claudebot and then Moltbot.

它以前叫做 Claudebot，然後是 Moltbot。

And how is this actually different from how you might use Claude code or any other agent?

這跟使用 Claude code 或任何其他代理程式有什麼不同？

The core of openclaw is what's called the gateway.

That's a process running on a machine, which shouldn't be your personal machine.

這是一個在機器上運行的程序，不應該是你個人的機器。

But we'll talk about security in a moment.

Of course, Claude code can do a lot of that too.

當然，Claude code 也能做到很多這類事情。

But what makes OpenCloud different is that it's always on.

但 OpenCloud 的不同之處在於它始終保持運行。

It maintains a persistent workspace with memory and session logs, so you can chat with your agents through Telegram or Slack and delegate tasks that they can do on their own in the background.

它會維護一個持久的工作區，裡面有記憶體和會話記錄，所以你可以透過 Telegram 或 Slack 與你的代理程式哈拉，並委派任務，讓它們在背景自行處理。

So that's a fundamentally different paradigm from you personally managing CLAUDE code sessions in your terminal.

這與你個人在終端機裡管理 Claude code 會話，是完全不同的模式。

Openclaw is closer to having teammates who do their work on their own workstations.

Openclaw 更像是擁有會自行在工作站上完成工作的隊友。

The first question is, where should this thing run?

第一個問題是，這個東西應該在哪裡運行？

Now, I don't recommend you run openclaw on your daily driver machine.

不過，我並不建議你在日常使用的電腦上運行 OpenClaw。

You don't want to give it unfettered access to your files and your accounts.

你不會想讓它不受限制地存取你的檔案和帳號。

And even if you isolate it with something like Docker, your machine would need to be on and awake 247 for your agents to work.

即使你用 Docker 之類的東西將它隔離，你的電腦也需要 24/7 開機且保持運行，你的代理程式才能工作。

So Openclaw needs its own dedicated machine.

所以 OpenClaw 需要它自己的專用機器。

That could be a cloud VPS starting at around five bucks a month.

可以是每月大約五塊美金起的雲端 VPS。

Doesn't have to be a Mac Mini, any kind of computer on Your network both are valid and a lot of people are doing well with the VPS setups.

不一定要是 Mac Mini，你網路上的任何電腦都可以，很多人都用 VPS 設定得很好。

But I went ahead and I spent the 600 bucks on a new Mac mini M4.

不過我還是花了大約 600 塊買了一臺新的 Mac Mini M4。

I like to be able to screen share into it, see the desktop, install things and manage it visually.

我喜歡能夠螢幕共享進去，看到桌面，安裝東西並視覺化地管理它。

And I ssh in too when I just need to run a quick command.

而且我也可以透過 SSH 登入，只要我需要執行一個快速指令。

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, so the cost would start to balance out anyway.

而且如果我最後會把我想到的所有使用情境都交給我的代理程式團隊處理，我需要的儲存空間和頻寬就會比便宜的 VPS 套餐來得多，所以成本其實也會差不多。

And hey, if none of this works out, I'll throw that Mac Mini up in my home music studio.

而且嘿，如果這些都行不通，我會把這臺 Mac Mini 放在我的家庭音樂工作室。

I need to think carefully about what my agents can and can't access.

我需要仔細思考我的代理程式可以存取什麼，不能存取什麼。

Now this is where the hiring metaphor really kicked in.

現在這就是聘用比喻真正發揮作用的地方了。

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.

如果我要找人加入我的團隊，我不會給他們存取我個人筆記型電腦的權限，也不會讓他們在一個我登入所有東西的瀏覽器裡隨意操作。

Now an employee would get their own machine, their own email access to the files and services that they need with the right permissions, nothing more.

現在一個員工會拿到他們自己的機器、他們需要的檔案和服務的電子郵件存取權，並擁有正確的權限，不多也不少。

I set up a dedicated email address for my agents.

我為我的代理程式設定了一個專用的電子郵件地址。

I created a GitHub username that I can invite to specific repos.

我創建了一個 GitHub 使用者名稱，可以邀請他們加入特定的儲存庫。

I can grant and revoke access to services just like I would with any other team member.

我可以像對待任何其他團隊成員一樣，授予和撤銷對服務的存取權。

現在，檔案處理起來有點棘手。

I want easy two way syncing between my computer and the open cloud workspace on the Mac Mini, 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.

我希望我的電腦和 Mac Mini 上的開放雲端工作區之間能夠輕鬆實現雙向同步，特別是我正在開發一個大腦系統，我所有的商業活動都會記錄在 markdown 檔案中，我的代理程式可以存取並處理這些檔案。

So all my files live either in GitHub repos or my main Dropbox account.

所以我所有的檔案都儲存在 GitHub 儲存庫或我的主要 Dropbox 帳戶中。

But I don't want to just share my personal Dropbox with OpenClaw.

但我不想直接與 OpenClaw 分享我的個人 Dropbox。

So I had openclaw set up its own Dropbox account.

所以我讓 OpenClaw 設定了它自己的 Dropbox 帳戶。

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, and

而我想要在我主要的 Mac 和 OpenClaw 的 Mac Mini 之間共享的特定資料夾，兩個 Dropbox 帳戶都能存取，

這樣其他東西就都能被隔離在外了。

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.

因為如果你不小心，光是跟你的代理程式哈拉和執行任務，就很容易累積數百甚至數千美元的令牌費用。

I blew past $200 in the first two days of setting up my system.

我在設定系統的前兩天就花掉了 200 美元。

Now I already pay for a Cloud Max plan and I was hoping that I could just use that, but

現在我已經付費訂閱了 Claude Max 方案，原本希望能直接使用它，但

then I heard the stories of accounts being shut down because this type of usage might be against Anthropic's terms of service.

聽說有些帳戶被關閉，因為這種使用方式可能違反 Anthropic 的服務條款。

And then within a few days he upgraded to the $200 subscription or euros because he's in Austria and he was in love with that thing that for me was like a very early product validation.

幾天後他就升級到每月 200 歐元的訂閱方案，因為他人在奧地利，而且他非常喜歡那個東西，對我來說就像是早期產品驗證一樣。