Claude Duet Safety, Privacy, and Security
Anthropic launched Claude Duet into research preview, deploying an autonomous background agent that isolates user passwords, browser cookies, and payments.
By Dillip Chowdary • Oct 24, 2026 • Source: claude.com

At a glance
- Product
- Claude Duet, research preview
- Credentials
- Passwords and tokens never reach the model
- Blocked
- Banking transfers, account takeovers, securities trading
- Needs approval
- Deleting orders, sending payments, creating accounts
- Purchases
- Single-use cards generated through Stripe Link
In this post
Anthropic launched Claude Duet into research preview, introducing an autonomous cloud-based agent that runs across connected applications after users close the app. According to claude.com's report, the agent reads inboxes, drafts replies, and runs routines unattended. Anthropic built the system on three principles: screening drafts with a safety classifier, requiring user approvals for sensitive actions, and isolating credentials so passwords and tokens never reach the model.
This report details the architectural safeguards, credential isolation layers, approval policies, and memory retention controls governing Claude Duet. It is written for engineering leaders and administrators evaluating how autonomous cloud agents manage confidential communications, resist prompt injections, and control service permissions during unattended execution.
01What actually changed
Anthropic separated the reasoning engine from execution environments and credential storage. Unlike traditional assistants where session state mingles within context windows, Claude Duet delegates browsing to isolated virtual machines and routes service requests through external proxy layers.
Consequential operations like deleting orders, sending payments, or creating accounts are barred from auto-approval rules, requiring human confirmation regardless of past frequency. Furthermore, banking transfers, account takeovers, and securities trading remain completely restricted, blocking the agent from attempting them even when explicitly commanded by the user.
The system deploys a specialized safety classifier derived from the auto mode classifier in Claude Code, running parallel to the primary model. This classifier reviews drafted messages before dispatch, sorting data into two strict tiers.
Critical identifiers including government ID numbers, bank details, and account passwords face an absolute ban and will never be shared under any circumstances. Secondary private data such as personal medical notes or financial details require explicit consent, although user prompts requesting messages to specific recipients satisfy this rule automatically.
02How it works
Website code, cookies, and session tokens remain on the browser machine, preventing external scripts from accessing local storage or agent memory. Only page text and downloads return to the agent, where prompt injection defenses evaluate incoming content. Uploads receive the same sensitive-information scan as outbound text.
Website code, cookies, and session tokens remain on the browser machine, preventing external scripts from accessing local storage or agent memory. Only page text and downloads return to the agent, where prompt injection defenses evaluate incoming content. Uploads receive the same sensitive-information scan as outbound text.
The encrypted secret passes directly to the browser unopened, keeping plaintext credentials invisible to the model. An upcoming 1Password integration will soon support approving login requests inside the password manager. For purchases, the agent generates single-use cards through Stripe Link, letting users confirm merchant totals in their Link app and shielding primary card numbers.
The encrypted secret passes directly to the browser unopened, keeping plaintext credentials invisible to the model. An upcoming 1Password integration will soon support approving login requests inside the password manager. For purchases, the agent generates single-use cards through Stripe Link, letting users confirm merchant totals in their Link app and shielding primary card numbers.
Advertisement
Tech Pulse Daily
Get tomorrow's pulse first
Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.
03Why it matters now
Autonomous agents introduce security challenges because they execute tasks unattended without direct human observation. When agents read untrusted internet content, indirect prompt injection risks emerge because hidden directives can attempt to hijack execution.
Relying strictly on in-model alignment has proven inadequate to protect systems against malicious instructions. By isolating approvals, credentials, and message classification on external cloud infrastructure outside the reasoning engine, the architecture guarantees that malicious prompt payloads embedded in web pages cannot falsify approvals, forge permissions, or trick the model into revealing secrets.
Anthropic calibrated request frequencies to reserve confirmation prompts showing destinations, content, and recipients for consequential steps like spending funds or deleting files. Phishing risks are countered by confining authentication dialogues to native app interfaces during user-initiated sign-ins. Prompts never arrive via SMS, email, or third-party websites outside claude.ai, preventing attackers from deploying spoofed interfaces to harvest credentials.
Anthropic calibrated request frequencies to reserve confirmation prompts showing destinations, content, and recipients for consequential steps like spending funds or deleting files. Phishing risks are countered by confining authentication dialogues to native app interfaces during user-initiated sign-ins. Prompts never arrive via SMS, email, or third-party websites outside claude.ai, preventing attackers from deploying spoofed interfaces to harvest credentials.
04Who is affected
Disconnecting an application immediately revokes future access. However, information previously extracted remains in the agent's memory until cleared manually through settings. Claude Duet also inherits historical context from previous Claude chats, and deleting the primary account purges all stored task histories and agent memories permanently, giving users complete data lifecycle control.
Disconnecting an application immediately revokes future access. However, information previously extracted remains in the agent's memory until cleared manually through settings. Claude Duet also inherits historical context from previous Claude chats, and deleting the primary account purges all stored task histories and agent memories permanently, giving users complete data lifecycle control.
Enterprises tracking Claude Managed Agents will see familiar security patterns, particularly strict credential separation. Connected app credentials never enter the environment where the agent reasons; placeholder tokens sit there instead while an external proxy substitutes live credentials as requests dispatch.
Anthropic staff dogfood Claude Duet on their own accounts daily, testing background workflows against real-world operations. This internal testing provides operational data to refine the safety classifier, ensuring the model avoids sharing private personnel details like performance review discussions in broader team status recaps.
05What to watch
Users track agent activities through a centralized task list featuring dedicated pages for each workflow, allowing live adjustments while tasks execute. Because the classifier is actively learning during research preview, Anthropic noted it will occasionally flag benign content or miss sensitive details.
When flagged for containing unauthorized private data, Claude Duet can rewrite drafts to omit sensitive material before requesting user approval. Observers should track ongoing classifier updates as Anthropic balances sensitive information detection against unnecessary false alarms across everyday messaging tasks.
Key milestones ahead include direct 1Password integration, enabling credential approvals within the password manager without exposing secrets to the reasoning engine. Administrators should also monitor approval calibration tuning and auto mode enhancements as broader usage data arrives.
Non-negotiable boundaries will remain in effect: trading securities, moving funds between bank accounts, and accessing unauthorized third-party accounts remain completely forbidden even with user approval. Claude Duet outlines an operational framework for persistent autonomous agents, isolating credentials and sandboxing browser environments to execute tasks securely.
Frequently asked questions
Can Claude Duet execute stock trades or bank transfers if approved?
No, trading securities and moving money between bank accounts remain off-limits even with explicit user approval.
How does Claude Duet isolate user passwords and sign-in tokens?
Passwords are encrypted with single-use keys and sent directly to an isolated cloud browser machine without passing through the model. Connected app credentials never enter the agent machine, using token placeholders resolved by an external proxy.
What payment method does Claude Duet use for online purchases?
The agent uses one-time virtual cards through wallets like Stripe Link limited to specific merchants and amounts. Users verify the purchase details and grant final approval directly within the Link app.
What happens to stored memory when an application is disconnected from Claude?
Disconnecting an application halts new data collection immediately, but previously learned information remains in the agent's memory until manually reset in settings. Deleting the user's primary Claude account permanently purges all stored memories and task histories.
Sources
Author
Dillip Chowdary
Writes Tech Bytes coverage of AI, engineering, and the tools that actually ship. Editor of Tech Pulse Daily.
Related on Tech Bytes
Advertisement