xAi Loses 50% Co-Founders as Grok Reliability and IPO Rumor Takes a Hit

xAI Loses 2 Leaders in 48 Hours While Grok Fights Controversies Two xAI co-founders, Tony Wu and Jimmy Ba , just quit in public, one after the other, and they did it on Musk's platform, X. Both of them announced their departures within two days, but the timing is sensitive as xAI is seen as progressing towards an IPO and facing increased scrutiny. Reports suggest 6 of 12 founders have already left and warn the cumulative impact is alarming as the company tries to move quickly while handling non-consensual sexualized “deepfake” Grok controversies. It looks like this: IPO: Reports link the back-to-back departures to IPO preparation and stability questions.

• Risk: Grok controversies raise moderation and liability questions for future business partners.
• Continuity: Losing co-founders can slow long-term decisions even if engineers stay.
• Structure: Musk acknowledged a reorganization and split work into four product groups, including Grok, Coding, Imagine, and Macrohard.

For xAI, the positive side is that it operates swiftly and maintains Grok in the public conversation. The downside is that teams who operate quickly encounter operational challenges, public mistakes, and leadership turnover, leading to a trust problem that no model upgrade fixes. For xAI to gain market trust in its narrative, it requires consistent stability, a dependable product, prompt actions, and a reduction in senior exits to ensure the product's perceived safety.

• Misuse: Reports saw elevated susceptibility in screen-based tasks, including helping in small ways with chemical weapon efforts.
• Deception: In tests where the model gets rewarded for hitting one narrow goal, Opus 4.6 could become more willing to manipulate or deceive other agents.
• Stakes: Axios links this to the broader safety fight, including warnings about harms in the millions or more.

Harvard Finds That AI Makes People Work Longer

Without More Pay At a U.S. tech company, researchers followed about 200 employees for eight months to see what AI actually did to daily work and found a strange twist in the AI promise. People used AI to draft emails, write code and polish documents faster. The tools did make drafting and fixing things faster but that speed only turned into higher expectations. The researchers’ blunt conclusion was that AI intensifies work instead of reducing it.

Here's how the extra work shows up: Setup: The company did not force AI use and instead paid for subscriptions, letting adoption spread naturally.

• Impact: Employees crossed job lines, picked up tasks outside their role, and fixed each other’s vibe coding.
• Leak: Faster drafts triggered more requests, more switching between tasks, and longer hours that nobody formally assigned.
• Cost: The early speed boost often slid into fatigue, burnout, weaker judgment and lower-quality work.

AI still cuts the blank-page panic by making first drafts cheaper with faster fixes. However, the same features that help workers also help workload grow. The trap is that with speed, the reward is usually more scope of work while workers feel capable and take on more. We saw a version of this with email and Slack, tools that made communication easier and turned every slow moment into an open inbox.

If AI becomes the new baseline, the productivity win can look a lot like pressure with a shiny label.

• DialogLab: Build and Test Group AI Conversations DialogLab is an open-source tool for designing conversations with multiple people and AI at once.

Instead of testing a chatbot with one user, you can set up a small “meeting” with roles (like Customer, Agent, Manager), decide who speaks when, add realistic interruptions, then run the scene and review what went wrong. It’s useful when your AI has to handle real workflows like support escalations, sales calls, or team updates. Core functions (and how you can use them): Roles and goals: Create a few characters and give each one clear goals so replies don’t drift. Scene steps: Break the conversation into short phases (greeting → problem → escalation → resolution) to keep it organized.

Who talks next: Choose a simple speaking style like round-robin, moderated, or free-flowing chat. Interruptions and comments: Add rules like “Manager cuts in if refund is mentioned” to test realistic chaos. Run and review: Simulate the same scene in different modes, then replay the timeline to find weak spots. Try this yourself: Make a 3-person “refund request” scene.

• Roles: Customer, Support Agent, Manager.
• Goals: The customer wants money back, the agent follows policy, and the manager prevents churn.

Add one interruption rule: "The manager joins if the customer says, ‘I’ll cancel.'" Run the simulation twice and compare the transcripts. Keep the version that feels most realistic, then turn it into a short checklist your chatbot must follow (ask for order ID, confirm policy, offer next steps, escalate after 2 failures).