Only operate on the main branch for this project!!

<pasted_content id="1519"> hi, load the entire context from the D:\Atharva\NOTES projects> neathack folder and understand what we need to do here. We are going to be using opusplan mode and most things will be done with subagents parallely so subagents, sonnet 5.5 medium and this Opus 5.5 Medium

I am Atharva Shah, solo, DevRel. Talk to me in short, plain steps. I have ADHD. Project: FirstRun, for neatHack (kickoff Sat Oct 10 12:30 PM IST, submit Mon Oct 12 at 7:00 PM IST as an X quote post).

MODELS

• This lead session: Opus 5.5, medium effort, opusplan mode.
• Every subagent: Sonnet 5.5, medium effort. Run independent tracks in parallel.
• FirstRun's own runtime model calls: claude-sonnet-5-5, medium, through CLAUDE_CODE_OAUTH_TOKEN. No Anthropic API key. No Bedrock.

WHERE THINGS ARE

• D:\Atharva\firstrun is the product repo. All code goes here and only here.
• plan\ is a junction to D:\Atharva\NOTES\PROJECTS\NeatHack - 10 October. It is gitignored. Never commit it. Never copy its text into this public repo.
• Keys are in D:\Atharva\NOTES.env. Read them at run time. Never print or commit a key.
• Task board: Issues of HighnessAtharva/neathack-prep. Close an issue when its check passes.

ALREADY DONE (12:30 to 13:10 IST, verified)

• entire enable ran before commit 1. The repo is onboarded and mirrored on entire.io (aws-us-east-2).
• Pushed: Entire config, 6 runners in .entire/runners/, Graph and Brain agent instructions.
• Graph plugin and Brain plugin installed. Brain set up with --no-daemon. Watcher does not run on Windows.
• neatlogs SDK is in .venv. The CLI runs as: npx --yes -p node@22 -p neatlogs-cli@0.2.0 -- neatlogs ...
• Docker is in WSL: wsl -d Ubuntu-22.04 docker ...

STILL OPEN (do or tell me)

1. I flip Runners, Trails and Auto build on push in entire.io repo settings. Ask me if Trails is not on before you create one.
2. Run entire trail create for Layer 1 on its branch, after Trails is on.
3. Run entire brain setup refresh once the first sessions land. Run entire graph stats --repo . and save the number.
4. checkpoints are 0 until your first session commit. Run entire status and entire checkpoint list yourself so they land in the transcript.

READ FIRST, in this order

1. plan\07 Rules We Follow.md (F1 to F5)
2. plan\01 Project Plan.md ("The Simple Version Wins")
3. plan\08 FirstRun Spec.md
4. plan\09 Run Sheet.md
5. plan\05 Kickoff Prompts.md (prompts 1 to 7, prompt 6 is cut)
6. plan\19 Parallel Build Plan.md (the seven worker tracks)
7. plan\16 Entire Playbook.md and plan\21 Grading Checklist and Judge Map.md

RULES THAT NEVER BEND

• F5: never cut a use of neatlogs, Entire or cfo.ai. Cut a FirstRun feature first.
• Every commit carries an Entire-Checkpoint trailer.
• Never add a co-author line to a commit.
• Ask me before any push of a public post, and before any PR to another project.
• Log each event in plan\20 Build Log.md, one line each.

FIRST ACTIONS

1. Run entire status, git log and git remote -v. Report in 3 lines.
2. Enter plan mode. Plan Layer 1 from the spec. Split it into parallel Sonnet 5.5 medium subagent tracks per plan\19.
3. Show me the plan. Wait for my yes. Then fire the tracks. </pasted_content id="1519">

Base directory for this skill: C:\Users\ATHARV~1\AppData\Local\Temp\claude\bundled-skills\2.1.295\d2f05c417a9c44494aa5d1f45dc1bf82\claude-api

Building LLM-Powered Applications with Claude

This skill helps you build LLM-powered applications with Claude. Choose the right surface based on your needs, detect the project language, then read the relevant language-specific documentation.

Before You Start

