Claude 4.8 Opus vs Claude 4.5 Haiku

As you can see in the graph above, while in October, the use of Claude Sonnet 4.5 Thinking was normal, since the 1st of November, Perplexity has deliberately rerouted most if not ALL Sonnet 4.5 and 4.5 Thinking messages to far worse quality models like Gemini 2 Flash and, interestingly, Claude 4.5 Haiku Thinking which are probably cheaper models.

Perplexity is essentially SCAMMING subscribers by marketing their model as "Sonnet 4.5 Thinking" but then having all prompts given by a different model--still a Claude one so we don't realise!

Very scummy.

Anthropic just dropped Haiku 4.5 and the numbers are wild:

**Performance:**

* 73.3% on SWE-bench Verified (matches Sonnet 4 from 5 months ago)
* 90% of Sonnet 4.5's agentic coding performance
* 2x faster than Sonnet 4
* 4-5x faster than Sonnet 4.5

**Pricing:**

* $1 input / $5 output per million tokens
* That's 66% cheaper than Sonnet 4 ($3/$15)
* \~10x cheaper than Sonnet 4.5 for 90% of the performance

**Why this matters:**

Multi-agent systems are now economically viable. Before Haiku 4.5:

* 10 agents × $15/million = $150/million (too expensive)
* 10 agents × 10s latency = 100s total (too slow)

With Haiku 4.5:

* 10 agents × $5/million = $50/million (3x cheaper)
* 10 agents × 2s latency = 20s total (5x faster)

**Use cases unlocked:**

* Real-time chat assistants (2s response time)
* Automated code reviews (\~$0.01 per review)
* Pair programming with Claude Code (no latency friction)
* Rapid prototyping (iterate as much as you want)

**Available now:**

* Claude.ai
* Claude Code (CLI + extension) - use `/model` command
* API: `model="claude-haiku-4.5-20251015"`
* AWS Bedrock
* Google Cloud Vertex AI

We wrote a deep-dive article (in French, but code examples and benchmarks are universal) with cost analysis, migration guides, and real scenarios: [here](https://cc-france.org/blog/claude-haiku-45-le-modle-qui-redfinit-le-rapport-p)

The barrier between "proof of concept" and "production" just got dramatically lower.

What are you planning to build with it?

Press CTRL+I to invoke Windsurf Command ([documentation)](https://docs.windsurf.com/command/windsurf-overview): this generates code at your cursor, or it edits blocks of text. It never uses any credits.

Also, GPT 5.1 Codex and 5.1 Codex Mini are free in Cascade / chat ([documentation](https://docs.windsurf.com/windsurf/models)).

Anthropic just dropped Haiku 4.5 and the numbers are wild:

**Performance:**

* 73.3% on SWE-bench Verified (matches Sonnet 4 from 5 months ago)
* 90% of Sonnet 4.5's agentic coding performance
* 2x faster than Sonnet 4
* 4-5x faster than Sonnet 4.5

**Pricing:**

* $1 input / $5 output per million tokens
* That's 66% cheaper than Sonnet 4 ($3/$15)
* \~10x cheaper than Sonnet 4.5 for 90% of the performance

**Why this matters:**

Multi-agent systems are now economically viable. Before Haiku 4.5:

* 10 agents × $15/million = $150/million (too expensive)
* 10 agents × 10s latency = 100s total (too slow)

With Haiku 4.5:

* 10 agents × $5/million = $50/million (3x cheaper)
* 10 agents × 2s latency = 20s total (5x faster)

**Use cases unlocked:**

* Real-time chat assistants (2s response time)
* Automated code reviews (\~$0.01 per review)
* Pair programming with Claude Code (no latency friction)
* Rapid prototyping (iterate as much as you want)

**Available now:**

* [Claude.ai](http://Claude.ai)
* Claude Code (CLI + extension) - use `/model` command
* API: `model="claude-haiku-4.5-20251015"`
* AWS Bedrock
* Google Cloud Vertex AI

We wrote a deep-dive article (in French, but code examples and benchmarks are universal) with cost analysis, migration guides, and real scenarios: [here](https://cc-france.org/blog/claude-haiku-45-le-modle-qui-redfinit-le-rapport-p)

The barrier between "proof of concept" and "production" just got dramatically lower.

What are you planning to build with it?

\[title has it all\]

I was just casually reading how LLMs are evolving and I found some pretty wild implications for how we might build with them going forward. Basically, model providers are taking over a lot of the heavy lifting for prompt engineering and context management that developers used to have to do themselves.

What started as a prompt engineering trick in 2022 (telling models to think step by step) is now being trained directly into models. This means better outputs without needing explicit instructions anymore. Anthropic trained Claude 4.5 Haiku to be explicitly aware of its context window usage. This helps the model wrap up answers when the limit is near and persist with tasks when there's more space reducing a phenomenon called- agentic laziness where models stop working prematurely.

Anthropic's memory tool lets Claude store and retrieve information across conversations using external files, acting like a persistent scratchpad. The model decides when to create read update or delete these files, solving the problem of either stuffing too much into the prompt or building your own complex memory system.

This feature allows clearing old tool results from earlier in a conversation. Currently limited to tool result, it uses placeholders to signal context trimming to Claude meaning you still manage message context but the tool handles some of the heavy lifting.

Providers handle prompt caching differently. OpenAI does it automatically while Anthropic requires you to add a bit of code to your API requests to enable it. This feature helps save on computational costs by reusing previous prompt computations.

This feature gives developers and the model real time awareness of how much context space is remaining in a session. It supports memory and context editing and can be used for other use cases too. OpenAi's retrieval API acts as a built in RAG system. Instead of managing your own vector database and retrieval pipeline you upload documents to OpenAi and they handle indexing, search and injecting context automatically.

So basically model providers are training their models to actually use these new tools effectively making the distinction between improvements baked into the model during training and those exposed via API tools increasingly unclear.

The bit about context management moving upstream and being handled by model providers is super interesting because i've been seeing this with prompt optimization. [Tools](https://www.promptoptimizr.com) like mine are trying to abstract away the complexity and it feels like the big players are starting to do just that with context.

My take is that this shift is going to democratize building advanced LLM applications even further. It feels like we're moving from an era of painstaking infrastructure building to one focused purely on agent design and intelligent orchestration. context editing and memory tools are abstracting away the need for developers to manually manage all that context and in practice i've been seeing how much time that saves users building complex agents.