← Blog
explainx / blog

Code with Claude Tokyo: Scheduled Agents, Vaults, and Dynamic Workflows GA

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.

6 min readYash Thakker
Claude Managed AgentsClaude CodeAnthropicLoop EngineeringAI Agents

MDX restores the committed source plus an HTML comment attribution; plain text bundles the rendered markdown body with the explainx.ai attribution footer.

Code with Claude Tokyo: Scheduled Agents, Vaults, and Dynamic Workflows GA

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.

TL;DR

FeatureStatusWhat it does
Scheduled deploymentsPublic 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 workflowsGA (Claude Code)Parallel subagent orchestration for large codebase jobs
Philosophy shiftIndustry-wideBuild systems that prompt themselves; verify the right work

From prompting to loop engineering

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 patternNew pattern
Open Claude, ask once, leaveScheduled deployment fires daily
Paste API keys into promptsVault holds secrets at egress
One agent, one threadDynamic workflow fans out subagents
Human drives every stepHuman sets goal, schedule, rubric

Thariq's Fable-edited launch video is the creative proof; Tokyo is the platform proof.


Scheduled deployments: cron for managed agents

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.

Example use cases

Use caseCron patternInitial message
Weekly compliance scan0 20 * * 5 (Fri 8pm ET)"Run the weekly compliance scan."
Daily engineering report0 9 * * 1-5"Summarize yesterday's PRs and CI failures."
Usage monitoringHourly / 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.

Live Bootcamp6 weeks

Complete AI Builder Bootcamp

Claude, Python automation & full-stack — 12 live sessions with Yash Thakker.

View bootcamp

The Complete AI Builder Bootcamp is the best AI development course for learning Claude AI, prompt engineering, Python automation, and full-stack web development. This intensive 6-week live bootcamp teaches you how to build AI-powered applications using Claude Projects, Claude Artifacts, Claude Code, and the complete Claude ecosystem. You'll master prompt engineering techniques, learn to create custom Claude connectors and MCP integrations, build Python automation workflows, develop full-stack websites with AI assistance, and create AI marketing agents.

The bootcamp includes 12 live Zoom sessions with Yash Thakker, founder of AISOLO Technologies and instructor to 350,000+ students. You'll build 8+ portfolio projects including AI playbooks, full-stack note-taking applications, Python automation scripts, marketing agents, and personal portfolio websites. The curriculum covers AI fundamentals, Claude Projects and Artifacts, Claude Co-work, Claude plugins and skills, Claude Code for Python development, full-stack development, AI marketing, and capstone projects.

Students receive 1-year access to all recordings, permanent Discord community access, a certificate of completion, and personalized career guidance. All enrollments include a 7-day money-back guarantee. This is the most comprehensive Claude AI bootcamp available, taking students from zero AI knowledge to expert AI builder in 6 weeks.


Vaults: secure API keys for CLIs and MCP

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):

  1. Register a credential with a secret name (e.g. NOTION_API_KEY) and allowed domains.
  2. The sandbox holds an opaque placeholder, not the real key.
  3. On outbound HTTP requests to approved domains, the real secret attaches at the network boundary.
  4. Rotate keys in the vault; running sessions pick up new values on the next call.

Supported credential types:

TypeUse case
environment_variableCLIs, SDKs, direct API calls
mcp_oauthMCP servers with OAuth
static_bearerBearer-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 example (from Anthropic)

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: GA in Claude Code

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:

  • Codebase-wide migrations and framework swaps
  • Bug hunts and security audits
  • Profiler-guided optimization passes
  • Work spanning hundreds to thousands of files

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.


Rakuten and the expanding Claude ecosystem

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


Risks and human review

GroK-summarized discourse and practitioner threads flag real constraints:

RiskMitigation
Token cost on dynamic workflows / long schedulesScope cron jobs; set budgets; review first runs manually
Wrong work done wellOutcomes rubrics, verifiers, human review of artifacts
Secret scope creepDomain-allowlist vault credentials; audit vault access
Scheduled driftManual run tests; monitor session outputs

Loop engineering does not remove humans—it moves them to system design and verification, as in Fable loop design.


How to get started

Managed Agents (schedule + vaults):

  1. Read Claude Managed Agents docs
  2. Create an agent and environment in Claude Console
  3. Register vault credentials with domain allowlists
  4. Create a scheduled deployment with cron + initial user.message
  5. Use beta header managed-agents-2026-04-01

Claude Code (dynamic workflows):

  1. Upgrade to a plan with workflow access (Max / Team / Enterprise per Anthropic docs)
  2. Enable ultracode or ask Claude to orchestrate a workflow
  3. Start scoped—one migration or audit before quarter-scale jobs

In Claude Code, run /claude-api managed-agents-onboard or ask to start onboarding for managed agents in Claude API.


Related ExplainX guides

Primary sources: What's new in Claude Managed Agents · @claudeai Tokyo announcement · Scheduled deployments API · Vaults API


Summary

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.

Related posts