讓 grok bot 方案用久一點：1）能用事件觸發就用...

讓 grok bot 方案用久一點： 1）能用事件觸發就用。slack、github、一個 reaction。真的發生事情 bot 才跑（cron 就算沒變也會叫醒它） 2）指示 bot，一進展不了或卡住就通知你。這樣你作為人可以再把它拉回路上 3）能用連接器就別用瀏覽器！在網站上點來點去是一堆截圖和步驟。連接器一次呼叫給你同樣資料，而且舒服／快／順很多 4）技能保持緊，但把真正會帶跑的細節放進去。太含糊 bot 可能亂走、重試，比稍長一點更貴。太具體你又得確保它真的正確 5）不要在 bot 聊天裡寫程式！對 repo 踢一個雲端 agent，或叫它用 cursor/grok build cli 做 6）一次性監看用完就刪（grok bot 會提醒你這件事）

原文：how to make your grok bot plan last longer: 1) use an event trigger when you can. slack, github, a reaction. the bot only runs when something actually happened (a cron wakes it even if nothing changed) 2) instruct the bot to notify you as soon as it can’t make further progress or is stalled. this way you as human can help putting it on the right course again 3) connectors > browser when possible! clicking around a site is a pile of screenshots and steps. a connector gives you the same data in one call, and it's so much nicer/faster/smoother 4) keep skills tight, but put in the details that actually steer the run. too vague and the bot might wander, retry, and costs more than a slightly longer one. too specific and you have to make sure its really correct 5) don't do the coding in the bot chat! kick a cloud agent at the repo, or ask it to use cursor/grok build cli to do it 6) delete one-shot watches when they're not needed anymore (grok bot will remind you about this)

整合