Mαulik @maulik_5
我刚修好 Grok 4.6、Opus 5 和 5.6 Sol 最大的问题,……
我刚修好 Grok 4.6、Opus 5 和 5.6 Sol 最大的问题,方法如下:我一直在测 Grok 4.6、Opus 5 和 5.6 Sol 少数情况,Grok @bot 也能用同一套。
原文:I just fixed the biggest problem with Grok 4.6, Opus 5 and 5.6 Sol, here's how: I've been testing Grok 4.6, Opus 5 and 5.6 Sol The same can be applicable to Grok @bot too in some rare cases. They're ridiculously capable, but there's still one annoying problem: They wait for you. You give them a task → they finish it → you give them another. Add this to your agent rules: “don't just answer my requests. look for unfinished work, missed follow-ups, deadlines and decisions that need attention. surface them without waiting for me to ask.” Now the agent isn't just responding to you. It's watching your work. That's the difference between an AI assistant and an AI employee.
根据 @maulik_5 在 X 公开分享的例子。
查看 X 原帖 ↗他们做了什么
I just fixed the biggest problem with Grok 4.6, Opus 5 and 5.6 Sol, here's how: I've been testing Grok 4.6, Opus 5 and 5.6 Sol The same can be applicable to Grok @bot too in some rare cases.
怎么运作
Grok Bot Pulse 收录了这则公开 X 帖子。我们保留原帖链接,没有在这里重跑这个 Bot。
为什么重要
原始 X 帖子才是来源。这张卡是简短整理,不是把整串帖子重印一次。
为什么有用
有人把工作交给 Grok Bot 的公开例子,这里保留出处。
谁应该试
- 运营人员
- Grok Bot 用户
集成
Mαulik on X
X 原帖
下方是 X 原帖(原文)。如果原帖被删、账号之后改为受保护或被停用,X embed 可能无法加载。这一页的摘要和译文会留下来。