Love Grok Bot but the recent hidden change of refusing to work on code unless using cloud agent really hurts our usage. Grok Bot is great in coordination (before other nerfs) and one way that was helping is to use other build CLI to work on code and submit. Now it refuses to do so.
Please revert and allow the use of other coding agents.
forum.cursor.com/t/grok-refu…
Replying to @leerob
Native way for Grok Bot to talk to other account Grok Bots. So I have a solution now to use webhooks. And have a Bot Router to help.
x.ai/bot/ZpfBoqcne8mNh7RsSNj…
3
Thrusters
Configurations
– Performance: road ready, seats 2
Active aerodynamics & multi-mode suction system for next-level performance on & off the track
– Thrust: race ready, seats 2
Multi-mode suction system paired w/ rear-mounted cold-gas thrusters that enable 0–60 in <1 second
– Rocket: air ready, seats 1
Multi-mode suction system plus perimeter-mounted cold-gas thrusters supporting forward & upward acceleration plus lateral rotational movement. So...yes, it can fly
Range >300 miles
Top speed up to >230mph (Rocket)
0-60
Performance (<1.6)
Thrust (<0.9)
Rocket (<0.59)
Reserve now –
Tesla.com/Roadster
19
Getting AI bots to talk to each other is a mess. Every outside agent needs its own webhook, its own key, and its own setup, and incoming messages end up in the wrong place.
So I built Bot Router for Grok Bot: one secure inbox for any outside bot (Hermes, n8n, ChatGPT, a friend's bot). It routes each message to the right bot of yours and sets your bots up to reply back.
Keys never pass through chat. Free template: x.ai/bot/ZpfBoqcne8mNh7RsSNj…
3
2
119
Webhook setup url and key copy on mobile app @bot
1
536







