`Anthropic TypeScript SDK` `0.100.0` Adds `claude-opus-4-8` Support

// related

• #0001

  #0001Models & APIGeekNews22 hours ago

  Anthropic Ships `Claude Opus 4.8`

  90radar

  Same-price upgrade over 4.7, with better benchmarks and collaboration. Worth re-testing as a coding and agent default before changing spend assumptions.

  • —Built on Claude Opus 4.7; this is an incremental top-tier model refresh, not a new product line.
  • —Benchmark performance improved while pricing stays unchanged. Existing API cost models do not need recalculation first.
  • —Collaboration capability was strengthened, so agent workflows and pair-programming style tasks deserve fresh evals.

  Source: news.hada.io/topic?id=29960Read original →
• #0002

  #0002Models & APIAnthropic Python SDK24 hours ago

  `anthropic-sdk-python` `v0.105.0` adds `claude-opus-4-8` support

  70radar

  anthropic-sdk-pythonPython SDK — official client for Anthropic API

  Python clients can now call the new Opus variant and inspect richer token details. Worth upgrading before wiring new Claude features into production.

  • —claude-opus-4-8 is now supported in the official Python SDK, removing manual model-name workarounds.
  • —Mid-conversation system blocks landed in the API layer, useful for agent flows that need runtime instruction changes.
  • —usage.output_tokens_details exposes finer output-token accounting, making cost/debug dashboards easier to build.
  • —Custom file size caps are supported, so upload limits can be enforced closer to the SDK boundary.

  Source: github.com/anthropics/anthropic-sdk-python/releases/tag/Read original →
• #0003

  #0003Models & APIvercel_blogyesterday

  `Claude Opus 4.8` lands on `Vercel AI Gateway`

  80radar

  Vercel AI GatewayLLM gateway — unified calls, cost tracking, and failover

  Long-running coding and knowledge tasks can now route through one Vercel API. Useful if you already want retries, cost tracking, and failover without wiring providers yourself.

  • —Use anthropic/claude-opus-4.8 in the AI SDK; model switching stays inside the existing Gateway path.
  • —Positioned for long-horizon agent work: multi-step refactors and complex coding tasks need less mid-task correction.
  • —Gateway adds usage and cost tracking, retries, failover, and latency/cost-based provider sorting. Less infra glue around LLM calls.
  • —Pricing mirrors provider rates with no Vercel markup or platform inference fee, including BYOK requests.

  Source: vercel.com/changelog/opus-4-8-on-ai-gatewayRead original →