𝓖𝓮𝓽𝓽𝔂 𝑰𝒏𝒗𝒆𝒔𝒕𝒎𝒆𝒏𝒕𝒔 ™

Update #2 (after meeting with the @bot @SpaceXSI engineering team): - Team is great. They care a ton. They owned it. - They admitted that it was almost entirely from pulling Opus 5.5 out. Which is now back as of this AM. - Learned a little bit about the context-compaction process with Grok 4.7-summarize which is not a public model. Plays a role in routing config and the summary we get back. - Grok 5.0 should be insane next level (just as an aside point) - I am somewhat surmising on why stuff went so poorly over the weekend but a lot of it has to do with not just pulling Opus 5.5 out but when they did that a known problem (and was on cursor as well) showed up which is when you switch the model mid task (which would’ve happened by removing our 5.5) it cannot remember the context and even of what it can gather its truncated (likely do to 4.7-summarize compacting). So in our case what likely happened was we had a lot of stuff mid flight that was likely pulling on opus 5.5 heavy, then it got pulled, routed to different model, forgot the context, and turned incredibly dumb. We laughed when I showed them a project that was mid flight in a doc. The first half of the doc was intelligently designed, formatted, etc. and the second half of the doc was a wall of seemingly incoherent, non formatted text. Again, I’m surmising but I think it was dumber model with all context removed - I won’t say much here but Elons comment on it being “unsustainably high relative to revenue” was a much larger chess move. Won’t say much past that. Not my place. But he’s definitely playing a much larger chess match than just “Grok bot isn’t sustainable”. - The problems we all experienced should be fixed and I do not think they want to go back to what they experienced over the weekend with the hit it took. - They are very much focused on the enterprise use case for grok bot in the future All in all, how’s this impact my decision making moving forward with the enterprise contract we have: - Honestly still weighing the decision vs just using team plan. Working through some terms - the reason to move forward is pretty simple. Unlimited users (so not paying per seat but for usage), access to forward deployed team and engineers for support and circumstances like I just experienced, very granular governing and guardrails for the org. That’s it Impressed with the team overall and I think the main benefit to staying vs moving to open source (for a company like mine vs being a solo/small company) is trusting their ability to ship and keep building plus keep it maintained. Shoutout to @ASankarraman for jumping in to help and to the @SpaceXSI, @bot, and @elonmusk teams