来自 @fedeecaccia 的 Grok Bot 案例

嘿！我今天的建议：别叫 Grok Bot Agent 直接运行代码。改叫它们去编排云端的 Cursor Agent。 为什么？ - 编排层留在 Grok Bot。 - 你可以在 @cursor_ai 选不同模型和多个 Agent。 - 最重要的是，你不会烧光宝贵的 Grok Bot 余额。运行改走你的 Cursor 余额。底层计费相同，但两边余额消耗速度差很多。 这套设置对我很好用。 你在项目里是怎么编排 AI Agent stack 的？

原文：Hey! My recommendation of the day: don’t ask Grok Bot agents to execute code directly. Ask them to orchestrate Cursor agents in the cloud instead. Why? - You keep the orchestration layer in Grok Bot. - You can choose different models and multiple agents in @cursor_ai . - Most importantly, you don’t burn through your valuable Grok Bot balance. The execution happens through your Cursor balance instead. Same underlying billing, but the two balances are consumed at very different rates. This setup has been working really well for me. How are you orchestrating your AI agent stack in your projects?

集成