GPT-4.5 FLOP, Claude 3.7 Sonnet starter pack — the early March 2025 vibe shift

IndyDevDan’s March 3 video — “GPT-4.5 FLOP? Claude 3.7 Sonnet STARTER PACK. What is Claude Code REALLY?” — landed days after two consequential launches and called the vibe shift before the discourse caught up. OpenAI shipped GPT-4.5 in late February. Anthropic shipped Claude 3.7 Sonnet + Claude Code roughly the same week. The market reaction was lopsided in a direction OpenAI did not expect.

Dan’s framing was clean: GPT-4.5 was a chat-tier improvement at frontier-tier pricing. Claude 3.7 Sonnet was a real model upgrade plus the first version of Claude Code — Anthropic’s terminal-native agent that, by March’s end, would be cited in every “what’s actually changing in dev tools” thread on Reddit.

What GPT-4.5 actually was

OpenAI’s framing for GPT-4.5: “our largest and best model for chat to date.” Trained on more compute, more data, designed for emotional intelligence, better at conversational nuance.

What it wasn’t: a coding model. Benchmarks landed unspectacular on SWE-bench, HumanEval, LiveCodeBench. Pricing was high. The API rollout was limited (ChatGPT Pro first, then Plus). For the developers who had been waiting for GPT-5-shaped progress, this was not the model they were waiting for.

Dan’s read in the video: GPT-4.5 was OpenAI’s “the next jump is harder than expected” admission, packaged as a launch. The community largely agreed within days.

What Claude 3.7 Sonnet + Claude Code actually was

Anthropic shipped two things at once, and the combination mattered more than either alone:

Claude 3.7 Sonnet — a hybrid reasoning model. Same Sonnet family that had been Anthropic’s workhorse since mid-2024, but now with optional “extended thinking” that traded latency for quality. Benchmark improvements were real (SWE-bench Verified ~70%), but the bigger story was the model’s specific tuning for agentic workflows — long task chains, tool use, multi-step coding loops.

Claude Code — Anthropic’s first official CLI-native coding agent. Terminal-first, file-system aware, runs the agent loop locally. No editor required. No IDE plugin. Just Claude in your shell, doing your work. For engineers who had been frustrated with Cursor’s pricing changes and the IDE-extension layer of abstraction, this was a different shape of tool.

Dan’s follow-up DEVLOG on March 10 — “Claude Code has CHANGED Software Engineering” — went further: this isn’t “another coding assistant.” This is a category reset.

The community read

The r/ClaudeAI threads through March crystallize the reception. Two stand out:

The “85% problem” thread (1,775 upvotes): A non-technical user describes building real software with Claude Code — and hitting a wall at 85% completion where the model can’t finish the last 15% without senior-engineer-level intervention. This thread became the canonical “Claude Code is amazing but not magic” reference for weeks.

“I’ve watched it generate working features in minutes. Then I’ll ask it to fix a subtle bug and it goes in circles. The 85% problem isn’t theoretical — it’s where every non-trivial project lands.”

The “100% AI-generated code” thread (2,303 upvotes): A technical user (different audience) reports shipping a NodeJS + MongoDB project with Claude Code + Cursor entirely AI-generated. The 12-point breakdown reads like a methodology paper: structure first, commit often, handover docs between sessions.

“The most important step is setting up a clear project structure. Don’t ask Claude to write a feature — give it the file tree and the context for that file, then ask.”

These two threads, two weeks apart, are the same story from opposite angles. The model + agent combination is genuinely useful for shipping real work. The non-technical user’s “85% problem” and the technical user’s “structure first, commit often” methodology are the same lesson: the tool is real, the discipline required is also real.

Creator POV vs Reddit dissent

Dan’s POV through March is bullish on Claude Code specifically — he repeatedly returns to it across his TOP 6 PRO tips, the codebase architecture series, the slash commands deep-dive. His thesis: Claude Code is the daily driver; Cursor and other IDE-extension tools are now in the niche-tool category.

The Reddit dissent has three flavors:

• “Cursor is still better for visual workflows.” Many devs preferred IDE-integrated AI for tasks involving lots of file navigation. Claude Code’s terminal-only ergonomics didn’t fit their muscle memory.
• “It’s expensive.” Claude Pro at $20/mo didn’t include Claude Code at launch; API pricing for Claude Code via the Anthropic API was real money for heavy users. Cost-conscious indie devs stayed on Cursor.
• “It hallucinates file paths.” Early Claude Code had reliability issues — claiming to have edited files it didn’t, getting confused on monorepos. This improved over April-May but March users hit it.

The pro-Claude-Code dissent (counter to Dan): “this is just Anthropic’s response to Cursor’s success and the agent will stagnate once Anthropic gets distracted.” The pro-Cursor counter-counter: “Anthropic owns the model and the agent — they will iterate faster than Cursor can adapt.” History through 2025-2026 favors Anthropic’s position.

What this means for working engineers in March 2025

Three practical reads from the moment:

1. Default to Claude 3.7 Sonnet for coding work. GPT-4.5 isn’t the right tool. Cost-quality math favors Sonnet for the foreseeable months.

2. Take Claude Code seriously even if you don’t switch. The terminal-first agent pattern is now real. Even if you stay on Cursor/Windsurf, watching how Claude Code evolves is the leading indicator for where the tooling category is going.

3. Plan for the “85% problem.” The model gets you to 85% of any task. The remaining 15% requires you. Budget accordingly — fewer projects, more depth on each.

The honest critique

What this story does NOT mean in March 2025:

• GPT-4.5 isn’t useless. For chat / emotional-intelligence tasks, it’s measurably better than 4o. For coding, it’s not the right tool.
• Claude Code isn’t a solved product. Reliability issues, expensive for heavy use, terminal-only ergonomics aren’t for everyone.
• The “85% problem” doesn’t mean AI coding is hype. It means AI coding is real but not magic — the last 15% is where engineering judgment lives.

For most working engineers reading this in early March 2025: the vibe shift is real, Claude is ascendant, OpenAI is recalibrating, and the agent-loop pattern is now the dominant shape of AI dev tools. The next 12 months will be downstream of decisions made this quarter.