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)