Grok bot 可能是第一个让非技术背景的人带一队 ai agent...

Grok bot 可能是第一个让非技术背景的人，用一队 ai agent 经营整间公司的工具，不用工程背景。 真正设得好，可以这样做。 1. 一次设置一个任务。agent 跑在共用云端电脑上，所以把电子报、社区发文和行政工作混进同一套，会把背景撑爆、token 烧很快。每个 bot 只管一件工作。 2. 从幕僚长开始。给它你现有的文档、notion、slack、gmail，你实际在用的那些，让它盘点生意，再告诉你最该先建、真正能推营收的三个 agent。 3. 先证明任务能做，再为它雇人。让幕僚长先手动做一次，你自己看产出，然后才说「现在建一个完全做这件事的 bot。」每个新 agent 都用证明过的任务换来，不要凭空雇。 4. 限制是功能，不是缺陷。agent 名额有限、一个 bot 一条讨论串，像私讯队友，逼你对准任务，而不是每个闪过的点子都开一个 bot。 5. 拍板的是你，不是 agent。没完没了地纠结内容该放哪、流程该怎么走，是陷阱。到某个点你决定、承诺、往下走。agent 执行你的决定，不是替你做决定。 6. 第一周不要加新 agent。先学真正的系统，用你已有的去执行。大概第三周，真正的缺口才明显，扩编才说得通，不要更早。 7. 反复例行工作最后再加。内核设置被证明之后，问幕僚长哪些反复工作真的能在你睡觉时把生意往前推，让它去建那些自动化。

原文：Grok bot might be the first tool that lets a non-technical person run an entire business with a team of ai agents, no engineering background required. here's how to actually set it up well. 1. one mission per setup. agents run on a shared cloud computer, so mixing your newsletter, your social posting, and your admin work into one setup creates context bloat and burns through tokens fast. scope each bot to one job. 2. start with a chief of staff. give it access to your existing docs, notion, slack, gmail, whatever you actually use, have it audit the business, then tell you the top three agents worth building first to actually move revenue. 3. prove a task works before you hire for it. have the chief of staff do the task once manually, review the output yourself, and only then say "now build a bot that does exactly that." earn each new agent by proving the task first, don't hire speculatively. 4. the constraints are the feature, not the limitation. a limited number of agent slots, one thread per bot, like dming a teammate, forces you to stay mission-oriented instead of spinning up a bot for every passing idea. 5. you make the calls, not the agent. endless tinkering over where content should live or how a process should work is a trap. at some point you decide, commit, and move on. the agent executes your decision, it doesn't make it for you. 6. run week one with zero new agents. just learn the actual system, execute with what you already have. week three or so is when the real gaps become obvious and expansion actually makes sense, not before. 7. add recurring routines last. once the core setup is proven, ask your chief of staff what recurring jobs would genuinely move the business forward overnight, and let it build the automations that run while you sleep.

集成