How background work, connected context, and approval requests change the way developers and growth teams delegate.
A launch follow-up can stall without anyone forgetting their job. A customer replies in email, a deadline changes elsewhere, and the person responsible discovers the connection after their next meeting. Getting an AI to draft the reply is straightforward. Getting it to notice that a reply is needed creates a different engineering problem.
That is the problem behind Claude Duet. Its usefulness will depend on whether the attention it saves exceeds the effort required to check its work. For developers and growth teams, that makes context quality, interruption timing, and approval boundaries central to evaluating it.
What Is Claude Duet?
Anthropic opened Claude Duet’s research preview on October 21, 2026. The Claude Duet proactive AI agent works in the background and brings work back for attention. Access begins through a waitlist for US Pro and Max subscribers, with standalone iOS and Android apps and web access through claude.ai. It is included in those plans during the preview and shares their usage limits. Anthropic’s announcement describes the release and access conditions.
The familiar chat interaction starts when you decide what to ask. Duet adds another starting point: something in your connected work appears to need a response. That shifts part of the delegation problem toward deciding which signals deserve an interruption.
For a growth lead, an unanswered customer question might matter more than another campaign summary. For a developer, a useful handoff might be a prepared brief that makes an upcoming decision easier. The benefit depends on selecting the right work as much as producing the output.
How Claude Duet Works: From Context to Suggested Actions
What context does Claude Duet use?
Duet carries over memory, skills, and connected apps from your Claude account. It accepts text or voice messages and works on its own cloud computer. The product page describes an ongoing thread, morning briefs, and deliverables such as documents, decks, and dashboards.
For anyone delegating work, context needs an owner. Before handing over a launch task, identify which document contains the approved date and which conversation contains the latest customer commitment. Two accessible sources can still disagree.
A practical instruction would name the authoritative source and explain what to do with conflicts: prepare a draft, identify the disagreement, and ask before making a commitment. That gives the reviewer a concrete question to resolve instead of a polished answer built on an unstated assumption.
How suggested actions reach the user
Anthropic says Duet checks connected accounts every few hours and lets users adjust what they hear about and how often. Its cloud browser allows work to continue while their devices are off. The announcement explains this background workflow.
Periodic checks create a useful distinction between follow-up work and urgent operations. A delayed sales response might tolerate the interval. An incident escalation could require immediate delivery and a known response path. Keep those timing requirements explicit when choosing what to delegate.
Notification preferences also need business meaning. “Tell me about important messages” leaves importance undefined. A narrower instruction could prioritize customer commitments due today while collecting routine updates into a brief. You can then judge whether the interruptions match that intention.
Where user control fits
Duet is designed to present proposed messages, payments, signatures, and deletions for approval. The help center also distinguishes task tracking from completion: Duet can suggest that work looks finished, but only the user marks it complete. Anthropic’s getting-started guide documents these controls.
Treat approval as a decision about consequences. A grammatically correct email can still promise an unsupported delivery date. Before confirming it, check the recipient, commitment, and supporting evidence. Those details determine whether the action is appropriate.
A Hypothetical Workflow, Step by Step
Consider an illustrative launch follow-up workflow. This is a proposed delegation pattern, not a report of tested Duet behavior.
First, define a bounded assignment: prepare follow-ups for a named group of prospects using an approved launch brief. Specify that uncertain product claims should become questions for you.
Second, identify the source of truth. The launch brief should govern availability dates; the customer conversation should govern what that particular prospect asked. If they conflict, the draft should preserve the conflict for review.
Third, review a small batch of proposed replies. Check whether each one answers the actual question and whether any statement creates a new commitment. Similar-looking drafts can require different decisions when prospects have different expectations.
Fourth, approve only the replies you can substantiate. An unresolved engineering dependency should remain unresolved in the message rather than becoming a confident deadline.
Finally, compare the work against your original list. A smooth conversation is weak evidence of coverage. A record of which prospects were addressed, which remain blocked, and why gives you a basis for the next handoff.
This workflow makes delegation inspectable without assuming every draft will be correct.
Privacy, Permissions, and Practical Limits
The help center makes several consequential boundaries explicit. Disconnecting an app stops future access but retains memory of earlier conversations. Past-chat search follows Claude’s memory setting. You cannot watch or take over Duet’s browser during the preview, Microsoft 365 is unavailable, and Team and Enterprise plans are excluded. The documented limitations should shape the scope of a trial.
Access revocation and removal of remembered information therefore require separate consideration. If a workflow involves customer material, decide what information it needs before connecting accounts. A broad integration can expose more context than a narrow assignment requires.
Anthropic says Duet uses isolated credential handling and additional checks for sensitive information. These are vendor-described safeguards, not an independent guarantee. Its announcement outlines the protections.
The help center also acknowledges imperfect prompt-injection defenses. External content can attempt to redirect an agent, so a plausible draft still deserves scrutiny before an external action.
How to Decide Whether Claude Duet Fits Your Workflow
Start with work where a missed interval is tolerable and the result is easy to inspect. Brief preparation and draft follow-ups offer clearer review criteria than assignments such as “manage the launch.”
During a trial, record missed items, unnecessary interruptions, and corrections required before approval. Include the time spent reviewing. Background checks also consume shared plan limits, according to the product’s usage explanation, so delegation has a resource cost alongside the attention cost.
Expand the assignment when you can explain why the first one worked: its sources were clear, its decisions were bounded, and reviewing its output took less effort than preparing it yourself. That gives you a defensible reason to hand over the next piece of work.
Top comments (0)