CLAUDE LABJP
FORK — Claude Code 2.1.212 changes what /fork does: it copies your conversation into a new background session with its own row in claude agents, so you can keep working. The old in-session subagent is now /subtaskLIMITS — WebSearch calls are now capped at 200 per session by default, and subagent spawns get the same 200 ceiling, so a runaway search or delegation loop stops on its ownMCPBG — MCP tool calls running past two minutes now move to the background automatically, keeping the session usable. Tune the threshold with CLAUDE_CODE_MCP_AUTO_BACKGROUND_MSPLANFIX — Fixed plan mode auto-running file-modifying Bash commands such as touch and rm without a permission prompt or an SDK canUseTool callbackSONNET5 — Claude Sonnet 5 is running on introductory pricing of $2 per million input tokens and $10 per million output. After August 31 it moves to $3 and $15IPO — Bankers are reportedly lining up investor meetings for Anthropic ahead of a possible public listing as soon as OctoberFORK — Claude Code 2.1.212 changes what /fork does: it copies your conversation into a new background session with its own row in claude agents, so you can keep working. The old in-session subagent is now /subtaskLIMITS — WebSearch calls are now capped at 200 per session by default, and subagent spawns get the same 200 ceiling, so a runaway search or delegation loop stops on its ownMCPBG — MCP tool calls running past two minutes now move to the background automatically, keeping the session usable. Tune the threshold with CLAUDE_CODE_MCP_AUTO_BACKGROUND_MSPLANFIX — Fixed plan mode auto-running file-modifying Bash commands such as touch and rm without a permission prompt or an SDK canUseTool callbackSONNET5 — Claude Sonnet 5 is running on introductory pricing of $2 per million input tokens and $10 per million output. After August 31 it moves to $3 and $15IPO — Bankers are reportedly lining up investor meetings for Anthropic ahead of a possible public listing as soon as October
TAG

batch processing

6 articles
Back to all tags
Related:
Claude API4cost optimization2API2Message Batches1error handling1production operations1streaming1monitoring1indie developer1Crashlytics1Crash Analysis1Indie Development1
API & SDK/2026-07-02Advanced

When 41 of 20,000 Message Batches Requests Quietly Vanished — Field Notes on Reconciling and Requeuing Partial Failures

processing_status: ended does not mean every request succeeded. How errored and expired results hide inside a finished batch, and how a custom_id ledger catches every gap and requeues safely — with real cost and timing numbers.

API & SDK/2026-06-28Advanced

Measure Streaming CPU and Dropped Chunks to Stabilize Long Batch Jobs

You start an overnight batch, and by morning only half of it finished. The culprits were CPU pinned during streaming and a quiet connection drop. Here is a monitor wrapper that measures stream CPU and throughput, and resumes from interruptions.

API & SDK/2026-06-01Advanced

Grouping Crashes by Root Cause: A Triage Design Built on the Claude API

Crashlytics 'Issues' often scatter the same root cause across separate entries. After years of running apps with 50M+ cumulative downloads, here is how I use the Claude API to regroup crashes by actual root cause and rank them, with working code and real numbers.

API & SDK/2026-04-11Intermediate

Claude API Batch Processing — Reduce API Costs by Up to 90% with Asynchronous Batch Implementation

Master Claude API batch processing for efficient large-scale requests. Learn async batch patterns to reduce costs and avoid rate limits.

API & SDK/2026-04-02Intermediate

Anthropic API Cost Optimization Guide: Cut Your Monthly Bill by 50–70%

A complete guide to reducing your Anthropic API costs by 50–70%. Covering model selection, Prompt Caching, batch processing, and token reduction — with production-ready code you can apply to your app today.

API & SDK/2026-04-02Advanced

Claude API Messages Batches: Cutting Production Costs by Up to 50% with Async Processing

An implementation guide for putting the Claude API Messages Batches API into production. Polling design, real cost measurements, and operational gotchas from running 1,920 monthly requests across four Dolice Labs sites.