Skip to content

All news

5 today

Sep 28Monday

claude.dev Blog

How to design evals and hillclimb with Claude

Claude's claude-api skill added guidance on eval design and hillclimb optimization. In Claude Code, /claude-api build-eval builds an eval and /claude-api hillclimb improves an app step by step.

Why it matters: Claude organizes eval design and step-by-step optimization into workflows that need human confirmation, using held-out test sets and noise checks to cut overfitting and wasted changes.

claude.dev Blog

Claude Sonnet 5.5 dev guide: model choice, migration and tuning

Claude Sonnet 5.5 is available. Anthropic says it is 30% faster than Sonnet 5 at the same price per token, cutting cost by up to 30% on most tasks. It natively supports a 1M-token context window and has adaptive thinking on by default. The guide suggests using it for everyday tasks with clear requirements and checkable results, and leaving complex work that needs careful judgment to Opus 5.5.

Why it matters: The guide lists the parameter and parsing changes needed to migrate existing apps to Sonnet 5.5's thinking modes and tool calls.

Sep 25Friday

claude.dev Blog

How Opus 5.5 task cost in Claude Code is calculated

Task cost for Opus 5.5 in Claude Code comes from turns, cache reads, output tokens and model price, and cutting usage can raise retry cost. At API list prices, the same sample session falls from $3.50 on Opus 5 to $2.40 on Opus 5.5, about 31% lower, with cache writes excluded from the sample. The estimate of 40% lower cost on typical workloads also includes fewer task tokens under default settings.

Why it matters: The Claude Code cost guide bills turns, cache and thinking output separately, and uses the same task to separate a lower unit price from lower task consumption.

claude.dev Blog

Claude Code guide: matching effort level to the task

Claude Code's effort setting controls how much compute the model spends on a task. Higher levels add autonomous judgment, verification and edge-case testing; lower levels suit fast interaction and iteration. Drawing on Opus 5.5 tests and Terminal-Bench 3.0 results, the author suggests having the model interview you to clarify requirements first, then implement and iterate at low effort, and verify at high effort. More effort usually cuts failures from missed edge cases, but it cannot fix a wrong approach.

Why it matters: A tested workflow that splits fast iteration and edge-case testing across different stages of a Claude Code task.

Sep 22Tuesday

claude.dev Blog

How to get the most out of Opus 5.5 in Claude and Claude Code

Anthropic's official guide covers using Opus 5.5 in Claude and Claude Code, spanning prompts, long-task control and result checks. It recommends stating clear completion criteria, setting in CLAUDE.md the conditions for continuing versus stopping to ask, keeping task lists in files, and checking the evidence sub-agents submit.

Why it matters: Anthropic's guide breaks long tasks into completion criteria, stop conditions and result checks, using file lists and sub-agent evidence to cut missed steps.

Jul 24Friday

claude.dev Blog

New context engineering rules for Claude 5 generation models

Anthropic describes its context engineering approach for the Claude 5 generation models, cutting the Claude Code system prompt for Claude Opus 5 and Claude Fable 5 by more than 80% with no measurable loss on coding evals.

Why it matters: Anthropic splits context management into lightweight repo notes, on-demand skills and specific reference files, a transferable way to cut repeated instructions and over-constraint.

Jun 3Wednesday

claude.dev Blog

Building Claude Code: how Anthropic uses skills

Anthropic shared lessons from hundreds of active skills inside Claude Code, grouping them into nine uses and covering how to write, distribute and measure them. A skill is a folder of instructions, scripts and resources. Write down common errors, load reference files on demand, reuse helper scripts, and phrase the description as a trigger condition. Small teams can share skills through a repo; at larger scale an internal plugin marketplace works, with a PreToolUse hook logging usage to find skills that under-trigger.

Why it matters: Anthropic sorts internal skill practice into nine uses and distills a team skill library from error logs, on-demand file reads and script reuse.

Jun 2Tuesday

claude.dev Blog

How Claude Code dynamic workflows tailor an execution framework per task

Claude Code shipped dynamic workflows last week. Claude writes an execution framework for the current task on the spot, and workflows can be saved, shared and reused. They coordinate subagents through agent(), parallel() and pipeline() in JavaScript, can pick a model and a separate worktree, and resume a session after an interruption.

Why it matters: Claude Code splits execution and adversarial verification across subagents with separate contexts, a concrete orchestration method for cutting self-preference and goal drift on complex tasks.

May 20Wednesday

claude.dev Blog

Using Claude Code: why HTML beats Markdown for complex output

Thariq Shihipar, a member of the Claude Code team, shares a method for generating complex output in HTML instead of Markdown, to improve reading, visualization, sharing and interaction. He exports interface tweaks as prompts so manual edits feed back into the agent workflow.

Why it matters: A Claude Code team member generates interactive documents in HTML and turns interface tweaks into prompts, feeding manual edits back into the agent workflow.

Apr 30Thursday

claude.dev Blog

Building Claude Code: designing agents around prompt caching

The Claude Code team shared engineering lessons on prompt caching, keeping the request prefix stable to cut latency and cost in long agent sessions. Put static content first, update state through messages, avoid switching models or adding and removing tools mid-session, and use defer_loading to load tools late. When compacting context, reuse the original session's system prompt, tool definitions and history, then append the compaction request so it hits the cache. The team also tracks cache hit rate and treats an abnormal drop as an incident.

Why it matters: The Claude Code team applies cache prefix stability to prompt ordering, tool loading and context compaction, a transferable caching method for long agent sessions.

Apr 10Friday

claude.dev Blog

Tools from the agent's point of view: how Claude Code designs tools

The Claude Code team reviewed its tool design, stressing that tools keep changing with model capability, agent goals and runtime environment. AskUserQuestion became a standalone tool for structured questions after two failed attempts, and Task replaced TodoWrite with task dependencies and shared updates across subagents. Context retrieval moved from pre-indexed RAG to Grep search and progressive disclosure; the Claude Code Guide subagent searches docs in its own context and returns only the answer to the main agent.

Why it matters: The Claude Code team uses question asking, task collaboration and context search as examples of treating observed model behavior as the input to tool design.

Mar 11Wednesday

Mistral AI

Mistral builds an agent on Vibe that writes Rails tests automatically

Mistral built an agent on its open-source coding assistant Vibe that writes Rails RSpec tests on its own. It reads source code, generates or improves tests, checks them against style rules and coverage targets, and runs unattended in CI/CD.

Why it matters: Mistral published its full method for building an auto-RSpec-test agent on Vibe, including transferable details on context engineering, skill files and custom tools.