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 可能無法載入。這一頁的摘要和譯文會留下來。