Claude Duet
Proactive cloud agent that checks connected work apps, prepares tasks and asks for approval before consequential actions.
Score calculation
(2 + 2 + 5 + 2 + 2 + 3) ÷ 6 = 2.7
6 of six dimensions rated. Unrated dimensions are excluded from the average.
Full scoring method ↗Setup details
Claude Duet research preview for invited US Claude Pro or Max users. Uses the Claude account’s memory, connectors and plan limits; agent browser and computer run in Anthropic cloud.
What fits your needs
Hosted personal-work agent with Anthropic’s Claude model; available by waitlist to US Pro/Max accounts during research preview.
Proactive work
Checks connected email and calendar at intervals, prepares drafts and longer work products, and continues tasks in the cloud when the app is closed.
See the evidence
Connected business tools
Uses apps connected to Claude, including Gmail, Calendar, Drive, Slack and selected business services.
See the evidence
Tradeoffs to expect
Preview limits
Waitlist access is US-only for Pro and Max; the agent uses plan limits, cannot switch models, and cannot yet be monitored or taken over in its browser.
See the evidence
How to switch
Connect and scope apps
Connect apps in Claude settings, review the connector permissions, and disconnect any app to stop future access; previously learned information remains until memory reset.
Practical questions
Approval gates
Duet waits for approval before sending messages, paying, signing documents or deleting; securities trades, moving money between accounts and accessing another person’s account remain disallowed even with approval.
Credentials and memory
Anthropic says passwords and tokens stay outside the agent’s reach. Duet shares Claude memory and connected-app context; disconnecting stops new access but does not erase learned data until reset.
Duet is described as an Anthropic cloud-computer and browser service; product-specific energy, facility electricity and resource-control reporting are absent.
See the evidence
Anthropic describes Duet’s dedicated hosted computer/browser, which establishes the product’s cloud operation. The reviewed docs do not quantify the service’s energy, identify electricity sourcing for the compute facility or offer workload resource controls tied to physical reductions; no impact is inferred.
1 + 1 reporting + 0 electricity + 0 controls = 2/10. This grades documented practices and transparency.
Task energy, serving model route, region/facility electricity and compute resource controls are not reported for Duet.
- Reporting1/3
- Anthropic describes a separate cloud computer and browser for Duet, establishing hosted operation but no task energy reporting.
- Electricity sourcing0/3
- The Duet cloud-computer description does not map execution to a named facility or disclose that facility’s electricity mix.
- Resource controls0/3
- The reviewed Duet sources provide no user-visible token, context or compute control documented as reducing physical resource demand.
Water disclosure
Water reporting has not been assessed for this choice.
Duet names Claude Opus 5.5; Anthropic discloses broad training-data categories but not named sources, training-data rights or release-specific creator remedies.
See the evidence
Anthropic’s Duet help page identifies Opus 5.5, whose Transparency Hub describes a proprietary mix of publicly available online information, public/private datasets, user data and synthetic data. It provides no named-source rights ledger; account training preferences are distinct from the training data used to train the model.
1 + 1 source transparency + 0 permission + 0 creator controls = 2/10, with the permission cap applied.
No complete source/license inventory or Opus 5.5-specific evidence of creator removal and retraining was found in the reviewed disclosures.
- Source transparency1/3
- Anthropic’s Opus 5.5 transparency entry describes a proprietary mixture of broad data categories without a named-source inventory; Duet’s help page names Opus 5.5.
- Documented permission0/4
- The disclosed broad data categories do not document an affirmative rights basis for the material training data.
- Creator controls0/2
- The reviewed model transparency material doesn’t show a training-data creator opt-out or removal-and-retraining process for Opus 5.5.
Duet uses a cloud computer and connected Claude context; credentials are isolated from the agent, and memory/access can be reset or disconnected.
See the evidence
Anthropic says Duet inherits Claude memory, skills and connected apps, stores task history and memory until deletion/reset, and runs its own cloud computer and browser. Its design keeps passwords and tokens outside the agent machine and adds an external approval/classifier layer, but this remains hosted processing.
5/10 reflects documented task approvals, isolated credentials and reset/disconnect controls, while the research preview remains cloud-hosted and inherits account-connected data.
Retention periods, region-specific processing, model-training application and account controls follow Claude plan terms and the research-preview settings.
Claude Duet is a closed hosted research preview using Claude Opus 5.5; no product runtime or model weights are published.
See the evidence
Anthropic identifies Claude Opus 5.5 as the Duet model and describes a private cloud agent/browser architecture. The cited materials do not make the runtime or model weights available for inspection or self-hosting, although the product has connectors and user controls.
2/10 reflects a managed, waitlisted cloud preview with a fixed model and no published source license or user-controlled deployment route.
The service implementation and full model training record are not exposed in the cited launch materials.
Anthropic publicly requires suppliers to follow a vendor code covering labor and human rights, but public worker-specific implementation, voice and outcomes are sparse.
See the evidence
Anthropic’s July 2026 Transparency Hub says suppliers must comply with a Vendor Code of Conduct covering labor and human rights and apply equivalent standards through their own supply chains; the Trust Center lists a Global Vendor Code of Conduct, but its text is access-gated in the public interface. This supports limited credit for a supplier standard, not a finding about annotator pay, exposure controls or actual enforcement. These findings concern the developer or operator. This product’s use in a particular deployment needs separate evidence.
1 + 1 pay & conditions + 0 worker voice & remedy + 0 evidence & follow-through = 2/10. This grades documented worker safeguards, not a measured rate of mistreatment.
The public code text, worker complaint outcomes, rates/pay, annotation supplier identities and workforce coverage were not accessible in this review; company model documentation doesn’t confirm current worker treatment.
- Pay & conditions1/3
- Anthropic states that its supplier code sets labor and human-rights requirements and cascades equivalent standards through vendor supply chains; the publicly listed code text is access-gated, so no specific working conditions or application are verified.
- Worker voice & remedy0/3
- No public worker-specific grievance channel, opt-out, worker survey or worker representation mechanism was established in the sources reviewed.
- Evidence & follow-through0/3
- The Trust Center lists a vendor code and security audits for vendors handling Anthropic data, but no accessible evidence of labor audits, worker remediation or outcomes was found.
Anthropic reported extensive, mission-critical classified use in military and national-security workflows in February 2026, including intelligence analysis and operational planning, while the current contract status and any targeting/combat-intelligence use are not established.
See the evidence
Anthropic’s Feb. 26, 2026 statement says Claude was extensively deployed in classified Department of War and national-security settings for intelligence analysis, modeling and simulation, operational planning and cyber operations. The same statement says Anthropic had not objected to particular operations ad hoc and that lawful foreign-intelligence use was supported, while opposing mass domestic surveillance and fully autonomous weapons. This confirms broad defense enablement and named military workflow use, but does not identify target selection, strike decisions or combat-intelligence support. The statement reports the DoW was threatening offboarding; whether the deployment/contract continued by the October 2026 review date is not publicly established in the sources reviewed. These findings concern the developer or operator. This product’s use in a particular deployment needs separate evidence.
1 + 1 use restrictions + 1 enforcement & oversight + 2 relationship disclosure = 5, capped at 3/10. Known defense ties lower this rating; safeguards can improve it within the relationship’s cap.
The public statement does not enumerate active task orders, system versions, unit-level deployments, operational outcomes, or independent audit results. DoW supply-chain risk litigation and court orders make access status time-sensitive; the company's current page describes the status as of its stated dates.
- Use restrictions1/4
- Anthropic says it opposed mass domestic surveillance and fully autonomous weapons in its DoW contract discussions, but supports lawful foreign intelligence and partially autonomous weapons; the statement reports the DoW sought broader any-lawful-use terms.
- Enforcement & oversight1/3
- Anthropic states that it has safeguards and resists certain uses, but the reviewed statement provides no independent military-use review, published enforcement or remedy outcomes.
- Relationship disclosure2/2
- Anthropic names classified deployments and use categories and reports a dispute and possible offboarding; it does not disclose actual missions, current use-level limits, or post-dispute contract status.
Anthropic reported mission-critical classified use across multiple military workflows, but the source doesn’t confirm target selection, strikes, or combat intelligence; broad-defense cap applies. Current post-dispute contract status is unknown. The relationship limits this grade to 3/10.
Military rubric ↗Anthropic is not named in the BNC consumer guide or No Tech campaign reviewed.
See the evidence
The official BNC guide and No Tech campaign list named corporate targets; Anthropic does not appear in the reviewed target lists. This limited check is not an endorsement and doesn’t show relationships with cloud or government customers.
This is limited to the two official BNC campaign sources; it does not cover every local campaign, supplier, investment, or future change.
All sources
- Introducing Claude Duet ↗
- Get started with Claude Duet ↗
- Anthropic Consumer Terms ↗
- BNC consumer boycott and pressure guide ↗
- BNC No Tech campaign ↗
- Claude Duet Safety, Privacy, and Security ↗
- Anthropic Transparency Hub ↗
- Anthropic use of personal data in model training ↗
- Official source repository or product page ↗
- Official license or documentation ↗
- Anthropic consumer model-training policy, including Claude Code ↗
- Anthropic Department of Defense prototype agreement ↗
- Claude Code provider and network requirements ↗
- Anthropic commercial model-training policy ↗
- Stanford CRFM 2025 Anthropic transparency assessment ↗
- Claude 3 Model Card ↗
- Anthropic Inbound Services Agreement ↗
- Where things stand with the Department of War ↗
- Anthropic: expanded Amazon compute agreement, April 2026 ↗
- LLM gateway configuration ↗
- CLI reference ↗
- Other LLM gateways — Claude Code Docs ↗
- Dario Amodei on the Department of War discussions ↗
- Countering misuse of AI: September 2026 ↗
- Claude for Government ↗
- Anthropic Transparency Hub: Voluntary Commitments ↗
- Anthropic Trust Center: Global Vendor Code of Conduct ↗
- Statement from Dario Amodei on our discussions with the Department of War ↗