Brace yourself for a political soap opera featuring two of America’s biggest personalities, Elon Musk and President Donald Trump, whose recent spat could power a SpaceX rocket all on its own.
According to the Daily Mail, this high-stakes drama, erupting over a massive spending bill and a scrapped NASA nomination, saw tensions flare on Thursday before cooling by Friday evening with both men extending olive branches.
The feud ignited on Thursday when Musk, Tesla’s visionary CEO, publicly slammed Trump’s so-called “Big Beautiful Bill,” a spending measure projected to balloon the national debt by $3.8 trillion on top of the already staggering $36 trillion.
Musk didn’t hold back on X, arguing the bill would shackle the nation in “debt slavery” and undercut his DOGE team’s efforts to streamline government waste. Well, turns out even billionaires can’t stomach a blank check when it’s taxpayers footing the bill.
Adding fuel to the fire, Musk was livid over the cancellation of Jared Isaacman’s nomination to lead NASA, a decision Trump attributed to Isaacman’s past donations to Democrats. Trump even admitted this move “upset” Musk, which is putting it mildly when you consider Musk’s Mars colonization dreams were riding on that pick.
Behind the scenes, whispers from Musk’s allies and White House insiders point fingers at Sergio Gor, director of the Presidential Personnel Office, as the architect of this mess. Reports suggest Gor sabotaged Isaacman’s nomination, and tensions with Musk have simmered for months, including a March clash over leaked stories.
The Washington Post notes Gor was itching for payback against Musk, allegedly feeding Trump evidence of Isaacman’s donations despite Trump knowing about them long before. If true, this smells like petty politics, not principle, and it’s no way to build trust in a new administration.
Meanwhile, Musk’s net worth took a $27 billion nosedive in mere hours after the feud went public on Thursday, a reminder that even titans bleed when they clash. Still, by Thursday evening, Musk signaled a willingness to dial down the heat, deleting a provocative X post linking Trump to unrelated controversies.
In another pivot, Musk initially announced decommissioning his SpaceX Dragon spacecraft, a move that would’ve left the U.S. reliant on Russian tech for space access, but reversed course soon after. Call it a strategic retreat—sometimes playing nice is the only way to keep the mission on track.
Trump, for his part, initially threatened to yank loans and subsidies for Musk’s ventures but softened his stance by Friday, saying any action “would need to be fair.” Musk’s response on X? A succinct “Fair enough,” hinting at a truce. Yet, as a White House ally put it, “There’s hope that there’s going to be a reconciliation. But it'll never be the same.” Trust, once cracked, doesn’t glue back together overnight, no matter how many photo ops at Mar-a-Lago or rocket launches in Brownsville, Texas, they share.
Photographs of Musk and Trump together, from the Oval Office to a SpaceX Starship test flight on November 19, 2024, remind us they’ve been allies before. But alliances in politics are as fragile as a satellite in a meteor shower when egos and billions are at stake.
Some Republicans, alongside Musk, have voiced alarm over the spending bill’s fiscal recklessness, while conservative firebrand Marjorie Taylor Greene griped about an overlooked AI provision. It’s refreshing to see pushback against unchecked spending, even if it took a billionaire’s megaphone to amplify the concern.
If this bill flops in the Senate, Trump might face chaos and have no choice but to patch things up with Musk to steady the ship. White House officials, however, insist there’s no plan for a direct call between the two, suggesting this detente might simmer on the back burner for now.
Errol Musk, Elon’s father, offered a blunt take: “They will have to sort it out, and because Trump is the one who was elected, Elon is going to have to accept he is not going to be the general.” Wise words—Washington isn’t a SpaceX boardroom, and even Musk can’t rewrite the chain of command.
