◉CLAUDE LABJP
●2.1.296 — Subagents can set their own autoCompactWindow, and an env var pins the model used by workflow agents●AGENTS — Managed Agents gain dynamic workflows in beta: an agent can build a run for work with many pieces (Oct 9)●SONNET 4.5 — Retires on the Claude API on 11/30, 50 days left. Migrate to Sonnet 5.5●Q&A — A long-running report: Max plan users hit usage limits almost immediately●HAIKU 5.5 — Code written for Haiku 4.5 hits a 400 error on budget_tokens●NEW — Before you cut an always-loaded instruction file in half, sort it into three drawers●2.1.296 — Subagents can set their own autoCompactWindow, and an env var pins the model used by workflow agents●AGENTS — Managed Agents gain dynamic workflows in beta: an agent can build a run for work with many pieces (Oct 9)●SONNET 4.5 — Retires on the Claude API on 11/30, 50 days left. Migrate to Sonnet 5.5●Q&A — A long-running report: Max plan users hit usage limits almost immediately●HAIKU 5.5 — Code written for Haiku 4.5 hits a 400 error on budget_tokens●NEW — Before you cut an always-loaded instruction file in half, sort it into three drawers
TAG

anthropic-sdk

3 articles
← Back to all tags
Related:
claude-api3tool-use1production1retry1indie-dev1troubleshooting1
⬡ API & SDK/2026-05-26Advanced

Stabilizing Claude API Structured Responses in Production — Notes on tool_use, JSON Schema, and Layered Validation

Getting Claude to return JSON takes a few lines. Keeping that JSON usable in production is a different problem. Here is the layered design I landed on after running a wallpaper classification pipeline through Claude API, built around tool_use, JSON Schema, and domain validation.

⬡ API & SDK/2026-05-23Intermediate

Absorbing the Claude API "Tool Result Submitted" Error in a Retry Layer: A Small Conversation-History Repair

How I absorbed the Claude API "Tool result could not be submitted because the previous turn was not a tool use" error inside a small retry layer, with the diagnosis order I followed after it hit a production batch.

⬡ API & SDK/2026-04-28Intermediate

Why "The requested model does not exist" Won't Go Away — Claude API Naming and Access Pitfalls

The model_not_found error in the Claude API is almost always a typo or a stale model alias — not a permissions issue. Here are the current model IDs as of April 2026 and a clear order for narrowing down the cause.