Claude Scheduled Agents and Vault Credentials: What Anthropic's New Autopilot Features Mean for Your Team

TL;DR

Anthropic just shipped two features that change what Claude Managed Agents can do: scheduled deployments and vault credentials. In plain language: your AI agents can now run on autopilot — on a schedule you set, without anyone pressing a button — and they can securely log into your other tools without anyone sharing passwords. Both features are in public beta now. Here's what they are, why they matter, and what your team should do about it.

What Are Claude Managed Agents?

A quick refresher: Managed Agents are AI workers you configure once and let run independently.

Claude Managed Agents launched earlier this year as a way to set up AI agents that do real work on their own — not just answer questions when asked, but actively complete tasks. You define what the agent should do, what tools it can use, and what information it needs. Then you deploy it, and it runs.

Think of a managed agent like an employee with a very specific job description. You tell it: “Monitor these customer support tickets and flag anything that mentions billing errors.” Or: “Read every new contract that comes in and summarize the key terms.” The agent does the work. You review the output.

Until now, though, managed agents had two big gaps. First, someone had to start them — either a person pressing a button or a developer writing code to trigger them. Second, if the agent needed to connect to another system (your CRM, your project management tool, your email), someone had to figure out how to pass credentials around without exposing them. These two gaps kept managed agents stuck in “impressive demo” territory for a lot of teams.

That's what the June update fixes.

Scheduled Deployments: Your AI Agent Runs on a Clock

Set a schedule. The agent runs automatically. No developer needed.

A scheduled deployment is exactly what it sounds like: you give your managed agent a schedule, and it runs at those times without anyone doing anything. Every morning at 7 AM. Every Friday afternoon. Every hour during business hours. Whatever you need.

Each time the schedule fires, the agent starts a fresh session and does its job from start to finish. When it's done, the results are there waiting for you.

Here's why this is a bigger deal than it sounds:

