The barriers between AI model providers are becoming increasingly high. This situation is driven by commercial, technological, and market factors—and even personal rivalries. Yet, one thing is certain: this is not good for users. Moreover, as time goes on, ordinary users will have less and less say regarding their use of AI.
The most terrifying prospect is that robots (AI) will increasingly resemble humans, while humans increasingly come to resemble robots—subject to manipulation and external control, forced to simply accept their lot.
Collected a new list of Grok Bot pro tips shared by the @bot team:
1) Ask Grok Bot to set up Peekaboo on your Mac to enable more OpenClaw like features
2) Use bots as roles (designer, engineer, or PM.) Each has its own system prompt and routines
3) Use channels to organize projects and workstreams. Same bot can work across many different channels
4) Avoid scheduled routines that run too frequently. Hourly or a few times a day is usually good enough
5) For recurring tasks, try giving that to a fresh bot, while you continue your chat with your main bots (like a chief of staff)
6) Set up customizable rules to allow or deny actions. For bots that are connected to X, Gmail, etc. consider blocking any write/destructive actions and have it ask for approval first
7) Feed your Bot examples from your previous handwritten content, it will get better over time
8) Make a Chief of Agents. Give it the rules you want every bot to follow: draft only, naming, voice, what tools they’re allowed to touch. For any new Bots, ask it to create them for you with same rules.
9) For routines, ask yourself if a real human teammate could do this job? If yes, build it. If no, optimize it first. Never run a routine every 5 minutes.
10) Name-driven behavior. Bots act proactively just from the name given at creation. The role is legible from the name, and that alone helps steers behavior.
tips sourced from @naoufal_elh@kiaraplds@johnbai@shaoruu@poteto@pengzheng_@leerob
The best thing about the Grok @bot is that it grants you extensive access to a cloud-hosted instance (with impressive specs), opening up vast possibilities for creativity. I currently plan to install @Kimi_Moonshot Code CLI to consolidate a workflow that previously required switching between multiple tools into a seamless, all-in-one process.
*** In my line of work—commercial real estate research and analysis—Kimi’s built-in professional database plugins have proven incredibly useful (I highly recommend giving them a try). I have also established a comprehensive automated workflow using Kimi.
Grok Build on Android just got a major update that brings serious end-to-end app development right into your pocket
This update adds some seriously useful pieces:
• Push projects straight to GitHub
• Store API keys and secrets
• Lock apps to invited users
• Download builds directly
• Connect custom domains
• Share projects straight to 𝕏
The crazy part is what this means in practice
You can now sit on your phone, build an app with Grok, connect the backend pieces, secure it, publish it and ship the code without ever moving to a laptop
Grok Build is getting dangerously close to making “I have an idea” → “the app is live” something you can do from anywhere
What @nvidia needs to guard against now comes not from its direct competitors, but from the very customers who once placed massive orders with it—including, but not limited to, @OpenAI , @AnthropicAI , and @Google .
There is more to come.
What strikes me is that, within the rapidly evolving AI industry, companies situated at various points along the value chain face such an urgent need to build "moats" connecting their upstream and downstream operations.
https://t.co/47SELuYR9h
Wrapping the backend access permissions of an application you’ve built into an @ChatGPT MCP is an incredibly useful capability.
You can invoke it directly in Chat mode, solving the inconvenience of not having your computer with you.🥳