Claude Duet: Work That Continues While You Step Away, with Decisions Still to Make

Checked October 27, 2026. Based on official announcements and help documentation. MSL has not operated Claude Duet or measured its performance.

The appealing idea behind Claude Duet is not simply another way to get an answer. It is a different handover: work continues while you step away, and the decisions that need you come back later. Availability and operating limits matter before that idea becomes a production plan.

What changed

Anthropic announced Claude Duet’s research preview on October 21, 2026; Ledge.ai covered it on October 23. The official announcement describes a proactive agent that works through connected apps and continues on its own cloud computer and browser after you close your device. Account checks happen at intervals, rather than representing uninterrupted monitoring.

Availability comes before the workflow

The official help page currently requires a US Claude account, a Pro or Max plan and a waitlist invitation. Team and Enterprise access is not available yet. These sources do not establish a general release date for Japan.

The preview is included in Pro and Max without an additional fee, but shares the plan’s limits with ordinary Claude use. Background work counts toward those limits. An assistant continuing in the cloud is therefore not an unlimited service. I would not change a subscription solely on the assumption that immediate access is guaranteed.

For publishing, I would start before the publication decision

My first candidate would be preparation around editorial work: identifying which unanswered conversations require a decision, locating public material before a meeting, or bringing overlapping deadlines to an editor’s attention. These are MSL’s proposed uses, not tasks we have successfully run in Duet.

I would judge the result by three things: which source was consulted, what remains unconfirmed, and who must make the next decision. A polished report that obscures those details can create more work when the editor returns. A shorter handover that exposes them may be more useful.

I would keep normal communication routes and project tracking in place. A system that checks periodically and can misjudge urgency should not become the only place where a time-sensitive client message can be noticed.

Approval is part of the handover

The announcement and help page describe approval before actions such as sending messages, paying, signing or deleting. The October 23 safety explanation adds detail about approval mechanisms and a separate automated check outside the working model. These are descriptions of product safeguards, not evidence that errors are impossible.

For a publishing team, preparing a draft and authorising publication remain distinct decisions. But approval also needs to be usable. If reviewing a request requires reconstructing a long history every time, the work has merely moved back to the editor. I would want a concise account of the proposed change and the evidence behind it.

Disconnecting is not the same as forgetting

The safety documentation says disconnecting an app stops subsequent access, while previously learned information remains until memory is reset. That makes the end of a project another decision point: review account access, conversation history and memory as separate parts of the relationship.

I would not connect confidential project material first and work out the rules afterwards. The useful starting question is what information the task actually needs, and whether its owner has approved that use.

What MSL would adopt or defer

I would defer relying on Duet for a Japan-based production workflow under the current regional and invitation requirements. If access conditions change, I would consider public-information preparation first. I would then examine source traceability, how unresolved decisions return to the editor, and whether background use competes with the rest of the team’s Claude work.

More output alone would not establish value. My adoption criterion is a better handover in both directions: work that can be clearly delegated before stepping away, and results that are easy to assess on return.

Sources and review date

• Introducing Claude Duet, October 21, 2026.
• Get started with Claude Duet, official help.
• Claude Duet Safety, Privacy, and Security, October 23.
• Discovery: Ledge.ai coverage, October 23.

All checked October 27, 2026. Research-preview regions, eligible plans, features and limits may change. Confirm current official conditions before applying or changing a subscription.