Skip to main content
Search

# Claude Managed Agents

18 related articles

Subscribe to updates
  1. Anthropic publishes a Claude Managed Agents reference build: a scheduled brief that reads Slack and GitHub, reports only changes, and flags sources it could not read

    Anthropic built a reference implementation of a scheduled agent automation on Claude Managed Agents (beta): it reads Slack channels and GitHub pull requests from per-source bookmarks, reports only what changed since the last run, and posts the result to one Slack channel. Against the usual failures of scheduled jobs, the configuration keeps a source's bookmark when a read fails and names that source as unreadable at the end of the brief, and it updates bookmarks and its ledger only after Slack confirms a post.

  2. 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.

  3. Claude Managed Agents can now write their own multi-agent workflows, with the server running phases in the background and merging results

    Anthropic's Claude Platform release notes say a Claude Managed Agents agent can now use dynamic workflows for work with many pieces, such as reviewing hundreds of documents. A workflow is a program that runs many agents in phases and combines their results, and the server runs it in the background as a workflow run. The capability is in beta under the managed-agents-2026-04-01 beta header, enabled by setting the agent's multiagent field to type multiagent_20261001 with workflows enabled.

  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 Platform adds an IP allowlist for organizations, so a leaked API key only works from listed addresses

    Claude Platform now offers organizations an IP allowlist in the Claude Console, in beta. Previously a leaked API key could be used from any address to reach covered services; with the allowlist on, requests from addresses not on the list are refused, limiting where the key can be used. Admins can add IPv4 and IPv6 addresses or CIDR ranges, up to 1,000 per organization.

  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 Console adds an organization-wide IP allowlist, narrowing where a leaked API key can be used

    Anthropic added a beta IP allowlist to the Claude Console, so only addresses on an organization's list can reach covered services, which limits where a leaked API key can still be used. Previously organizations had no console-level way to narrow requests by source address. Admins can enter IPv4 and IPv6 addresses or CIDR ranges, up to 1,000 per organization.

  8. 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.

  9. 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.

  10. Claude's Messages API takes four times more per request: 32 MB becomes 128 MB on the first-party API

    Anthropic's Claude Platform release notes raise the maximum request size for the Messages API and the Token Counting API from 32 MB to 128 MB on the first-party Claude API. Before this change, both endpoints stopped at 32 MB, so larger inputs could not be submitted as a single request. The change covers request size on the first-party Claude API only, and the notes report no throughput, latency or cost measurements.