Grok Bot 用量与权限不可预测的吐槽
有用户称一个 Grok Bot 工作流一天烧掉 Cursor Pro+ 周额度的 13%，并汇总了额度、访问权限、离开后能否继续跑这三类意外。
One Grok Bot workflow reportedly burned 13% of a $60/month Cursor Pro+ plan’s weekly Grok Bot allowance in ONE DAY. That is wild. But usage is only part of the problem. Users are still getting surprised by three things: What will this job burn? What can the Bot actually access? Will it still work when I walk away? That is the gap. Grok Bot can already do absurdly ambitious work. It can browse. Call. Run routines. Use connectors. Work across apps. Keep going while you are gone. But the boring stuff still matters. Multiple users reported Finance connection problems. Multiple users reported login and 1Password friction. Others could not find the X access they expected. And I found five separate examples of people mixing up Grok, Grok Bot, integrations, projects, automations, or where a feature actually lives. That does NOT mean Grok Bot is broken. It means the capability is moving FASTER than the predictability around it. And that might be the next big unlock. Not another flashy feature. Knowing exactly what your Bot can reach. What it will burn. And what happens when you leave it alone. That is when an agent stops feeling like a demo. It starts feeling like infrastructure. If you use Grok Bot every day, what still catches you off guard?