Skip to main content
Search

# Claude Haiku 5.5

13 related articles

Subscribe to updates
  1. Claude Code now sends sandboxed Bash through normal permission checks, and no-prompt runs need an explicit switch

    Claude Code's changelog says sandboxed Bash commands now follow the normal permission flow by default instead of running without prompts; keeping prompt-free execution requires setting sandbox.autoAllowBashIfSandboxed. The same batch makes read-only git commands ask first in repositories that are not the project's or trusted, and unpacks plugin MCP bundles under the plugins directory so read-only plugin folders load. These changes concern the permission boundary for an agent running commands and loading plugins locally, not model capability.

  2. Claude Sonnet 5.5 prompt-cache reads drop to $0.10 per million tokens, while cache writes and all other prices stay put

    In its Claude Platform release notes, Anthropic cut the price of prompt cache reads on Claude Sonnet 5.5 from $0.20 to $0.10 per million tokens, which is 0.05x the base input price instead of 0.1x. Cache writes and all other prices are unchanged. For developers who resend the same long prefix, the saving applies to re-reading the cache, not to the first write or to newly generated content.

  3. Claude agents can now write their own multi-agent workflows, with the server running each one in the background

    Anthropic added dynamic workflows in beta to Claude Managed Agents on the Claude Platform: for work with many pieces, such as reviewing hundreds of documents, an agent can write a program that runs many agents in phases and combines their results, and the server runs it in the background as a workflow run. It is turned on by setting the agent's multiagent field to multiagent_20261001 with workflows enabled; the user can tell the agent in its system prompt when to start a run and follow each run through workflow_run.* events on the session's event stream.

  4. Claude Platform keeps conversations server-side: long chats and agent loops send only new messages, cutting time to first token

    Anthropic released message threads in beta on the Claude Platform Messages API, keeping the conversation on the server so later requests send only new messages, which makes requests smaller and lowers time to first token for long conversations and agent loops. The feature is enabled with the message-threads-2026-08-12 beta header, a thread expires 5 minutes after its last request and is deleted no more than 1 hour after its last use, and it is available on the Claude API, Claude Platform on AWS, Claude Models on Google Cloud (Anthropic managed), and Claude in Microsoft Foundry.

  5. Claude message threads enter beta: long conversations send only new messages, cutting time to first token

    Anthropic released message threads in beta on the Messages API, keeping long conversations and agent loops on the server so each later request sends only the new messages, which shrinks requests and lowers time to first token. Previously such multi-turn interactions had to resend the full history each time. A thread expires 5 minutes after its last request and is deleted no more than 1 hour after its last use, and it is available on the Claude API, Claude Platform on AWS, Claude Models on Google Cloud (Anthropic managed), and Claude in Microsoft Foundry.

  6. Claude Console adds organization-wide IP allowlisting: a leaked API key is confined to listed addresses

    Anthropic now offers an IP allowlist for organizations in the Claude Console, in beta, and requests to covered services from addresses not on the list are refused, which limits where a leaked API key can be used. Admins can add IPv4 and IPv6 addresses or CIDR ranges, up to 1,000 per organization. Previously an organization could not narrow the entry point for requests by source address in the console; this setting shrinks the usable range after a key leak from any address to the listed ones.

  7. Claude models arrive on Google Cloud under Anthropic management, with IAM for access and Marketplace for billing

    Anthropic's Claude Platform release notes announce that Claude models are available on Google Cloud in an Anthropic-managed form: the API is still operated by Anthropic but reached through a customer's Google Cloud project, with access controlled by Google Cloud IAM and billing handled by Google Cloud Marketplace. The same notes say fast mode for Claude Opus 5.5 is available in that managed form. For teams already running workloads on Google Cloud, the route puts model calls inside the cloud provider's existing identity and billing systems.

  8. Claude adds a usage and cost API that splits bills by model, workspace and API key

    Anthropic released a beta Usage and Cost Analytics API on the Claude Platform, with two organization-level endpoints that report token usage and cost for Claude Console and Claude Enterprise organizations and let callers filter and group results by dimensions such as model, workspace, API key, and the user or service account behind each request. The same data previously came from the Usage and Cost API and four report endpoints of the Claude Enterprise Analytics API, which are now legacy but remain supported, with two documented migration paths. The new endpoints require the analytics-usage-cost-2026-08-24 beta header.

  9. Claude models land on Google Cloud: IAM governs access, Marketplace bills, and Opus 5.5 fast mode comes along

    Anthropic has put Claude models on Google Cloud in an Anthropic-managed form, so developers call the Claude API through their own Google Cloud project. Access is controlled by Google Cloud IAM and billing runs through Google Cloud Marketplace, replacing a separate arrangement for permissions and payment. Fast mode for Claude Opus 5.5 is available on the same managed channel.

  10. Claude Tag opens in beta: enterprise admins can read and change Claude settings on Slack channels

    Anthropic's Claude Platform release notes make the Claude Tag API available in beta to Claude Enterprise organizations, with /v1/organizations/claude_tag/ endpoints that read and change Claude Tag settings on Slack channels and workspaces. The endpoints show which settings apply in a channel and where each comes from, and can attach Access bundles; they require an Admin API key created by the primary owner and are not available to Claude Platform (Claude Console) organizations.