explainx / blog
Anthropic at Code with Claude Tokyo: cron scheduled Claude Managed Agents, vaults for API keys, dynamic workflows GA in Claude Code—from loop engineering to production agents.
Jul 1, 2026
Fable 5 is live July 1. Thirty-five concrete tasks to run first — with Sonnet 5 fallbacks and GPT-5.6 on the same export timeline.
Jun 30, 2026
After Boris Cherny and Peter Steinberger made "loop engineering" viral, Andrew Ng reframes it for 0-to-1 products: an inner coding loop, a developer steering loop, and an outer user-feedback loop — each running on a different clock.
Jun 29, 2026
For the first time, more U.S. businesses on Ramp pay for Anthropic than OpenAI — 34.4% vs 32.3% in April 2026, with Anthropic quadrupling share in a year while OpenAI grew 0.3%. The viral X thread tied it to loop engineering and Dario Amodei's claim that some Anthropic engineers barely write code anymore. Here is what the index actually counts, what it does not, and why workflow beats chat.
At Code with Claude Tokyo in June 2026, Anthropic shipped three production-oriented upgrades that turn Claude from a chat interface into scheduled, credentialed, parallel infrastructure—and the developer discourse on X framed the same week as a shift from prompt engineering to loop engineering.
@claudeai summarized the launch:
New from Code with Claude Tokyo: scheduled deployments and environment variables in vaults are in public beta in Claude Managed Agents, and dynamic workflows in Claude Code are generally available. Agents now run on a schedule, use your tools securely, and take on bigger jobs.
On June 11, @ClaudeDevs reiterated both Managed Agents features for developers building on the Claude API:
We've just added two new Claude Managed Agents features: 1. Scheduled deployments — run tasks on a schedule. 2. Environment variables — expose vault credentials for CLIs as environment variables.
Onboard from Claude Code with /claude-api managed-agents-onboard — covered in our Claude Code commands reference.
TL;DR
| Feature | Status | What it does |
|---|---|---|
| Scheduled deployments | Public beta (Managed Agents) | Cron-fired agent sessions—daily reports, compliance scans, monitoring |
| Vaults (env vars) | Public beta (Managed Agents) | API keys as opaque placeholders; injected at network egress |
| Dynamic workflows | GA (Claude Code) | Parallel subagent orchestration for large codebase jobs |
| Philosophy shift | Industry-wide | Build systems that prompt themselves; verify the right work |
An Anthropic engineer quote circulated widely on X via @Rixhabh__:
You're not supposed to prompt Claude. You're supposed to build a system that prompts itself.
That matches what @ClaudeDevs said when Fable 5 launched:
We used to verify that Claude did the work right. Now we verify that it's doing the right work.
The Tokyo announcements are infrastructure for that second model:
| Old pattern | New pattern |
|---|---|
| Open Claude, ask once, leave | Scheduled deployment fires daily |
| Paste API keys into prompts | Vault holds secrets at egress |
| One agent, one thread | Dynamic workflow fans out subagents |
| Human drives every step | Human sets goal, schedule, rubric |
Thariq's Fable-edited launch video is the creative proof; Tokyo is the platform proof.
Scheduled deployments give a Claude Managed Agent a cron schedule and timezone. When the schedule fires, the agent starts a new session and completes its task—no scheduler for you to build or host.
From Anthropic's announcement:
Each time the schedule fires, the agent starts a new session and completes its task, with no scheduler for you to build or host.
| Use case | Cron pattern | Initial message |
|---|---|---|
| Weekly compliance scan | 0 20 * * 5 (Fri 8pm ET) | "Run the weekly compliance scan." |
| Daily engineering report | 0 9 * * 1-5 | "Summarize yesterday's PRs and CI failures." |
| Usage monitoring | Hourly / daily | "Flag customer usage surges for review." |
Anthropic documents manual runs via a run endpoint—test before committing to cron. Org limit: 1,000 scheduled deployments per organization (contact support for more).
API: Requires beta header managed-agents-2026-04-01. See scheduled deployments docs.
Managed agents connect through API calls, CLIs, and MCP. Vaults now store environment variables so CLIs authenticate without the agent ever seeing the secret.
How it works (vault docs):
NOTION_API_KEY) and allowed domains.Supported credential types:
| Type | Use case |
|---|---|
environment_variable | CLIs, SDKs, direct API calls |
mcp_oauth | MCP servers with OAuth |
static_bearer | Bearer-token MCP servers |
Compatible CLIs named by Anthropic include Browserbase, KERNEL, Notion, Ramp, and Sentry. Browserbase and KERNEL add browser capabilities to managed agents for the first time—agents can navigate the web alongside other tools.
Ramp stores credentials in vaults so a managed agent can monitor usage and customer conversations, flagging surges as they happen so the team can confirm whether activity is intended—ideal for pairing with scheduled deployments.
Dynamic workflows graduated from research preview to general availability at Tokyo. Claude Code can now generate scripts that run tens to hundreds of parallel subagents for jobs that do not fit a single thread:
Each subagent works independently; results are checked before merge; the workflow iterates until convergence. Progress persists across interruptions—jobs pick up where they left off.
Trade-off: Substantially higher token usage than a normal session. Anthropic recommends scoping the first workflow and confirming before large runs. Enable via ultracode in the effort menu or ask Claude to create a workflow directly.
This complements /batch and /loop patterns in the CLI—Managed Agents for cloud cron, Claude Code for local parallel orchestration.
@goyalshaliniuk and others on X reframed the same week: Claude is an ecosystem, not a chatbot—Cowork, Code, Managed Agents, MCP, plugins, and API.
Concrete production mention from Anthropic's materials: Rakuten uses managed agents for spreadsheet analysis—the kind of recurring, tool-heavy task scheduled deployments target.
This builds on May 2026's Dreaming, multiagent orchestration, and Outcomes betas. Tokyo adds when (schedule) and how safely (vaults) agents run in production.
GroK-summarized discourse and practitioner threads flag real constraints:
| Risk | Mitigation |
|---|---|
| Token cost on dynamic workflows / long schedules | Scope cron jobs; set budgets; review first runs manually |
| Wrong work done well | Outcomes rubrics, verifiers, human review of artifacts |
| Secret scope creep | Domain-allowlist vault credentials; audit vault access |
| Scheduled drift | Manual run tests; monitor session outputs |
Loop engineering does not remove humans—it moves them to system design and verification, as in Fable loop design.
Managed Agents (schedule + vaults):
user.messagemanaged-agents-2026-04-01Claude Code (dynamic workflows):
In Claude Code, run /claude-api managed-agents-onboard or ask to start onboarding for managed agents in Claude API.
Primary sources: What's new in Claude Managed Agents · @claudeai Tokyo announcement · Scheduled deployments API · Vaults API
Code with Claude Tokyo delivered the missing ops layer for agentic AI: cron schedules for recurring work, vaults for CLI/MCP secrets, and dynamic workflows GA for parallel codebase jobs. Together with Fable 5 and loop primitives, Anthropic's story is coherent—design the loop, store the credentials, schedule the run, verify the outcome.
Bookmark this alongside our managed agents deep dive and loop engineering guide when building production agent systems.
Feature availability, beta headers, and pricing reflect Anthropic announcements as of June 11, 2026. Verify claude.com/blog and platform docs before production deployment.