Grok Bot on Super Grok Heavy $300 a month does not last 2 days. If they don't figure out how to make it much more efficient I will cancel very soon and go all in on Open AI as I hear they have a $500 a month tier coming. Who else is using Grok Bot and experiencing fast crippling usage exhaustion. Grok Bot can't run my life or my business if it never has any usage available. Im averaging 8 actual days a month of real work with it before usage limits.

Grok, Cursor, Grokbot and X https://x.com/xfreeze/status/2104625424022274078?s=46

My Codex setup has evolved beyond a normal coding assistant. It now works as a background operational coordinator for my daily work, particularly email, quotations and the small decisions that would otherwise constantly interrupt me. I receive around 120 emails per day. A large percentage is internal chatter or information I need to be aware of but don't need to act on. Others require quotations, replies, follow-ups or specific actions. Instead of manually processing that stream, I have a coordinator chat in Codex that periodically receives my email and decides what should happen next. It can classify emails, archive or mark them unread, suggest what I should do, create drafts, send emails when appropriate and delegate work to specialised chats. For example, quotation requests are sent to a dedicated quotation chat with its own strict skill and workflow. When the quotation is finished, that chat communicates the result back to the coordinator, which then tells me that it is ready for review. The important part is that I remain in the loop without having to operate the system continuously. Codex's live voice is particularly valuable here. I can be working on something completely different while the coordinator continues processing things in the background. When something genuinely needs my judgement, it can simply talk to me: «“You received this. I think it should be archived and marked unread. Do you agree?”» Or: «“The quotation is ready for you to check.”» I answer by voice and continue working. Instead of reading and deciding what to do with 120 emails, I mainly deal with the relatively small number of decisions that actually require me. Why the model matters This is also why I currently cannot simply replace Codex with Grok Bot, even if Grok can technically perform the same orchestration. I have tested this. The problem isn't whether Grok can read an email, delegate to another chat or communicate results back to the coordinator. It can. Most of the architecture works.

The newest coding models write a lot of unit tests. Most of them restate the code they were written after, so they always pass and catch almost nothing. They run fast, but they break on every refactor and the agent burns time fixing tests instead of the feature. I now test with E2E runs that exercise the real feature and leave an artifact I can check and rerun. If a piece has to be tested alone, the model writes down how it could fail before it writes the code. The prompt I used to clean out mine. "This repo is full of low-signal unit tests. Delete every one that wouldn't catch a real bug our E2E tests miss. Fan the work out across parallel subagents, and use pstack and poteto-mode. Then add these rules to AGENTS.md so future agents stop writing them. Never write unit tests after you write code. Highly prefer E2E tests as the sole testing mechanism. Use them to verify complex features work. At the end of E2E tests, produce a verifiable and repeatable artifact. If you must test a system in isolation, first write down all the ways it could fail, then write the code."

How cool is this? There goes my weekend lol https://youtu.be/mrdFgLXiy-o?is=0Ni_zjqC6-SxCAs9 https://github.com/wombatoperator/omarchy-voice