Founder @ Omoha Solutions | Software + AI systems. I write about inner order, execution, and building leverage. Helping teams reduce chaos with structure.
I have a voice product live. The talking is the easy part. The real work is signup, the session, and whether a stranger can pay.
https://t.co/t2m8Zoc6Ch
Collected Grok Bot pro tips shared by the @bot team:
1) Connect multiple accounts across plugins (i.e. personal and work Gmail accounts)
2) One Chief of Staff plus a few specialists beats one mega-chat
3) Pin your top 1-2 agents for quick access
4) Have it keep a Notion page of outstanding work so you can ask "what's left" instead of babysitting
5) Treat each bot as a job, not a whole project
6) For difficult tasks, hit “teach a task” in the browser, record yourself doing it once, and the bot can repeat it
7) Ask the bot which team skills and plugins to turn on for your job
8) Tell your bot to generate an avatar for each of your bots
9) Consider turning on Always Allow and turning off Auto Review to make your bots more autonomous, make sure to test workflows first (be careful!)
10) Create sections in your sidebar to organize your bots
11) Resize the sidebar when you need additional space
12) Ask your bots to evaluate themselves and suggest improvements to workflows
GROK 4.6: The First Model to Beat the Unbeatable
Every big model tried to beat Kimi K3.
Claude Fable 5. Claude Opus 5. GPT Soul Max. GPT 3.8 Max.
All of them failed. Not one could do it.
Grok 4.6 just walked past all of them.
Here's the honest breakdown:
→ It beats Kimi K3 on real coding benchmarks. First model ever to pull it off.
→ It scored 61 on the Artificial Analysis index. Near the top of the pack.
→ xAI trained it with Grok 4.5's own data. The AI helped build its successor.
→ It's built for long-running agents. Whole projects, not one-off answers.
→ But the truth: on long heavy coding, GPT 5.6 Luna still edges it out.
Think of it as an A student in almost every subject.
One subject, a couple classmates score higher.
The real question isn't "which model is best."
It's "which model fits YOUR task."
Want the SOP? DM me. 💬
I caught myself trying to improve a process that should have been deleted. Building better systems also means admitting when a workflow no longer deserves to exist.
Today may be one of the most important days in the march toward the singularity. Not because one model crossed a final line, but because the pace of capability gains became impossible to ignore.
GLM-5.3 and Grok 4.6 landed almost back to back. Grok 4.7 may be only weeks away. This release cadence is going to cause massive disruption. The winners will not be the people loyal to one model, but the builders who can evaluate, switch, and ship before the market catches up.
I've become less impressed by how much an AI agent can do in a demo. The real test is whether I can trust it with a boring task on Tuesday, inspect what it changed, and recover cleanly when it gets something wrong.
Submitted a controlled proposal today. The hard part was not writing it. It was deciding exactly what not to promise, then putting that boundary in the offer.
Every SaaS founder eventually discovers that building the feature was the easy part. The harder work is packaging the value clearly enough that the right person understands why it matters and why it is worth paying for.
A clear mind does not come from having fewer problems. It comes from knowing which problem is yours to solve now, and refusing to carry the rest all at once.