Before: If you wanted an AI agent to do something every morning — say, pull yesterday's sales numbers, compare them to targets, and send a summary to the team — someone on your technical team had to build a scheduler. They'd need to set up a server, write a cron job (a programmer's term for a timed trigger), handle error logging, manage uptime, and maintain the whole thing. Most companies with 20–200 employees don't have the engineering capacity for this.
Now: You configure the agent, set the schedule, and click deploy. Anthropic runs the infrastructure. You don't need to build anything, host anything, or maintain anything.

This is the difference between “we could theoretically automate this” and “it's automated, and it took 20 minutes to set up.”

What Scheduled Agents Actually Look Like in Practice

Five examples that translate directly to work your team is doing manually today.

1. Daily business digest

A scheduled agent runs every morning at 6:30 AM. It pulls data from your CRM, your support inbox, and your project management tool. By the time your team opens their laptops, there's a summary waiting: new leads from yesterday, support tickets that need attention, project milestones that are due this week. Nobody compiled that report. It just appeared.

2. Weekly compliance scan

Every Friday at 4 PM, an agent reviews the week's contracts, invoices, or transactions against your compliance checklist. It flags anything that looks unusual — missing signatures, terms that differ from your templates, amounts that fall outside normal ranges. Your compliance person reviews the flags on Monday instead of spending Monday doing the scan manually.

3. Nightly data sync and cleanup

An agent runs every night at midnight. It checks your CRM for duplicate contacts, updates records that have become stale, and reconciles data between systems. The kind of database hygiene that everyone knows should happen but nobody has time to do — handled automatically.

4. Recurring client reports

If you send monthly reports to clients — marketing performance, financial summaries, project updates — a scheduled agent can generate the first draft on the same day each month. It pulls the data, formats the report, and puts it in your review queue. You edit and send. The two hours you used to spend assembling the raw report? Gone.

5. Inventory and operations monitoring

An agent checks stock levels, supplier lead times, or system health every few hours. When something crosses a threshold you've defined — stock below reorder point, a supplier delay, an error rate spike — the agent creates an alert and, optionally, starts the response process. You're not checking dashboards. The agent is checking for you.

Vault Credentials: Your Agent Can Log In Without Seeing the Password

Vault environment variables let agents access your tools securely — without exposing API keys or passwords to the AI model itself.

This is the second half of the update, and it's just as important as scheduling — even if it sounds more technical.

Here's the problem it solves: most business tools require some form of login. Your CRM has an API key. Your email system has credentials. Your accounting software has a token. If you want an AI agent to interact with any of these systems, it needs those credentials.

The old way to handle this was messy. You'd either paste credentials into the agent's configuration (risky — anyone with access to the agent could see them) or build a custom integration layer (expensive and time-consuming).

Anthropic's vault credentials work differently:

You store the credential in a vault. Think of it like a lockbox. The credential goes in, and a label goes on the outside.
The agent gets the label, not the key. When the agent runs, the credential is injected into its environment at the last moment — just long enough for the tool to authenticate. The AI model itself never sees the actual credential. It knows it has access to “CRM_API_KEY” but it cannot read, copy, or output the value.
Access is controlled by your admin. Your admin decides which agents get which credentials. Revoke a credential, and every agent that used it loses access instantly.

Why does this matter for non-technical teams? Because it means you can give an AI agent access to your real business tools — your actual CRM, your real accounting system, your production email — without the security risk of sharing passwords with a piece of software. Your IT team or admin sets it up once. The agents use the access. Nobody's credentials are floating around in a configuration file somewhere.

Why This Update Matters More Than It Looks

Scheduling + secure credentials = the difference between an AI demo and an AI employee.

Here's the honest truth about where most companies are with AI agents right now: they've seen demos. They've maybe built a proof of concept. But very few have AI agents doing real, recurring work in production — meaning work that actually runs every day, touches real systems, and produces results that people depend on.

The reason isn't that the AI isn't capable enough. It's plumbing. Specifically, two pieces of plumbing:

Who starts the agent when nobody's around? If a human has to trigger every run, you don't have automation — you have a tool that requires a babysitter. Scheduled deployments fix this.
How does the agent authenticate to real systems without leaking credentials? If you can't securely connect the agent to your CRM, your email, your database, then the agent can only work with data you manually feed it. Vault credentials fix this.

Together, these two features remove the biggest practical blockers that have kept AI agents in pilot mode. They don't make the AI smarter. They make it deployable.

The analogy I keep coming back to: imagine you hired a brilliant new team member, but they could only work when you stood next to them and they couldn't log into any of your company's systems. That's what managed agents were before this update. Now they can work on their own schedule and access the tools they need. That's a fundamentally different proposition.

What This Costs and Who Can Use It

Available now in public beta for Claude for Work (Team) and Enterprise plans.

Both features — scheduled deployments and vault credentials — are in public beta as of June 2026. They're available on Claude for Work (Team) and Enterprise plans. If your organization is on one of these plans, your admin can start configuring scheduled agents today.

Key details:

Limit: Up to 1,000 scheduled deployments per organization (contact Anthropic support if you need more).
Control: You can pause, resume, or archive any scheduled deployment at any time. You can also trigger manual runs on demand — useful for testing before you set a schedule.
Monitoring: Each run produces a session log, so you can see exactly what the agent did, what data it accessed, and what output it produced.
No infrastructure required: Anthropic hosts and runs the scheduled agents. You don't need servers, containers, or DevOps knowledge.

If you're on a Claude Pro or Max individual plan, these features aren't available yet. Managed agents are currently a team and enterprise feature. If your company doesn't have a Claude for Work plan, this might be the reason to get one.

How This Connects to Other Recent Claude Updates

Scheduled agents are part of a larger pattern: Claude is becoming an operating system for business automation.

If you've been following Anthropic's releases over the past few months, you'll notice a pattern. Each update adds a layer that makes AI agents more practically useful in real business settings:

Managed Agents (early 2026): Agents that can be configured to do specific tasks independently.
Memory (April 2026): Agents that remember what they've learned across sessions and share knowledge with each other.
Dreaming and Outcomes (May 2026): Agents that review their own past work, learn from mistakes, and grade their output against a quality standard.
Multiagent Orchestration (May 2026): A lead agent that delegates work to specialist agents working in parallel.
Scheduled Deployments + Vault Credentials (June 2026): Agents that run on autopilot and securely connect to your real business tools.

Each piece on its own is useful. Together, they describe something that starts to look less like a chatbot and more like a digital workforce: AI workers that have memory, learn from experience, can manage teams of other AI workers, run on a schedule, and securely access your company's tools.

We're not there yet — there are still limitations, and human oversight is still essential. But the trajectory is clear, and it's moving fast.

What Your Team Should Do This Week

Three concrete steps to take advantage of this update.

1. Make a list of recurring manual tasks

Sit down with your team and identify the tasks that someone does on a regular schedule — daily, weekly, or monthly. Reports that get compiled every Monday. Data that gets checked every morning. Summaries that get written every quarter. Not everything on this list will be a good fit for a scheduled agent, but many will be. Focus on tasks that are predictable, repetitive, and time-consuming but not judgment-heavy.

2. Pick one task and build a scheduled agent for it

Don't try to automate everything at once. Choose one task — ideally something low-stakes with clear, verifiable output. A daily summary. A weekly data check. A nightly cleanup job. Configure the agent, set the schedule, and let it run for a week. Review the output. Adjust. This is how you build confidence in the system without risking anything important.

3. Talk to your IT admin about vault setup

If your scheduled agent needs to access other systems (it probably will), your admin needs to set up the vault credentials. This is a one-time configuration per tool. Once it's done, any agent you authorize can use those credentials securely. The sooner the vault is set up, the sooner your agents can do useful work across your actual business tools.

FAQ

Do I need to be technical to set up a scheduled agent?

You need to be able to describe what you want the agent to do in clear, specific language. The scheduling and deployment parts are handled through Anthropic's platform — you pick a schedule from a menu, not write code. The vault credential setup is typically done by an IT admin. Once that's in place, configuring new agents is straightforward for non-technical users.

Is this different from Claude Code Routines?

Yes. Claude Code Routines are scheduled tasks that run in Claude Code — Anthropic's developer tool. They're designed for software engineers and run code-oriented tasks. Scheduled managed agents are for broader business automation. They don't require a coding environment and can be configured for any type of business task — report generation, data analysis, monitoring, compliance checks, and more.

Can a scheduled agent access my email, CRM, or other tools?

Yes, through vault credentials and MCP connectors. Your admin stores the access credentials in a vault, and the agent can use them to connect to external services. The agent never sees the actual credentials — they're injected securely at runtime. Anthropic supports a growing list of integrations, and the MCP connector ecosystem adds more all the time.

What if the agent makes a mistake?

Every run produces a detailed session log showing exactly what the agent did. You can review these logs, adjust the agent's instructions, and rerun the task. Start with low-stakes tasks and review output before trusting the agent with anything critical. You can also pause any scheduled deployment instantly if something goes wrong.

How is this different from Zapier or Make?

Zapier and Make are rule-based automation tools. They do exactly what you tell them: “When X happens, do Y.” Claude scheduled agents can reason about ambiguous situations, interpret unstructured data, and make judgment calls. A Zapier automation can move a support ticket to a folder. A Claude agent can read the ticket, understand the customer's actual problem, draft a response, and flag it for human review if the issue is complex. They serve different levels of automation complexity.

Is my data safe with scheduled agents?

Managed agents run in sandboxed environments — meaning they're isolated from other agents and users. Vault credentials are encrypted and never exposed to the AI model itself. Session logs are stored securely within your organization's account. Anthropic's standard data handling policies apply: data from Team and Enterprise plans is not used to train AI models.

What does this cost on top of my existing plan?

Scheduled deployments are included in Claude for Work (Team) and Enterprise plans during the public beta. Each agent run consumes tokens as normal — you pay for what the agent reads and generates, just like any other Claude usage. There's no separate scheduling fee. Check your plan's usage dashboard to monitor consumption.

Want to set up your first scheduled agent this week? The Deployed Kickstart gets your team hands-on with Claude in a single day — including managed agents and automation workflows. The Partner program gives you ongoing support as new features like this ship, so you're always getting value from the latest Claude capabilities.