Scan the target file (or, if no target file, the prompt and project) for non-Anthropic provider markers - import openai, from openai, langchain_openai, OpenAI(, gpt-4, gpt-5, file names like agent-openai.py or *-generic.py, or any explicit instruction to keep the code provider-neutral. If you find any, stop and tell the user that this skill produces Claude/Anthropic SDK code; ask whether they want to switch the file to Claude or want a non-Claude implementation. Do not edit a non-Anthropic file with Anthropic SDK calls. (Exception: the prompt-audit subcommand is non-interactive and does not stop here - it records non-Anthropic provider markers in its report's stated assumptions and never proposes switching a non-Anthropic file to the Anthropic SDK.)

Output Requirement

When the user asks you to add, modify, or implement a Claude feature, your code must call Claude through one of:

1. The official Anthropic SDK for the project's language (anthropic, @anthropic-ai/sdk, com.anthropic.*, etc.). This is the default whenever a supported SDK exists for the project.
2. Raw HTTP (curl, requests, fetch, httpx, etc.) - only when the user explicitly asks for cURL/REST/raw HTTP, the project is a shell/cURL project, or the language has no official SDK.

Never mix the two - don't reach for requests/fetch in a Python or TypeScript project just because it feels lighter. Never fall back to OpenAI-compatible shims.

Never guess SDK usage. Function names, class names, namespaces, method signatures, and import paths must come from explicit documentation - either the {lang}/ files in this skill or the official SDK repositories or documentation links listed in shared/live-sources.md. If the binding you need is not explicitly documented in the skill files, WebFetch the relevant SDK repo from shared/live-sources.md before writing code. Do not infer Ruby/Java/Go/PHP/C# APIs from cURL shapes or from another language's SDK.

If WebFetch or repository access fails (network restricted, timeouts, clone blocked): do not keep retrying - write code from the patterns and namespace/package tables in the {lang}/ file, run the compiler or interpreter on it, and iterate on the error output. For statically-typed SDKs (C#, Java, Go) a compile-fix loop against local errors reaches working code faster than blocked network research.

Defaults

Unless the user requests otherwise:

For the Claude model version, please use Claude Opus 5.5, which you can access via the exact model string claude-opus-5-5. Please default to using adaptive thinking (thinking: {type: "adaptive"}) for anything remotely complicated. And finally, please default to streaming for any request that may involve long input, long output, or high max_tokens - it prevents hitting request timeouts. Use the SDK's .get_final_message() / .finalMessage() helper to get the complete response if you don't need to handle individual stream events. When a streaming request defines user-defined (client) tools, set eager_input_streaming: true on each of those tools so large tool inputs (file contents, code, documents) stream as they are generated instead of arriving in one burst after the server finishes buffering them; the client then owns validation: the SDKs' tolerant parsers can return a silently truncated input instead of raising, so validate each parsed tool input against its schema before running it (the typed runner helpers such as betaZodTool / typed @beta_tool do this; betaTool() JSON-Schema tools and manual loops must validate themselves), treat a failure like invalid JSON (INVALID_JSON error tool_result when you hold the block, re-issue otherwise), check max_tokens / refusal stop reasons before running tools, and catch only the SDK's JSON error, never its typed API errors - pattern in shared/tool-use-concepts.md -> Eager input streaming. Leave it off for non-streaming requests, for server tools, and when the request goes through a proxy or an older Bedrock model deployment that rejects the field.

Warning: API Drift - Your Training Prior May Be Stale

Several common Claude API shapes changed in 2025-2026. If you recall a pattern from training, verify it against the {lang}/ files in this skill before writing - the rows below are the most frequent drift points:

The {lang}/ files in this skill are authoritative over recalled patterns.

Subcommands

If the User Request at the bottom of this prompt is a bare subcommand string (no prose), search every Subcommands table in this document - including any in sections appended below - and follow the matching Action column directly. This lets users invoke specific flows via /claude-api <subcommand>. If no table in the document matches, treat the request as normal prose.

Language Detection

Before reading code examples, determine which language the user is working in (exception: for the prompt-audit subcommand, skip this section's ask steps - the audit is non-interactive and its inventory is language-agnostic; when no language is inferable, proceed without asking and state the assumption in the report):

1. Look at project files to infer the language:

• *.py, requirements.txt, pyproject.toml, setup.py, Pipfile -> Python - read from python/
• *.ts, *.tsx, package.json, tsconfig.json -> TypeScript - read from typescript/
• *.js, *.jsx (no .ts files present) -> TypeScript - JS uses the same SDK, read from typescript/
• *.java, pom.xml, build.gradle -> Java - read from java/
• *.kt, *.kts, build.gradle.kts -> Java - Kotlin uses the Java SDK, read from java/
• *.scala, build.sbt -> Java - Scala uses the Java SDK, read from java/
• *.go, go.mod -> Go - read from go/
• *.rb, Gemfile -> Ruby - read from ruby/
• *.cs, *.csproj -> C# - read from csharp/
• *.php, composer.json -> PHP - read from php/

1. If multiple languages detected (e.g., both Python and TypeScript files):

• Check which language the user's current file or question relates to
• If still ambiguous, ask: "I detected both Python and TypeScript files. Which language are you using for the Claude API integration?"

1. If language can't be inferred (empty project, no source files, or unsupported language):

• Use AskUserQuestion with options: Python, TypeScript, Java, Go, Ruby, cURL/raw HTTP, C#, PHP
• If AskUserQuestion is unavailable, default to Python examples and note: "Showing Python examples. Let me know if you need a different language."

1. If unsupported language detected (Rust, Swift, C++, Elixir, etc.):

• Suggest cURL/raw HTTP examples from curl/ and note that community SDKs may exist
• Offer to show Python or TypeScript examples as reference implementations

1. If user needs cURL/raw HTTP examples, read from curl/.

Language-Specific Feature Support

Every SDK language above supports both the beta Tool Runner and Managed Agents (beta) - Python (@beta_tool decorator), TypeScript (betaZodTool + Zod), Java (annotated classes), Go (BetaToolRunner in the toolrunner pkg), Ruby (BaseTool + tool_runner), C# (BetaToolRunner + raw JSON schema), PHP (BetaRunnableTool + toolRunner()); code entry points are in the Tool Use Patterns quick reference below. cURL is raw HTTP (no SDK features) and supports Managed Agents.

Managed Agents code examples: see the reading guide in the ## Managed Agents (Beta) section below.

Which Surface Should I Use?

Start simple. Default to the simplest tier that meets your needs. Single API calls and workflows handle most use cases - only reach for agents when the task genuinely requires open-ended, model-driven exploration. "Simplest" means the least code you own: for a hosted, scheduled, or memory-backed agent, Managed Agents is usually the simplest option (no loop code, no state files, no scheduler), even though it's a bigger platform.

Note: Managed Agents is the right choice when you want Anthropic to run the agent loop and host the container where tools execute - file ops, bash, code execution all run in the per-session workspace. If you want to host the compute yourself or run your own custom tool runtime, Claude API + tool use is the right choice - use the tool runner for the agentic loop - its per-turn hooks still give you approval gates, logging, error interception, and conditional execution (see shared/tool-use-concepts.md) - or the manual loop when you want to own the entire loop yourself.

Cloud-provider access. Claude Platform on AWS is Anthropic-operated with same-day API parity - see shared/claude-platform-on-aws.md for client setup. For per-feature availability on Claude Platform on AWS, Amazon Bedrock, Google Vertex AI, and Microsoft Foundry, see shared/platform-availability.md - that table is the single source of truth in this skill; do not infer availability from anywhere else.

Building an Agent: Four Approaches

Once you've decided you actually need an agent (open-ended, model-driven tool use), there are four distinct ways to build one. Two independent questions separate them: who supplies the harness (the agent loop + context management) and who supplies the deployment (the infra the agent runs on). The Tool Runner and the Claude Agent SDK both supply a harness only - you still host and deploy them yourself - which is why they're easy to conflate. Managed Agents (CMA) is the only option that supplies both the harness and managed deployment; the manual loop supplies neither.

The harness/deployment split is the key mental model: options 1, 2, and 4 all leave deployment to you; only option 3 (CMA) adds managed deployment. Options 1-3 are what this skill generates; option 4 is a different library with its own docs - see the disambiguation below.

Tool Runner != Claude Agent SDK. These sound alike but are different packages:

• Tool Runner is part of the regular Anthropic API SDK (anthropic / @anthropic-ai/sdk), reached via client.beta.messages.tool_runner. It automates the request -> execute -> loop cycle for tools you define. No built-in tools, no filesystem access, no sandbox - you supply every tool and host the compute. It is option 2 above, a thin helper over POST /v1/messages.
• Claude Agent SDK (claude-agent-sdk / @anthropic-ai/claude-agent-sdk) is Claude Code packaged as a library. It ships built-in tools (file read/write/edit, bash, grep, web search), the full agent loop, context management, hooks, subagents, permissions, and sessions. You call query(prompt, options) and it drives everything.

Both are harness-only - you host and deploy them. The difference is scope of harness: the Tool Runner loops over tools you define (with per-turn hooks for approval, interception, result modification, and retries - but no built-in tools); the Agent SDK is the full Claude Code harness with built-in tools. Neither provides managed deployment - that's what Managed Agents (CMA) adds (Anthropic hosts the loop and a per-session sandbox).

This skill covers the Claude API and Managed Agents (options 1-3); it does not generate Claude Agent SDK code. If the user actually wants the Claude Agent SDK, point them to its docs (code.claude.com/docs/en/agent-sdk) - don't substitute the API Tool Runner for it, or vice-versa.

Should I Build an Agent?

Before choosing the agent tier, check all four criteria:

• Complexity - Is the task multi-step and hard to fully specify in advance? (e.g., "turn this design doc into a PR" vs. "extract the title from this PDF")
• Value - Does the outcome justify higher cost and latency?
• Viability - Is Claude capable at this task type?
• Cost of error - Can errors be caught and recovered from? (tests, review, rollback)

If the answer is "no" to any of these, stay at a simpler tier (single call or workflow).

Architecture

Everything goes through POST /v1/messages. Tools and output constraints are features of this single endpoint - not separate APIs.

User-defined tools - You define tools (via decorators, Zod schemas, or raw JSON), and the SDK's tool runner handles calling the API, executing your functions, and looping until Claude is done. For full control, you can write the loop manually.

Server-side tools - Anthropic-hosted tools that run on Anthropic's infrastructure. Code execution is fully server-side (declare it in tools, Claude runs code automatically). Computer use can be server-hosted or self-hosted.

Structured outputs - Constrains the Messages API response format (output_config.format) and/or tool parameter validation (strict: true). The recommended approach is client.messages.parse() which validates responses against your schema automatically. Note: the old output_format parameter is deprecated; use output_config: {format: {...}} on messages.create().

Supporting endpoints - Batches (POST /v1/messages/batches), Files (POST /v1/files), Token Counting (POST /v1/messages/count_tokens - see shared/token-counting.md), and Models (GET /v1/models, GET /v1/models/{id} - live capability/context-window discovery) feed into or support Messages API requests.

Current Models (cached: 2026-10-06)

Partner pricing: The prices above are Anthropic first-party API rates - they also apply to Claude on Microsoft Foundry, which is billed through the Microsoft Marketplace at standard API rates. Claude on Amazon Bedrock and Vertex AI is partner-operated with separate pricing - see Bedrock or Vertex AI. For WebFetch, use the Pricing row in shared/live-sources.md.

ALWAYS use claude-opus-5-5 unless the user explicitly names a different model. This is non-negotiable. Do not use claude-sonnet-5-5, claude-sonnet-5, or any other model unless the user literally says "use sonnet" or "use haiku". Never downgrade for cost - that's the user's decision, not yours. A request that describes a Sonnet by attribute ("cheapest Sonnet", "cheaper Sonnet", "newest Sonnet", "latest Sonnet") resolves to claude-sonnet-5-5. Where a second, cheaper model is in play alongside the main one (worker or sub-agent threads, bulk extractors, LLM judges, the executor under an advisor) - because the user asked for one or a guide in this skill calls for it - or the user says "sonnet" or "haiku" without a version, that means the current generation from the table above (claude-sonnet-5-5, claude-haiku-5-5); previous-generation IDs such as claude-sonnet-5 are only for users who name that version. Use claude-fable-5-1 only when the user explicitly asks for Claude Fable 5.1, "fable", or Anthropic's most capable model - it has different API behavior than the Opus family (see below) and pricing that exceeds Opus-tier. Use only the exact model ID strings from the table - they are complete as-is; never append date suffixes (claude-opus-5-5, never claude-opus-5-5-20260401 or any other date-suffixed variant you might recall from training data). If the user requests an older model not in the table (e.g., "opus 4.5", "sonnet 3.7"), read shared/models.md for the exact ID - do not construct one yourself.

Claude Fable 5.1 (claude-fable-5-1) - most capable widely released model

Claude Fable 5.1 is Anthropic's most capable widely released model, for the most demanding reasoning and long-horizon agentic work; everything below also applies to Claude Mythos 5.1 (claude-mythos-5-1, Project Glasswing - same capabilities, pricing, and API surface; it runs safeguards that depend on the access program, so the refusal handling below applies there too; successor to Claude Mythos 5, which ran no safety classifiers). 1M context window (the maximum is also the default), 128K max output. Key API differences from Opus-tier - see shared/model-migration.md -> Migrating to Claude Fable 5.1 for details:

• Thinking is always on - omit the thinking parameter entirely (or send {type: "adaptive"}). Any other explicit configuration is rejected: {type: "disabled"} and {type: "enabled", budget_tokens: N} both return a 400. Control depth with output_config.effort (supports low through xhigh and max).
• The raw chain of thought is never returned - responses carry regular thinking blocks (not redacted_thinking): display: "summarized" returns a readable summary, "omitted" (the default) leaves the thinking field as an empty string. Replay rules: pass thinking blocks back unchanged on the same model; other models drop them silently (unbilled - nothing to strip; Claude Mythos 5.1 instead reads them); details in shared/model-migration.md.
• Tokenizer - same tokenizer as Opus 4.8 (introduced with Opus 4.7). Token counts are roughly unchanged when migrating from Opus 4.7/4.8; per-token pricing differs. Coming from Opus 4.6, Sonnet, Haiku, or older, re-baseline with count_tokens (the Opus 4.7 tokenizer uses ~1×-1.35× as many tokens).
• refusal stop reason - handle it, and opt into fallbacks by default - safety classifiers may decline a request (HTTP 200, stop_reason: "refusal", with a stop_details category); always check stop_reason before reading content. When you write claude-fable-5-1, claude-opus-5-5, claude-opus-5, or claude-sonnet-5-5 code, include the server-side fallbacks parameter by default (for claude-sonnet-5-5, only the "default" form and only on the Claude API; on other platforms use the SDK middleware below, except when the request sends between_tools: only Claude Sonnet 5.5 accepts it and the middleware re-sends the same request body on the fallback model, so write the retry yourself and send it without between_tools - see shared/model-migration.md -> Migrating to Claude Sonnet 5.5 -> Safeguards and fallback). Simplest form: betas: ["server-side-fallback-2026-07-01"] + fallbacks: "default", which routes by refusal category so you never maintain a model list. (The older array form - betas: ["server-side-fallback-2026-06-01"] + fallbacks: [{"model": "claude-opus-4-8"}] - still works; Claude API and Claude Platform on AWS - on Bedrock, Vertex and Foundry, use the SDKs' client-side BetaRefusalFallbackMiddleware + BetaFallbackState). Tell the user you've enabled it; drop it only if they decline. Full semantics (billing, mid-stream refusals, credit repricing) in shared/model-migration.md -> refusal section. Per-language code examples in {lang}/claude-api/README.md § Refusal Fallbacks cover the array form only - for the "default" mode, follow the raw-HTTP shape in shared/model-migration.md -> Migrating to Claude Opus 5 -> New API features and swap fallbacks: [{...}] for fallbacks: "default" plus the -2026-07-01 header; the rest of the request is unchanged.
• No assistant prefill - same as the rest of the 4.6+ family.
• 30-day data retention required - Claude Fable 5.1 is not available under zero data retention unless expressly authorized by Anthropic; requests from an org whose retention configuration doesn't meet the requirement return 400 invalid_request_error.
• Longer turns, different prompting - single requests on hard tasks can run many minutes (plan timeouts/streaming/progress UX); effort sweeps should include low/medium for routine work; prompts written for prior models are often too prescriptive and reduce output quality. See shared/model-migration.md -> Migrating to Claude Fable 5.1 -> Behavioral shifts (prompt-tunable) for the recommended prompt snippets.
• Successor to Claude Fable 5 (claude-fable-5, still served) in the same tier at the same per-token price. Same surface as Claude Fable 5 with three breaking changes - forced tool use (tool_choice any / tool) returns a 400 (use auto + a prompt instruction, strict: true for schema-valid arguments, or structured outputs); thinking blocks are bound to the producing model (other models drop them, unbilled); and editing earlier turns invalidates thinking blocks ("preserved thinking"; new accounts created on/after 2026-08-31 get a 400 on edited history on every platform, and enforcement scope is decided per model, and Claude Mythos 5.1 doesn't run this check. Make every harness append-only and run the three-step check; the opt-in controls beta is on the Claude API, Claude Platform on AWS, Bedrock, and Vertex - Foundry unconfirmed, see shared/platform-availability.md) - plus per-message effort (beta mid-conversation-output-config-2026-07-01, also on Claude Opus 5 and Claude Opus 5.5), turn-scoped clear_at: "next_user_message" system messages (beta), thinking.display: "updates" progress notes (beta, all platforms), cache reads at $0.25/MTok, and content provenance. Covered Model - ZDR orgs get 400 invalid_request_error as on Claude Fable 5 (ZDR only if expressly authorized by Anthropic); no Priority Tier. Same tokenizer as Claude Fable 5. See shared/model-migration.md -> Migrating to Claude Fable 5.1 from Claude Fable 5.

Claude Opus 5.5 (claude-opus-5-5) - the current Opus and the default model

Successor to Claude Opus 5 in the Opus line at a lower price ($4 / $20 per MTok, cache reads $0.20), same 1M context / 128K output / tokenizer / feature set. Four breaking changes for code running on Claude Opus 5: thinking can't be disabled ({type: "disabled"} and budget_tokens both 400 at every effort level - effort is the only control, and its default is medium, one level below Claude Opus 5's high, so set it explicitly); forced tool_choice any/tool returns a 400 (use auto + strict: true and steer from the prompt, or structured outputs); thinking blocks are tied to the model and the conversation (preserved thinking: only Claude Fable 5.1 / Claude Mythos 5.1 on the Claude API read its blocks, so a fallback to Claude Opus 5 runs without them; accounts created on or after 2026-08-31 are enforced on the history-editing check); and on the Claude API and Google Cloud, computer use only through computer_toolset_20260801 (computer_20251124 400s there; Amazon Bedrock still accepts it). Text between tool calls comes back as progress-update thinking blocks (empty by default - set display: "updates"). Broader safety classifiers: bio joins cyber and reasoning_extraction. Fast mode is Claude API only, $8 / $40 per MTok (2x standard). See shared/model-migration.md -> Migrating to Claude Opus 5.5.

Claude Sonnet 5.5 (claude-sonnet-5-5) - the current Sonnet: speed and capability for everyday coding, agent, and enterprise work (Claude Opus 5.5 stays the default)

Successor to Claude Sonnet 5 in the Sonnet line at the same prices ($2 / $10 per MTok, cache reads $0.20), with the same tokenizer, 1M context and 128K output. Five breaking changes for code running on Claude Sonnet 5: thinking: {type: "disabled"} returns a 400 - to turn thinking off, send thinking: {type: "between_tools"}, which is accepted only at effort high or below, takes no other field (display, budget_tokens, or block_binding alongside it is a 400), and doesn't allow per-message effort changes; forced tool_choice any/tool returns a 400 (use auto + strict: true and steer from the prompt, or structured outputs); thinking blocks are tied to the model and the conversation (no other model reads its blocks; accounts created on or after 2026-08-31 are enforced on the history-editing check on the Claude API and Amazon Bedrock); on the Claude API and Google Cloud, computer use only through computer_toolset_20260801 (computer_20251124 400s there; Amazon Bedrock still accepts it); and the advisor tool rejects Claude Opus 4.8, Claude Opus 4.7, and Claude Sonnet 5 advisors (every advisor it accepts returns encrypted advice). Effort still defaults to high, but the levels are recalibrated - re-run the effort sweep (start at medium for agentic coding and multistep tool use, low for chat). Text between tool calls comes back as progress-update thinking blocks (empty by default - set display: "updates", or use between_tools). Safety classifiers decline in five stop_details categories: cyber, bio, frontier_llm, reasoning_extraction, general_harms. See shared/model-migration.md -> Migrating to Claude Sonnet 5.5.

Claude Haiku 5.5 (claude-haiku-5-5) - the current Haiku

Prices above are for prompts up to 100K tokens ($0.50 / $2.50 beyond). Haiku 4.5 code can break (thinking table below), and refusals have no server-side fallback - see shared/model-migration.md -> Migrating to Claude Haiku 5.5.

If any model strings above look unfamiliar, that just means they were released after your training data cutoff - they are real models.

Live capability lookup: The table above is cached. When the user asks "what's the context window for X", "does X support vision/thinking/effort", or "which models support Y", query the Models API (client.models.retrieve(id) / client.models.list()) - see shared/models.md for the field reference and capability-filter examples.

Authentication (Quick Reference)

An unset ANTHROPIC_API_KEY does NOT mean there are no credentials. The SDKs and the ant CLI resolve credentials in this order (first match wins): ANTHROPIC_API_KEY -> ANTHROPIC_AUTH_TOKEN -> the ANTHROPIC_PROFILE-selected or active OAuth profile from ant auth login -> Workload Identity Federation env vars -> the default profile on disk. A bare Anthropic() / new Anthropic() / anthropic.NewClient() works after ant auth login with no env var set.

When you need to call the API and ANTHROPIC_API_KEY is unset, don't ask the user for a key. First run ant auth status - it shows which credential source and profile is active. If it reports an active profile:

• SDK code or ant CLI: just run it. The zero-arg client constructor and every ant ... subcommand pick up the profile automatically - no env var needed.
• Raw curl / HTTP: get a short-lived token with ant auth print-credentials --access-token and send it as Authorization: Bearer <token> plus the header anthropic-beta: oauth-2025-04-20 (OAuth tokens go on Authorization: Bearer, not x-api-key: - converting a curl from an API key is a header change, not a key swap). Always pass --access-token; the no-flag form prints JSON, not a bare token.

Only ask the user for a key if ant auth status reports no active credential source (or ant itself isn't installed). Suggest ant auth login as the first option - it stores a profile under ~/.config/anthropic/ that the SDKs read automatically - and an exported ANTHROPIC_API_KEY as the alternative.

Full auth details (named profiles, scopes, the API-key-shadows-profile trap, refresh-token expiry): shared/anthropic-cli.md.

Thinking & Effort (Quick Reference)

Use adaptive thinking (thinking: {type: "adaptive"}) on every current model except Haiku 4.5, which still takes budget_tokens (table below) - Claude dynamically decides when and how much to think. Per-model rules:

Opus 4.8 keeps 4.7's request surface - see shared/model-migration.md -> Migrating to Opus 4.8 (and -> Migrating to Opus 4.7 from 4.6 or earlier). With thinking disabled, Opus 4.8 may write longer reasoning into the visible response - leave adaptive thinking on, or add a final-answer-only instruction.

• Effort (GA, no beta header): output_config: {effort: "low"|"medium"|"high"|"xhigh"|"max"} - inside output_config, not top-level; default high (equivalent to omitting it) on every current model except Claude Opus 5.5 and Claude Haiku 5.5, whose default is medium (thinking table above) - set it explicitly there. Controls thinking depth and overall token spend; combine with adaptive thinking for the best cost-quality tradeoffs. xhigh (added on Opus 4.7, between high and max) is the best setting for most coding and agentic use cases on Fable 5 / Opus 4.7/4.8 / Sonnet 5, and the default in Claude Code; effort matters more on those models than on any prior model in their tier - re-tune it when migrating, and run long-horizon/agentic tasks at high/xhigh with the full task spec given up front. Use a minimum of high for intelligence-sensitive work, max when correctness matters more than cost, and low for subagents or simple tasks - lower effort means fewer and more-consolidated tool calls, less preamble, and terser confirmations (high is often the sweet spot balancing quality and token efficiency).
• Choosing an effort level (cost tuning): Effort is the first quality-trading lever, after the free wins (caching first) - it trades thoroughness against token spend within one model, and the top of the range earns its cost only on hard problems (raise to max only when measurement shows headroom at the level below). Which workloads repay higher effort is a property of the workload: coding and long-horizon agentic work respond strongly; chat, classification, and high-volume or latency-sensitive routes often don't and do well at low, with medium as the cost-saving step-down where quality holds (the per-level defaults above cover the rest). Measure on a sample of real requests before raising a default, and tune per route rather than globally. Before building a multi-model cost cascade, measure the simpler alternative first - the most capable model at lower effort on the same tasks: lower effort on the newest models often matches or exceeds prior-generation performance at high effort (on Fable 5, lower effort often exceeds xhigh on prior models), and one model means one cache namespace (caches are model-scoped, so a cascade forfeits cache reuse across its models; a mid-conversation top-level effort change still invalidates the messages cache, though the per-message effort system message avoids that on Claude Fable 5.1 / Claude Mythos 5.1 / Claude Opus 5.5 / Claude Opus 5 / Claude Sonnet 5.5 / Claude Haiku 5.5 (with adaptive thinking) - shared/prompt-caching.md § Invalidation hierarchy). Judge cost per completed task, not per request - a cheaper request that needs more turns or retries to finish the job isn't cheaper. For the measured effort/cost tradeoffs by workload and the full lever order, shared/cost-optimization.md § 2.6.
• Thinking display - "omitted" by default on Fable 5 / Claude Fable 5.1 / Mythos 5 / Claude Mythos 5.1 / Opus 5.5 / 5 / 4.8 / 4.7 / Sonnet 5 / Claude Sonnet 5.5 / Claude Haiku 5.5: display: "summarized" returns a readable summary of the reasoning; "omitted" (the default on all eleven - a silent change from Opus 4.6 and Sonnet 4.6, where it was "summarized") streams thinking blocks with empty text. display controls visibility only - thinking happens and is billed the same under every setting; the raw chain of thought is never exposed on any model. If you stream reasoning to users, the default looks like a long pause before output - set thinking: {type: "adaptive", display: "summarized"} explicitly. (Independent of display, echo thinking blocks back unchanged when continuing on the same model; other models silently ignore them (Claude Fable 5.1 / Claude Mythos 5.1 read them, and Claude Sonnet 5.5 reads Claude Sonnet 5, Opus 4.8, Claude Haiku 5.5 / Haiku 4.5, and earlier models' blocks) - see the migration guide.) On Claude Fable 5.1 / Claude Mythos 5.1 / Claude Fable 5 / Claude Opus 5.5 / Claude Sonnet 5.5, display: "updates" (beta thinking-display-updates-2026-08-18, every platform) hides reasoning like "omitted" but returns the model's between-tool-call progress notes as short thinking block summaries - see shared/model-migration.md -> Migrating to Claude Fable 5.1 from Claude Fable 5 -> New API features.
• When the user asks for "extended thinking", a "thinking budget", or budget_tokens: always use Fable 5/5.1, Opus 5.5, 5, 4.8, 4.7, or 4.6 with thinking: {type: "adaptive"} - the fixed thinking-token-budget concept is deprecated and adaptive thinking replaces it. Do NOT use budget_tokens for new 4.6/4.7/4.8 code and do NOT switch to an older model just because the user mentions it. Gradual-migration carve-out: budget_tokens is still functional on Opus 4.6 and Sonnet 4.6 only, as a transitional escape hatch for existing code that needs a hard token ceiling before you've tuned effort - see shared/model-migration.md -> Transitional escape hatch. It is fully removed on Fable 5/5.1, Opus 5.5/5/4.7/4.8, Sonnet 5.5/5, and Haiku 5.5.

Compaction (Quick Reference)

Beta, Fable 5/5.1, Opus 5.5, Opus 5, Opus 4.8, Opus 4.7, Opus 4.6, Sonnet 5.5, Sonnet 5, Sonnet 4.6, and Claude Haiku 5.5. For long-running conversations that may exceed the 1M context window, enable server-side compaction. The API automatically summarizes earlier context when it approaches the trigger threshold (default: 150K tokens). Requires beta header compact-2026-01-12.

Critical: Append response.content (not just the text) back to your messages on every turn. Compaction blocks in the response must be preserved - the API uses them to replace the compacted history on the next request. Extracting only the text string and appending that will silently lose the compaction state.

See {lang}/claude-api/README.md (Compaction section) for code examples. Full docs via WebFetch in shared/live-sources.md.

Prompt Caching (Quick Reference)

Prefix match. Any byte change anywhere in the prefix invalidates everything after it. Render order is tools -> system -> messages. Keep stable content first (frozen system prompt, deterministic tool list), put volatile content (timestamps, per-request IDs, varying questions) after the last cache_control breakpoint.

Mid-conversation operator instructions (Claude Opus 5, Claude Opus 5.5, Claude Opus 4.8, Claude Fable 5, Claude Fable 5.1, Claude Mythos 5, Claude Mythos 5.1, Claude Sonnet 5.5; not Claude Sonnet 5; no beta header): append {"role": "system", ...} to messages[] instead of editing top-level system. Preserves the cached history prefix and is the prompt-injection-safe operator channel. See shared/prompt-caching.md § Mid-conversation system messages.

Top-level auto-caching (cache_control: {type: "ephemeral"} on messages.create()) is the simplest option when you don't need fine-grained placement. Max 4 breakpoints per request. Minimum cacheable prefix is model-dependent (512-4096 tokens - see shared/prompt-caching.md § API reference) - shorter prefixes silently won't cache.

Verify with usage.cache_read_input_tokens - if it's zero across repeated requests, a silent invalidator is at work (datetime.now() in system prompt, unsorted JSON, varying tool set).

For placement patterns, architectural guidance, and the silent-invalidator audit checklist: read shared/prompt-caching.md. Language-specific syntax: {lang}/claude-api/README.md (Prompt Caching section).

Fast Mode (Quick Reference)

Research preview, Claude Opus 5 / Claude Opus 5.5 / Opus 4.8 only - Claude API and Managed Agents, not Bedrock / Google Cloud / Foundry. Opus 4.7 fast mode has been removed: speed: "fast" on 4.7 returns an error. Fast mode on Claude Opus 5 is priced at $10 / $50 per MTok; on Claude Opus 5.5, $8 / $40. Fast mode runs the same model at up to 2.5x higher output tokens per second, at premium pricing. Three things are required on every request: use the beta messages endpoint (client.beta.messages....), pass the beta flag fast-mode-2026-02-01, and set speed: "fast" as a top-level request parameter (not a header, not in extra_body).

response.usage.speed reports which speed was used. Fast mode has its own rate limit separate from standard Opus; on 429, either retry after the retry-after delay or drop speed and fall back to standard (note: switching speed invalidates prompt cache). Not available with Batch API, Priority Tier, Claude Platform on AWS, or third-party platforms.

Priority Tier is not supported on every current model. It is supported on Claude Fable 5, Opus 4.8, and the older current models, but Claude Opus 5.5, Claude Opus 5, Claude Sonnet 5, Claude Sonnet 5.5, Claude Fable 5.1, Claude Mythos 5.1, Claude Mythos 5, and Mythos Preview are excluded - a Priority Tier request naming one of them fails validation.

Task Budgets (Quick Reference)

Beta, Claude Opus 5 / Claude Opus 5.5 / Fable 5 / Claude Fable 5.1 (confirm at launch) / Claude Sonnet 5.5 / Claude Haiku 5.5 / Opus 4.8 / 4.7 (not Claude Sonnet 5). A task budget gives Claude a token ceiling for an agentic loop so it paces itself and finishes gracefully instead of being cut off - distinct from max_tokens, which is an enforced per-response ceiling the model is not aware of. Minimum total: 20,000. Set task_budget inside output_config on client.beta.messages.stream(...) with beta flag task-budgets-2026-03-13 - use streaming so the large max_tokens doesn't hit HTTP timeouts (full details: shared/model-migration.md -> Task Budgets):

task_budget fields: type (always "tokens"), total, and optional remaining (defaults to total). The server injects a countdown marker Claude sees during generation; the budget counts what Claude generates and the tool results it reads this turn - not the full history you resend each request. Not the same thing as Managed Agents session budgets - those are hard, dollar-denominated, platform-enforced caps on one CMA session (shared/managed-agents-core.md § Session budgets); a task budget is advisory and token-denominated.

Observing spend: accumulate response.usage.output_tokens (plus the token count of the tool-result blocks you append) across loop iterations if you want to display progress. Leave remaining unset in the normal loop - the server tracks the countdown itself, and passing a client-computed remaining while also resending full history under-reports the budget. Only pass remaining when you compact or rewrite history between requests and the server can no longer derive prior spend.

Provider Clients (Quick Reference)

When targeting Claude on a third-party platform, use that platform's dedicated client class - not the first-party Anthropic() client with a base_url override. After construction the client exposes the same messages.create / .stream surface as the first-party SDK.

Amazon Bedrock

Use the Mantle client (Messages-API Bedrock endpoint). Bedrock model IDs take an anthropic. prefix (e.g. "anthropic.claude-opus-5-5"). Region is required.

AnthropicBedrock / BedrockClient / BedrockBackend (without Mantle) are the legacy bedrock-runtime InvokeModel path - prefer the Mantle client for new code.

Microsoft Foundry

The Go and Ruby SDKs do not currently support Foundry. For Ruby, use the standard Anthropic::Client.new(base_url: "<foundry endpoint>") as a fallback (Entra ID auth is not built in). For Claude Platform on AWS, see shared/claude-platform-on-aws.md.

Google Cloud Vertex AI

Two required constructor args: GCP project_id and region. Vertex model IDs take no prefix - current-generation models (Opus 5.5/5/4.8/4.7/4.6, Sonnet 5.5, Sonnet 5, Sonnet 4.6) use the bare first-party ID (e.g. "claude-opus-5-5"); dated-snapshot models use an @ version separator (e.g. claude-opus-4-5@20251101, not claude-opus-4-5-20251101). Auth is GCP ADC (gcloud auth application-default login); no Anthropic API key. region can be "global" (recommended), a multi-region ("us"/"eu"), or a specific region. After construction, use the same messages.create / .stream surface.

Context Editing (Quick Reference)

Beta. Context editing clears old tool results or thinking blocks from the conversation before the model sees it; it is not compaction (which summarizes). On client.beta.messages.* with beta context-management-2025-06-27, pass context_management.edits with a strategy type:

Strategy types: clear_tool_uses_20250919 (clears old tool results; optional clear_tool_inputs: true also clears the tool_use params) and clear_thinking_20251015 (clears thinking blocks). Do not use compact_20260112 or beta compact-2026-01-12 - those are the separate compaction feature.

Mid-Conversation System Messages (Quick Reference)

Claude Opus 5, Claude Opus 5.5, Claude Opus 4.8, Claude Fable 5, Claude Fable 5.1, Claude Mythos 5, Claude Mythos 5.1, Claude Sonnet 5.5, and Claude Haiku 5.5; not Claude Sonnet 5; no beta header. Append {"role": "system", "content": "..."} to the messages array (not the top-level system field) to add an operator instruction mid-conversation without invalidating the cached prefix. Use the regular client.messages.create - there is no beta. A mid-conversation system message must follow a user message (or an assistant message ending in server-tool use), and must be either the last entry in messages or be followed by an assistant turn - it cannot be messages[0]. Availability: shared/platform-availability.md. See shared/prompt-caching.md § Mid-conversation system messages. A beta extension shipped with Claude Fable 5.1: output_config: {effort: ...} with content: [] changes effort from that point on without a cache reset (beta mid-conversation-output-config-2026-07-01; Claude Fable 5.1, Claude Mythos 5.1, Claude Opus 5.5, Claude Opus 5, Claude Sonnet 5.5, and Claude Haiku 5.5 with thinking on; Claude API and Google Cloud). An effort-only message (empty content) is exempt from the placement rules above - it can sit anywhere in messages, including first or between an assistant turn and the next user turn; the rules apply to text and clear_at messages. For a per-turn reminder, give the message clear_at: "next_user_message" (beta mid-conversation-system-clear-at-2026-08-21): it renders for one turn, then stays in the transcript cleared - never delete earlier copies (on Claude Fable 5.1, Claude Opus 5.5, Claude Sonnet 5.5, and Claude Haiku 5.5 deleting one invalidates later thinking blocks); without the beta, a text block after the tool results, earlier copies kept. See shared/model-migration.md -> Migrating to Claude Fable 5.1 from Claude Fable 5 -> New API features.

Managed Agents (Beta)

Managed Agents is a third surface: server-managed stateful agents with Anthropic-hosted tool execution. You create a persisted, versioned Agent config (POST /v1/agents), then start Sessions that reference it. Each session provisions a container as the agent's workspace - bash, file ops, and code execution run there; the agent loop itself runs on Anthropic's orchestration layer and acts on the container via tools. The session streams events; you send messages and tool results back.

Availability: shared/platform-availability.md. For agents on Bedrock / Vertex / Foundry (where Managed Agents is unsupported), use Claude API + tool use.

Mandatory flow: Agent (once) -> Session (every run). model/system/tools live on the agent, never the session. See shared/managed-agents-overview.md for the full reading guide, beta headers, and pitfalls.

Beta headers: managed-agents-2026-04-01 - the SDK sets this automatically for all client.beta.{agents,environments,sessions,vaults,deployments,deployment_runs}.* calls. Memory stores use agent-memory-2026-07-22 instead, which the SDK sets on client.beta.memory_stores.* calls; sending both headers on a memory store request returns a 400. Files API and Skills API are out of beta - no beta header needed (see the API Drift table above for the migration guides).

Subcommands - invoke directly with /claude-api <subcommand>:

Reading guide: Start with shared/managed-agents-overview.md, then the topical shared/managed-agents-*.md files (core, environments, tools, events, outcomes, multiagent, webhooks, memory, scheduled-deployments, client-patterns, onboarding, onboarding-from-quickstart, onboarding-from-url, api-reference). For Python, TypeScript, Go, Ruby, PHP, and Java, read {lang}/managed-agents/README.md for code examples. For cURL, read curl/managed-agents.md. Agents are persistent - create once, reference by ID. Define agents and environments as version-controlled files synced with ant apply - this is the recommended flow (see shared/anthropic-cli.md): the CLI owns the control plane (creating and updating agents), your code owns the data plane (sessions.create with the stored agent ID). Call agents.create() in code only when you must provision programmatically; either way, store the returned agent ID and pass it to every subsequent sessions.create; never call agents.create() in the request path. If a binding you need isn't shown in the language README, WebFetch the relevant entry from shared/live-sources.md rather than guess. C# has beta Managed Agents support via client.Beta.Agents and related namespaces - see csharp/claude-api/README.md for details, or curl/managed-agents.md for raw HTTP reference.

When the user wants to set up a Managed Agent from scratch (e.g. "how do I get started", "walk me through creating one", "set up a new agent"): read shared/managed-agents-onboarding.md and run its interview - same flow as the managed-agents-onboard subcommand. When they point at a page to copy the setup from ("set up the agent from this cookbook", "build what this post describes"): read shared/managed-agents-onboarding-from-url.md instead. When what they describe is close to a bundled quickstart (list shared/managed-agents-quickstarts/; each file's frontmatter has a one-line description): say which one, and offer it once before the interview.

When the user asks "how do I write the client code for X": reach for shared/managed-agents-client-patterns.md - covers lossless stream reconnect, processed_at queued/processed gate, interrupt, tool_confirmation round-trip, the correct idle/terminated break gate, post-idle status race, stream-first ordering, file-mount gotchas, etc. For credentials, lead with vault environment_variable credentials - the first-class mechanism; secrets are substituted at egress and never enter the sandbox (shared/managed-agents-tools.md -> Vaults). Keeping credentials host-side via custom tools is the fallback where vault credentials don't fit (e.g. self-hosted sandboxes).

When the task is a deliverable - default the kickoff to an outcome, not a plain message. If the session's job is to produce something checkable (an artifact, a report, a PR, a dataset, a fixed set of changes), read shared/managed-agents-outcomes.md and kick off with user.define_outcome plus a starter rubric you draft from the task (5-10 concrete, independently gradeable criteria; comment it as a starter to tune). Reserve plain user.message for genuinely conversational sessions. Trigger on intent, not just the word: "keep working until it's right", "make sure the output is actually good", "don't stop at a first draft" all mean outcomes.

When the user asks about tool approvals, permission policies, or "auto mode" (which tool calls need a human, letting the server evaluate calls, evaluated_permission / evaluation on tool-use events): read shared/managed-agents-tools.md § Permission Policies - always_allow / always_ask / auto and the three auto outcomes (runs, denied as high-risk, pauses when indeterminate). For attaching a terminal to a live session (ant beta:sessions connect): shared/anthropic-cli.md.

When the user wants the agent to run on a schedule (cron, "every night", "weekly report"): read shared/managed-agents-scheduled-deployments.md - deployments fire sessions autonomously on a cron cadence, with per-firing run records and lifecycle controls (pause/unpause/archive).

When the agent's work fans out (research across several sources, per-file or per-record work, "look into N things, then summarize") or one loop would fill its context with reading: read shared/managed-agents-multiagent.md and recommend a multiagent session - start with just {"type": "self"} in the roster so the agent can delegate to copies of itself, then move reading-heavy sub-tasks to a cheaper worker agent (e.g. Claude Haiku 5.5, or Claude Sonnet 5.5 when the worker needs more judgment) referenced by ID.

Server Tools (Quick Reference)

Server-side tools run on Anthropic's infrastructure - no client-side execution loop. Declare in tools; results arrive as content blocks in the same response. No beta header unless noted. Prefer the latest type variant your model supports. The _20260209 web search / web fetch variants below (dynamic filtering) require Opus 5.5/5/4.8/4.7/4.6, Sonnet 5.5, Sonnet 5, or Sonnet 4.6; the basic variants for older models are listed after the table.

web_search_20260209 / web_fetch_20260209 have built-in dynamic filtering - code execution runs under the hood, so do not separately declare code_execution in tools (a second execution environment confuses the model). For models older than Opus 4.6 / Sonnet 4.6, use the basic variants web_search_20250305 / web_fetch_20250910 instead; on Vertex AI only basic web_search_20250305 is available. code_execution_20260120 (REPL persistence + programmatic tool calling) runs on Opus 4.5+ / Sonnet 4.5+. Go SDK only: code_execution_20260521 lives under client.Beta.Messages.New with Betas: []anthropic.AnthropicBeta{"code-execution-2025-08-25"} (other languages use plain client.messages.create); code_execution_20260120 uses the non-beta client.Messages.New in Go like everywhere else. Web fetch only fetches URLs already present in the conversation. Provider availability varies by tool - see shared/platform-availability.md. See shared/tool-use-concepts.md for pause_turn handling.

Document & File Input (Quick Reference)

PDF (base64, no beta): {"type": "document", "source": {"type": "base64", "media_type": "application/pdf", "data": <b64 string>}} in user content, placed before the text block. Base64 string must have no newlines. Limits: 32 MB request, 600 pages (100 for 200k-context models). Java: ContentBlockParam.ofDocument(DocumentBlockParam... Base64PdfSource.builder().data(...)).

Files API (no beta): upload via client.files.upload(...) -> response id is the file_id. Reference it as {"type": "document", "source": {"type": "file", "file_id": "..."}} for PDF/text, or {"type": "image", ...} for images - the content-block type must match the file's MIME type. To migrate code off files-api-2025-04-14, WebFetch the Files API row in shared/live-sources.md. Availability: shared/platform-availability.md.

Citations (no beta): set citations: {enabled: true} on each document content block (all or none). Response splits into multiple text blocks; cited blocks carry a citations array. Each citation has cited_text, document_index, document_title, and a location by type: char_location (start_char_index/end_char_index) for plain text, page_location (start_page_number/end_page_number, 1-indexed) for PDF, content_block_location for custom content. Incompatible with output_config.format (returns a 400).

Tool Use Patterns (Quick Reference)

Strict tool use (no beta): set strict: true as a top-level field on the tool definition (alongside name/description/input_schema), not on tool_choice. Schema must have additionalProperties: false + required. Guarantees tool_use.input validates exactly. Go: Strict: anthropic.Bool(true) + additionalProperties via InputSchema.ExtraFields; Java: .strict(true) + .putAdditionalProperty("additionalProperties", JsonValue.from(false)).

Parallel tool use (default on): one assistant message may contain multiple tool_use blocks. Execute them concurrently, then return all tool_result blocks in a single user message - splitting them across multiple messages silently trains Claude to stop making parallel calls. For a failed tool, return tool_result with is_error: true - don't drop it.

Tool Runner (SDK beta helper): drives the tool-call loop for you via client.beta.messages.*. Python: @beta_tool decorator + client.beta.messages.tool_runner(...) -> runner.until_done(). TypeScript: betaZodTool({...}) from @anthropic-ai/sdk/helpers/beta/zod + client.beta.messages.toolRunner(...) -> await runner. Go: toolrunner.NewBetaToolFromJSONSchema(...) + client.Beta.Messages.NewToolRunner(...) -> .RunToCompletion(ctx). Java requires .addBeta("structured-outputs-2025-11-13"). Ruby: Anthropic::BaseTool subclass + client.beta.messages.tool_runner(...). PHP: BetaRunnableTool + ->toolRunner(...). C#: raw JSON-schema tools + BetaToolRunner via client.Beta.Messages.ToolRunner(...).

Programmatic tool calling (no beta header): Claude calls your custom tool from inside code execution. Add {"type": "code_execution_20260120", "name": "code_execution"} and set "allowed_callers": ["code_execution_20260120"] on your custom tool. Opus 4.5+ / Sonnet 4.5+ (availability: shared/platform-availability.md). When responding to a pending programmatic call, the user message must contain only tool_result blocks (no text). Not compatible with strict: true, disable_parallel_tool_use, forced tool_choice, or MCP tools.

Other API Surfaces (Quick Reference)

Message Batches (no beta; availability: shared/platform-availability.md): client.messages.batches.create(requests=[{custom_id, params}, ...]) -> poll client.messages.batches.retrieve(id).processing_status until "ended" -> stream client.messages.batches.results(id). Each result has .custom_id + .result.type (succeeded/errored/canceled/expired); on success read .result.message.content. Python wraps requests as Request(custom_id=..., params=MessageCreateParamsNonStreaming(...)). Results arrive in any order - key by custom_id, never by position.

Models API (no beta; availability: shared/platform-availability.md): client.models.list() (auto-paginates) and client.models.retrieve("claude-opus-5-5"). Each model object has id, display_name, created_at, and - since Mar 2026 - max_input_tokens (the context window), max_tokens (the output cap), and capabilities. There is no context_window field.

Stop details (GA, Opus 4.7+): response.stop_details is populated only when stop_reason == "refusal" (fields: type: "refusal", category - an open set, e.g. "cyber", "bio", "reasoning_extraction", "frontier_llm", or null; see the docs for the full list - and explanation). It is null for every other stop_reason (end_turn, max_tokens, tool_use, pause_turn, ...) - always guard before reading.

Admin API (beta, since 2026-08-26): organization management - members, invites, workspaces and workspace members, API keys, rate limit reports, service accounts, federation issuers/rules, CMEK external keys - under client.beta.organization in all seven SDKs and ant beta:organization in the CLI. Requires an admin credential: an Admin API key (sk-ant-admin..., read from ANTHROPIC_API_KEY) or an org:admin OAuth token (ANTHROPIC_AUTH_TOKEN); regular API keys are rejected. Usage and cost reports and the Claude Enterprise user-management/analytics endpoints are not in the SDKs - raw HTTP only. See shared/admin-api.md.

Client config (no beta): timeout default 10 min; units differ by SDK - Python/Ruby: seconds; TypeScript: milliseconds; Go option.WithRequestTimeout(time.Duration); Java Duration; C# TimeSpan. TS scales the default up to 60 min for large max_tokens on non-streaming requests; Java does so for streaming requests (Java non-streaming scales 30s-10 min). max_retries/maxRetries default 2 (retries 408/409/429/5xx + connection errors). base_url (or ANTHROPIC_BASE_URL env). Per-request override: Python client.with_options(timeout=5.0).messages.create(...); TS client.messages.create({...}, {timeout: 5_000}); Ruby request_options: {timeout: 5}. Timeouts are retried - wall-clock can reach timeout × (max_retries+1).

Workload Identity Federation (Quick Reference)

GA, no beta header. Construct the normal zero-arg client (Anthropic() / new Anthropic() / anthropic.NewClient() / AnthropicOkHttpClient.fromEnv()); the SDK auto-detects WIF when all of ANTHROPIC_FEDERATION_RULE_ID, ANTHROPIC_ORGANIZATION_ID, ANTHROPIC_SERVICE_ACCOUNT_ID, and ANTHROPIC_IDENTITY_TOKEN_FILE (or ANTHROPIC_IDENTITY_TOKEN) are set, exchanges the JWT at /v1/oauth/token, and auto-refreshes. ANTHROPIC_WORKSPACE_ID does not gate activation - required only when the federation rule spans multiple workspaces (else 400 workspace_id_required), optional for single-workspace rules. ANTHROPIC_API_KEY or ANTHROPIC_AUTH_TOKEN (even empty) outrank WIF, and a set ANTHROPIC_PROFILE also wins over the federation env vars (a missing named profile is an error, not a fall-through) - unset all three.

Reading Guide

After detecting the language, read the relevant files based on what the user needs. Every {lang}/..., shared/..., and curl/... path cited in this document is relative to this skill's base directory, and none of those files' content is included above - Read each one on demand before relying on what it covers.

All SDK languages use the same multi-file layout - directory {lang}/claude-api/ containing README.md (install, client init, basic request, thinking, caching, stop details, misc), tool-use.md (tool definitions, agentic loop, Anthropic-defined tools, structured outputs), streaming.md, batches.md, files-api.md. Not every language has every file (e.g., Ruby has no batches.md); if a file is absent, that feature's example is not yet documented for that language - fall back to the cURL shape or WebFetch the SDK repo from shared/live-sources.md. cURL -> curl/examples.md.

The Quick Task Reference below uses the {lang}/claude-api/FILE.md path notation for all languages.

Quick Task Reference

Single text classification/summarization/extraction/Q&A: -> Read only {lang}/claude-api/README.md - always read the README first for any task (installation, quick start, common patterns, error handling)

Chat UI or real-time response display: -> Read {lang}/claude-api/README.md + {lang}/claude-api/streaming.md

Long-running conversations (may exceed context window): -> Read {lang}/claude-api/README.md - see Compaction section Migrating to a newer model (Haiku 5.5 / Sonnet 5.5 / Opus 5.5 / Fable 5.1 / Fable 5 / Opus 5 / Opus 4.8 / Opus 4.7 / Opus 4.6 / Sonnet 5 / Sonnet 4.6), replacing a retired model, or translating budget_tokens / prefill patterns to the current API: -> Read shared/model-migration.md Upgrading the Anthropic SDK package itself across a major version (anthropic 0.x -> 1.x: httpx2, awaited async .with_raw_response, removed deprecated parameters / aliases / Text Completions, Python >= 3.10) - or writing new code against a project already on 1.x: -> Read {lang}/claude-api/sdk-upgrade.md (currently Python only; other SDKs have no bundled major-version guide yet - use that SDK's CHANGELOG via shared/live-sources.md) Building an eval set for a Claude app (or "how do I know if my change helped"): -> Read shared/evals/build-eval.md - it loads shared/evals/eval-audit.md (the health checklist every eval must satisfy) before Step 0. Checking whether an existing eval is trustworthy ("is my eval any good?"): -> Read shared/evals/eval-audit.md and run it against the eval; report per its section 6. Iteratively improving an app against an eval (prompt tuning, hill-climbing): -> Read shared/evals/eval-hillclimb.md - runs Step 0 -> Step 5 with a train/test split; test is scored every round and is the headline. Rendering an eval-hillclimb HTML report: -> Run shared/evals/report/build-report.mjs when it is on disk (EAP install), else shared/evals/report/build-report-lite.mjs (always extracted with this skill) - both consume the _state.json / vN/ layout produced by the hillclimb guide and write the same trajectory/scores.tsv. Don't write a parallel one. Migrating to, prompting, or tuning Claude Opus 5.5 (thinking can't be disabled, effort tuning and the medium default, forced tool use, computer toolset, progress updates, safeguard false positives, visual inputs / design outputs): -> Read shared/model-migration.md -> Migrating to Claude Opus 5.5; the preserved-thinking mechanics it points at are under Migrating to Claude Fable 5.1 from Claude Fable 5 Migrating to, prompting, or tuning Claude Sonnet 5.5 (between_tools instead of disabled thinking, recalibrated effort, forced tool use, computer toolset, advisor pairings, progress updates, tool use in chat, mid-turn user messages, verification at low effort, safeguard categories): -> Read shared/model-migration.md -> Migrating to Claude Sonnet 5.5 Prompting or tuning Fable 5/5.1 (long turns, effort, verbosity, autonomous runs, sub-agents): -> Read shared/model-migration.md -> Migrating to Claude Fable 5.1 -> Behavioral shifts (prompt-tunable) + Long-running agent recommendations Prompting or tuning Claude Fable 5.1 (progress updates, parallel tool calls, writing density / formatting, autonomy, test sprawl, whole-file rewrites) or making a harness compatible with preserved thinking's history-editing check (history edits, compaction, per-turn reminders): -> Read shared/model-migration.md -> Migrating to Claude Fable 5.1 from Claude Fable 5 -> New API features + Behavioral shifts (prompt-tunable); for the history-editing check itself (the three-step check, the append-only edit table, compaction shapes), Breaking change 3 in the same section; to find, measure and fix the edits an existing harness makes (capture, diff, replay with drop_block, one fix per cause, model switches), run preserved-thinking-migration (Subcommands table) - it reads shared/preserved-thinking-migration.md Prompt caching / optimize caching / "why is my cache hit rate low": -> Read shared/prompt-caching.md (prefix-stability design, breakpoint placement, anti-patterns that silently invalidate cache) + {lang}/claude-api/README.md (Prompt Caching section) Auditing or cleaning up prompts, tool descriptions, skills, or agent configuration files such as CLAUDE.md ("is this prompt outdated", "remove the cruft", "this was written for an older model"): -> Read shared/prompt-audit.md - dated-pattern tables with greppable signals, the keep list (what NOT to delete), and the report + proposed-diff output contract Count tokens in a file / prompt / diff ("how many tokens is X"): -> Read shared/token-counting.md - use messages.count_tokens, never tiktoken Reducing or reviewing API spend ("the bill is too high", "make this cheaper", "am I overspending", cost per completed task, cheapest model or effort that holds quality): -> Read shared/cost-optimization.md - baseline and token profile first, then the levers in order (free wins before tradeoffs) with measured expectations, and a workload-shape -> lever mapping table

Function calling / tool use / agents: -> Read {lang}/claude-api/README.md + shared/tool-use-concepts.md (conceptual foundations: function calling, code execution, memory, structured outputs) + {lang}/claude-api/tool-use.md (language-specific code examples: tool runner, manual loop, code execution, memory, structured outputs)

Agent design (tool surface, context management, caching strategy): -> Read shared/agent-design.md (bash vs. dedicated tools, programmatic tool calling, tool search/skills, context editing vs. compaction vs. memory, caching principles)

Batch processing (non-latency-sensitive; runs asynchronously at 50% cost): -> Read {lang}/claude-api/README.md + {lang}/claude-api/batches.md

File uploads across multiple requests (same file without re-uploading): -> Read {lang}/claude-api/README.md + {lang}/claude-api/files-api.md

Organization administration (members, invites, workspaces, API keys, rate limit reports, service accounts, WIF resources, CMEK): -> Read shared/admin-api.md - client.beta.organization endpoint/method table, admin credentials, per-language naming and pagination, what stays curl-only

Debugging HTTP errors or implementing error handling: -> Read shared/error-codes.md - per-SDK typed exception class table and the Go errors.As pattern

Latest official documentation: -> WebFetch the URLs in shared/live-sources.md

Managed Agents (server-managed stateful agents with workspace): -> See the reading guide in the ## Managed Agents (Beta) section above - it lists every shared/managed-agents-*.md file and the language-specific READMEs ({lang}/managed-agents/README.md, curl/managed-agents.md).

When to Use WebFetch

Use WebFetch to get the latest documentation when:

• User asks for "latest" or "current" information
• Cached data seems incorrect
• User asks about features not covered here

Live documentation URLs are in shared/live-sources.md.

Common Pitfalls

• Don't truncate inputs when passing files or content to the API. If the content is too long to fit in the context window, notify the user and discuss options (chunking, summarization, etc.) rather than silently truncating.
• Prefill removed (Fable 5, Claude Fable 5.1, Opus 5, Claude Opus 5.5, Sonnet 5, Claude Sonnet 5.5, and the 4.6/4.7/4.8 family): Assistant message prefills (last-assistant-turn prefills) return a 400 error on Fable 5, Claude Fable 5.1, Opus 5, Claude Opus 5.5, Sonnet 5, Claude Sonnet 5.5, Claude Haiku 5.5, Opus 4.6, Opus 4.7, Opus 4.8, and Sonnet 4.6. Use structured outputs (output_config.format) or system prompt instructions to control response format instead. (One exception: the fallback-credit prefill claim - when redeeming a credit with fallback_has_prefill_claim: true, the server accepts the echoed assistant message; see the migration guide's refusal section.)
• Confirm migration scope before editing: When a user asks to migrate code to a newer Claude model without naming a specific file, directory, or file list, ask which scope to apply first - the entire working directory, a specific subdirectory, or a specific set of files. Do not start editing until the user confirms. Imperative phrasings like "migrate my codebase", "move my project to X", "upgrade to Sonnet 4.6", or bare "migrate to Opus 4.8" are still ambiguous - they tell you what to do but not where, so ask. Proceed without asking only when the prompt names an exact file, a specific directory, or an explicit file list ("migrate app.py", "migrate everything under services/", "update a.py and b.py"). See shared/model-migration.md Step 0.
• max_tokens defaults: Don't lowball max_tokens - hitting the cap truncates output mid-thought and requires a retry. For non-streaming requests, default to ~16000 (keeps responses under SDK HTTP timeouts). For streaming requests, default to ~64000 (timeouts aren't a concern, so give the model room). Only go lower when you have a hard reason: classification (~256), cost caps, deliberately short outputs, or max_tokens: 0 for cache pre-warming (see shared/prompt-caching.md -> Pre-warming).
• Disabling thinking on Claude Opus 5 has two failure modes - prefer low/medium effort instead. (On Claude Opus 5.5, {type: "disabled"} is a 400 at every effort level - use low effort. On Claude Sonnet 5.5 it is also a 400 - try low effort first, and if a route must stay thinking-off, send {type: "between_tools"} at high effort or below.) Watch for a disabled-thinking setting carried forward from Opus 4.8. With it, the model occasionally writes a tool call into its visible text instead of a tool_use block (the call never runs, no error is raised), and can leak <thinking> tags. Turning thinking on and lowering effort fixes both. If a route must stay thinking-off: delete any don't-think/don't-reason rule, don't name thinking tags, and add "When you use a tool, you may say a brief sentence first. If no tool can express what the user asked for, say so instead of guessing. Do not include internal or system XML tags in your response." Details: shared/model-migration.md -> Two failure modes when thinking is disabled.
• 128K output tokens: Fable 5, Claude Fable 5.1, Opus 5, Claude Opus 5.5, Opus 4.6, Opus 4.7, Opus 4.8, Claude Sonnet 5.5, Sonnet 5, Sonnet 4.6, and Claude Haiku 5.5 support up to 128K max_tokens, but the SDKs require streaming for values that large to avoid HTTP timeouts. Use .stream() with .get_final_message() / .finalMessage().
• Forced tool use removed (Claude Fable 5.1 / Claude Mythos 5.1 / Claude Opus 5.5 / Claude Sonnet 5.5): tool_choice: {type: "any"} and {type: "tool", name: ...} return a 400 (tool_choice: type "tool" and "any" are not supported for this model.), on count_tokens and Batches too. Use {type: "auto"} plus an explicit instruction naming the tool, strict: true on the tool to keep schema-valid arguments, or structured outputs (output_config.format) when the forced call only existed to get JSON back. {type: "none"} is unaffected; disable_parallel_tool_use still works with auto (at most one call).
• Tool call JSON parsing (Fable 5, Claude Fable 5.1, Opus 5, Claude Opus 5.5, and the 4.6/4.7/4.8 family): Fable 5, Claude Fable 5.1, Opus 5, Claude Opus 5.5, Opus 4.6, Opus 4.7, Opus 4.8, and Sonnet 4.6 may produce different JSON string escaping in tool call input fields (e.g., Unicode or forward-slash escaping). Always parse tool inputs with json.loads() / JSON.parse() - never do raw string matching on the serialized input.
• Structured outputs (all models): Use output_config: {format: {...}} instead of the deprecated output_format parameter on messages.create(). This is a general API change, not 4.6-specific.
• Don't reimplement SDK functionality: The SDK provides high-level helpers - use them instead of building from scratch. Specifically: use stream.finalMessage() instead of wrapping .on() events in new Promise(); use typed exception classes (Anthropic.RateLimitError, etc.) instead of string-matching error messages; use SDK types (Anthropic.MessageParam, Anthropic.Tool, Anthropic.Message, etc.) instead of redefining equivalent interfaces.
• Error handling - catch a chain, not one broad class. A single except APIStatusError / catch (AnthropicServiceException) / rescue APIError loses the distinction between retryable (429, >=500, network) and non-retryable (400/404) failures. Write a most-specific-first chain - e.g. NotFoundError -> RateLimitError -> APIStatusError -> APIConnectionError (or the Go equivalent: errors.As into *anthropic.Error then switch apierr.StatusCode { case 404: ...; case 429: ...; default: ... }). Per-language class names and namespaces are in shared/error-codes.md.
• Don't research SDK types - write first. If a type name isn't shown in the documentation included in this skill, write the code file from the namespace/package tables in the language-specific doc and let the compiler's error point you to the right name. Do not spend turns on WebFetch, SDK-repo clones, or compiling-and-running a separate reflection program to discover type names before writing - produce the source file first, then fix what the compiler reports. A quick strings / jar tf / javap against the installed SDK is acceptable for locating names (it returns in seconds), but don't escalate beyond that. A file with a wrong type name is recoverable; a session spent on discovery with no file written is not.
• Bash and text editor tools are Anthropic-defined, schema-less. Declare {"type": "bash_20250124", "name": "bash"} / {"type": "text_editor_20250728", "name": "str_replace_based_edit_tool"} - no input_schema. A custom tool with your own schema named "bash" is a different tool. Handler paths and security checks are in shared/tool-use-concepts.md § Client-Side Tools.
• Advisor tool model pairing. The advisor tool's model must be at least as capable as the request's top-level model - e.g. executor claude-sonnet-5-5 -> advisor claude-opus-5-5. An invalid pair returns 400; a claude-sonnet-5-5 executor accepts only the advisors its row in the pairing table lists (not Claude Opus 4.8 / 4.7 / 4.6, Claude Sonnet 5, or Sonnet 4.6). Pairing table (and which advisors return plaintext vs encrypted advisor_redacted_result advice) in shared/tool-use-concepts.md § Advisor. Availability: shared/platform-availability.md.
• Agent Skills != Managed Agents. To have Claude generate a .pptx/.xlsx/etc. via Agent Skills, call client.beta.messages.create with container={"skills": [...]}, the code_execution_20260521 tool, and the code-execution-2025-08-25 beta (Skills is out of beta - no skills-2025-10-02 header needed). Do not use client.beta.agents / sessions / environments here - those are the Managed Agents surface, not Agent Skills.
• MCP connector needs both halves. mcp_servers=[{type:"url", url, name}] alone is rejected as a validation error - also add tools=[{type:"mcp_toolset", mcp_server_name:<same name>}] with beta mcp-client-2025-11-20. Availability: shared/platform-availability.md.
• inference_geo is a direct top-level request parameter - client.messages.create(..., inference_geo="us") / .inferenceGeo("us"). Do not put it in extra_body / putAdditionalBodyProperty. (Messages API only - on Managed Agents, inference_geo instead nests inside the agent's model object, never top-level; see shared/managed-agents-core.md § Pinning inference geography.) Supported on Opus 4.6 / Sonnet 4.6 and later; availability: shared/platform-availability.md. response.usage.inference_geo reports where inference ran.
• Fine-grained tool streaming is not a beta feature; this skill's default is to turn it on for streaming + client tools (the API itself still defaults to buffered). Set eager_input_streaming: true on the tool definition and call the regular client.messages.stream(...). There is no beta header and no client.beta.* path. Do not also send the legacy fine-grained-tool-streaming-2025-05-14 beta header. Python's @beta_tool(eager_input_streaming=True) accepts it directly; TypeScript's betaZodTool() does not, so spread it on: { ...betaZodTool({...}), eager_input_streaming: true }. With the field on, the API no longer coerces or validates the input, so the accumulated partial_json may be incomplete (max_tokens) or invalid - guard the parse (shared/tool-use-concepts.md -> Eager input streaming).
• Cache diagnostics is beta. Use client.beta.messages.* with beta cache-diagnosis-2026-04-07. Pass diagnostics: {previous_message_id: null} on the first turn and diagnostics: {previous_message_id: <previous response id>} on subsequent turns; the result is on response.diagnostics. Availability: shared/platform-availability.md.
• Memory tool type is memory_20250818. Declare {"type": "memory_20250818", "name": "memory"}. Go uses the beta-namespace type {OfMemoryTool20250818: &anthropic.BetaMemoryTool20250818Param{}} on client.Beta.Messages.New; Python/TypeScript/Ruby/PHP/C# use the non-beta client.messages.create; Java has both a non-beta MemoryTool20250818 and a beta tool-runner path. Python/TypeScript provide BetaAbstractMemoryTool / betaMemoryTool helpers for implementing the backend.
• Use a model the feature actually supports. Some features are restricted to specific model tiers - fast mode is Claude Opus 5 / Claude Opus 5.5 / Opus 4.8 only (and Claude API only), task budgets (Messages API only - Managed Agents session budgets have no model-tier restriction) are Claude Opus 5 / Claude Opus 5.5 / Fable 5 / Claude Fable 5.1 (confirm at launch) / Claude Sonnet 5.5 / Claude Haiku 5.5 / Opus 4.8 / 4.7 only (not Claude Sonnet 5), and the advisor tool requires a valid executor<->advisor pair. If the user's prompt names a model that the feature doesn't support, use a supported model instead and note the substitution in the output.
• Don't define custom types for SDK data structures: The SDK exports types for all API objects. Use Anthropic.MessageParam for messages, Anthropic.Tool for tool definitions, Anthropic.ToolUseBlock / Anthropic.ToolResultBlockParam for tool results, Anthropic.Message for responses. Defining your own interface ChatMessage { role: string; content: unknown } duplicates what the SDK already provides and loses type safety.
• Report and document output: For tasks that produce reports, documents, or visualizations, the code execution sandbox has python-docx, python-pptx, matplotlib, pillow, and pypdf pre-installed. Claude can generate formatted files (DOCX, PDF, charts) and return them via the Files API - consider this for "report" or "document" type requests instead of plain stdout text.
• Server-tool errors don't raise. Web search and web fetch errors return HTTP 200 with a web_search_tool_result / web_fetch_tool_result block whose content is a single error object (e.g. {error_code: "max_uses_exceeded"}) - not a raised exception. For web search, a success content is a list; an error content is an object - branch on that before indexing.
• Managed Agents web tools ignore the environment's networking. web_search / web_fetch run on Anthropic's servers in cloud and self-hosted environments, and Console org-level web settings apply to the Messages API only. Turn both off (enabled: false) unless the job needs the web; when it does and the sites are known in advance, restrict them per tool with allowed_domains or blocked_domains (never both; 1-64 plain hostnames per list, subdomains covered; IPs, bare TLDs, single-label and localhost-style names rejected on both tools; a path suffix is allowed only on web_search) on the toolset configs entry - shared/managed-agents-tools.md § Web search & web fetch settings.
• Eval / hillclimb work has dedicated guides: If the user says "hillclimb", "improve my eval score", "iterate on my prompt against an eval", or "build me an eval" - load shared/evals/eval-hillclimb.md or shared/evals/build-eval.md rather than improvising. The bundled HTML report builder is shared/evals/report/build-report.mjs when it is on disk (EAP install), else shared/evals/report/build-report-lite.mjs (always extracted with this skill); don't write a parallel one.
• Code execution output block type: code_execution_20260521 returns bash_code_execution_tool_result (with .content.stdout), not the legacy bare code_execution_tool_result. Iterate response.content and match on the correct type.
• Tool search: never defer everything. The search tool itself must not have defer_loading: true, and at least one tool in tools must be non-deferred, or the API returns 400 All tools have defer_loading set.

Detected Language: python

python/claude-api/README.md is included below since every task starts there. Read the other referenced files from the base directory on demand. That directory is session-scoped — after resuming a session, or if a Read under it ever fails, re-invoke this skill to re-extract.

Installation

Client Initialization

Client Configuration

Per-request overrides

Use with_options() to override client settings for a single call without mutating the client:

Timeouts

Default request timeout is 10 minutes. Pass a float (seconds) or an anthropic.Timeout for granular control. On timeout the SDK raises anthropic.APITimeoutError (and retries per max_retries).

anthropic 1.x is built on httpx2, not httpx. anthropic.Timeout is httpx2.Timeout; if you import the HTTP library yourself, write import httpx2 as httpx - an object from the httpx package (httpx.Timeout, httpx.Client, transports, limits) is rejected or fails at request time. Existing httpx-era code is covered by the v1 migration guide and /claude-api upgrade python.

Retries

The SDK auto-retries connection errors, 408, 409, 429, and >=500 with exponential backoff (default 2 retries). Set max_retries on the client or via with_options(); max_retries=0 disables.

Async performance (aiohttp backend)

For high-concurrency async workloads, install anthropic[aiohttp] and pass DefaultAioHttpClient instead of the default httpx2 backend:

Custom HTTP client (proxy, base URL)

Use DefaultHttpxClient / DefaultAsyncHttpxClient - not a raw httpx2.Client (and never a client from the httpx package) - so the SDK's default timeouts and connection limits are preserved:

Logging

Set ANTHROPIC_LOG=debug (or info) to enable SDK logging via the standard logging module.

Basic Message Request

System Prompts

Mid-conversation system messages (model-gated)

For operator instructions that arrive mid-conversation (mode switches, injected state), append {"role": "system", ...} to messages instead of editing top-level system - this preserves the cached prefix and carries operator authority. Must follow a user message (or an assistant message ending in server-tool use), and must be either the last entry in messages or be followed by an assistant turn; cannot be messages[0]. Unsupported models return a 400 (role 'system' is not supported on this model). See shared/prompt-caching.md for when to use this vs. top-level system.

Vision (Images)

Base64

URL

Prompt Caching

Cache large context to reduce costs (up to 90% savings). Caching is a prefix match - any byte change anywhere in the prefix invalidates everything after it. For placement patterns, architectural guidance (frozen system prompt, deterministic tool order, where to put volatile content), and the silent-invalidator audit checklist, read shared/prompt-caching.md.

Automatic Caching (Recommended)

Use top-level cache_control to automatically cache the last cacheable block in the request - no need to annotate individual content blocks:

Manual Cache Control

For fine-grained control, add cache_control to specific content blocks:

Verifying Cache Hits

If cache_read_input_tokens is zero across repeated identical-prefix requests, a silent invalidator is at work - datetime.now() or a UUID in the system prompt, unsorted json.dumps(), or a varying tool set. See shared/prompt-caching.md for the full audit table.

Extended Thinking

Fable 5, Claude Opus 5.5, Claude Opus 5, Opus 4.8, Opus 4.7, Opus 4.6, and Sonnet 4.6: Use adaptive thinking. budget_tokens is removed on Fable 5, Claude Opus 5.5, Claude Opus 5, Opus 4.8, and 4.7 (400 if sent); deprecated on Opus 4.6 and Sonnet 4.6. Claude Opus 5.5: thinking is always on - omit thinking (or send {"type": "adaptive"}, which is equivalent); {"type": "disabled"} returns a 400 at every effort, as does a thinking budget. Control depth with output_config.effort instead - the default is medium on this model, where Claude Opus 5 defaults to high. Claude Opus 5: thinking is on by default - omitting thinking runs adaptive ({"type": "adaptive"} is equivalent), unlike Opus 4.8/4.7 where omitting it meant no thinking. {"type": "disabled"} is accepted only at effort high or lower; pairing it with xhigh/max returns a 400. Claude Haiku 5.5: adaptive thinking only, on by default; budget_tokens returns a 400. Older models: Use thinking: {type: "enabled", budget_tokens: N} (must be < max_tokens, min 1024).

Error Handling

Response Helpers

Every response object exposes _request_id (populated from the request-id header) - log it when reporting failures to Anthropic. Despite the underscore prefix, this property is public.

To access raw headers or other response metadata, use .with_raw_response:

Multi-Turn Conversations

The API is stateless - send the full conversation history each time.

Rules:

• Consecutive same-role messages are allowed - the API combines them into a single turn
• First message must be user
• role: "system" messages are allowed mid-conversation on supporting models (no beta header needed) - see § Mid-conversation system messages above

Compaction (long conversations)

Beta, Fable 5, Claude Opus 5.5, Claude Opus 5, Opus 4.8, Opus 4.7, Opus 4.6, and Sonnet 4.6. When conversations approach the 200K context window, compaction automatically summarizes earlier context server-side. The API returns a compaction block; you must pass it back on subsequent requests - append response.content, not just the text.

Stop Reasons

The stop_reason field in the response indicates why the model stopped generating:

Structured Stop Details

When stop_reason is "refusal", the response includes a stop_details object with structured information about the refusal:

Refusal Fallbacks (Claude Fable 5.1) - opt in by default

Fallbacks are opt-in: without them a refused request simply stops. Include the server-side fallbacks parameter in claude-fable-5-1 code by default - on a policy decline the API re-runs the same request on the fallback model inside the same call. A mid-stream decline is billed at normal rates, and the rescue bills at the fallback model's own rates, with cache repricing applied automatically; for a decline before any output, see How refusals are billed.

A stop_reason: "refusal" on the final response means the whole chain refused. The header must be exactly server-side-fallback-2026-06-01 for this array form; the newer fallbacks: "default" scalar form uses server-side-fallback-2026-07-01 instead (see shared/model-migration.md -> Migrating to Claude Opus 5 -> New API features), and pairing either header with the other form returns a 400. The parameter is rejected on the Batches API and unavailable on Amazon Bedrock, Vertex AI, and Microsoft Foundry - register the client-side BetaRefusalFallbackMiddleware on the client there instead. Full semantics (sticky routing, billing, streaming, echoing fallback turns back): shared/model-migration.md -> Migrating to Claude Fable 5.1 -> refusal stop reason.

Cost Optimization Strategies

1. Use Prompt Caching for Repeated Context

2. Choose the Right Model

3. Use Token Counting Before Requests

Retry with Exponential Backoff

Note: The Anthropic SDK automatically retries rate limit (429) and server errors (5xx) with exponential backoff. You can configure this with max_retries (default: 2). Only implement custom retry logic if you need behavior beyond what the SDK provides.

User Request

Only need: Sonnet 5.5 (claude-sonnet-5-5) list price per million input and output tokens.

[Image: original 1280x2574, displayed at 995x2000. Multiply coordinates by 1.29 to map to original image.]

getting this question

next question is this

for this?

done, both detections created and investigate started i think.

What are the next steps, do we have a front-end for it, what are the next steps please complete the entire hackathon project!!!

[Image: original 1280x4061, displayed at 630x2000. Multiply coordinates by 2.03 to map to original image.]

give me prompt to investgate on this window, yes on the pages you may use netlify instead of github and tell me the steps, also you may Permanently delete the ~50 empty junk traces in neatlogs okay

This is what neatlog told me todo! see image

<pasted_content id="1519"> You are an expert systems engineer and runbook generator. Your task is to extract installation and setup steps from the provided documentation Markdown and format them into a structured JSON runbook.

You must follow these strict rules to ensure reliability, safety, and determinism:

1. STRICT EXTRACTION ONLY (No Hallucinations):

   • You must ONLY extract commands that are explicitly written inside shell code blocks (e.g., bash, sh, ```shell) in the provided Markdown.
   • NEVER invent verification steps (such as command -v <cmd>, test -f <file>, which <cmd>) unless they are literally written as code blocks in the documentation.
   • If the documentation page is processed multiple times, it must produce the exact same steps every time.

2. PYTHON CODE & FILE EXECUTION (No true placeholding):

   • If the documentation contains a Python code block demonstrating how to run an example: a) Write the Python code to the specified file path (e.g., quickstart.py) using the Files schema field. b) Set the Command field of that step to execute the file: python <filename> (e.g., python quickstart.py). c) NEVER use true or other no-op shell placeholders as a command.

3. SAFE ENVIRONMENT VARIABLES & SECRETS:

   • NEVER hardcode fake API keys, fake tokens, or mock secrets (e.g., NEVER output export OPENAI_API_KEY='sk-...' or export MY_SECRET='abc').
   • If the documentation instructs setting an environment variable, use the variable itself as a safe placeholder: export OPENAI_API_KEY="${OPENAI_API_KEY}" or simply omit the export step if the runner environment is expected to already have it configured.
   • NEVER skip subsequent execution steps just because they require an API key or environment variable. Include them fully so they can run when a real key is provided.

4. STEP SCHEMA ALIGNMENT: Each step in your output must follow this structure:

   • Id: Sequential integer starting at 1.
   • Intent: A short description of what the step does.
   • Command: The exact shell command to execute (no dummy true commands).
   • Files (Optional): List of files to create before running the command.
   • Expected: Exit Code and expected output criteria. </pasted_content id="1519">

i did netlfiy part its 1run.netlify.app as that was what was available

keep going, show me the PR drafts when ready

<pasted_content id="1519"> also, even if we are technically there, the packaging part of it, making it interesting, and showing the value on the page, not just on any page, is something that we need to work on. If it's not accessible to people, there should be a good experience, like a full loop in the UI. The full loop should be visible: whatever Celera is doing, I want it to be exposed to the app.

We could have some UUID. If the user has it and runs it in the CLI, the CLI should spit out a secret or something. If they put that secret on my web page, they should see the full list of visual changes on the web page. That way, I can easily sell this in a narrative, or there should be something fun or interesting. Of course, technically, this is irrelevant. No doubt, but we kind of have to bring that CLI experience to the frontend somehow, without excessive craziness. That's for you to do.

Also, please be very careful about the AWS credit usage because we only have $25, and I do not have more than that. Please ensure that we only have $25. We have to be extremely careful about how we use that budget, right? Extremely careful, please. Thank you. </pasted_content id="1519">

the webpage should also have the launch video i made and posted on twitter and visuals and posts which i have planned! It should be a complete and total experience, launch subagent, should show it's powered by neatlogs, entire and cfo ai similar to how the video was made refer to video studio or NOTES and get frames, assets, copies and make a stylish apple design styled page, with a section about me at the end and that it's made for the neatlogs hack, also all my tweets that i am making from cultist_dev should be embedded here to really show the full journey

obviously docs which have been tested should be cached and it should show cached run we have limited resources so please be very safe!! Without great UI/UX we are nothing!

[Image: original 1280x6335, displayed at 404x2000. Multiply coordinates by 3.17 to map to original image.]

yes 1, 2, 3, keep going

Also if you see the trails are not in building phase yet why? Please read the rules and the plan and make sure we are nailing it and on track to win, other people trail (image 2 is attached and it has given these things see image 2) - we need to be ahead of this!!! DO this urgently, make sure we are on track and nailing it!!

keep going, merge trail 6 when green and also is this screenshot task actually working or a dead script?

keep going, merge trail 7 when green your job is to stay busy, find improvements and bring this whole hackathon to a state of completion, also this is one use case - can you hunt 2 other important use cases which no other tool does and something that will impress judges, can be packages and explained visually very well and has an agentic loop benefit - improve the scope and please add that + then add it to plan + the site work well and do a very very good job!!!

This should have moat, you will need to think well and it's okay if it's not technical, etc as long as it uses the features well. Continue working and making major leaps!

Stuff we add that is new should go into the website as well later properly!

i'm going away please work until completion as per previous messages which were interrupted sorry i am away you are on your away blocked tasks keep parked but rest please continue building well and logging!

[Image: original 1280x4741, displayed at 540x2000. Multiply coordinates by 2.37 to map to original image.]

yes post the bisect comment on #10149 if highly confident, we should raise prs if condifence score is justified etc

keep going, show me the PR drafts when ready

post both don't keep going

There has been some progress since i last talked in this session, can you catch up and then can you look at this thing these three are still open? i think they are already merged? if not what is the action item here?

close them

short answer only please