Skip to content

Claude Duet Guide: First Tasks That Actually Work

Claude Duet research preview is live. Join the US Pro/Max waitlist with the right email, wire only the connectors you need, and run three safe first tasks without torching your limits.

7 min readBeginner

End state you’re aiming for: Duet installed on phone or browser, two or three connectors live, and one background job that returns something you can approve – not a tour of menus.

Anthropic opened the Claude Duet research preview on October 21, 2026. Proactive agent, not a chat that waits for you. It pings first, keeps working on its own cloud VM after you close the app, and stops for approval before send, pay, sign, or delete (Anthropic’s announcement).

I mapped setup from the official help pages the evening it shipped so you don’t lose a day to the wrong email or a connector pile-on. Concrete next steps below.

Quick context: what you’re getting into

Standalone app on iOS, Android, and claude.ai during preview – separate from main Claude chat. Powered by Claude Opus 5.5. Memory, skills, and connectors carry over from your Claude account. US Pro and Max only, no extra preview fee, same shared usage pool.

As of October 2026 on Anthropic’s pricing page: Pro is $20/month, or $17/month if you pay $200 annually upfront. Max starts at $100/month (5×) or $200 (20×). Team and Enterprise: not in yet. Waves after waitlist – no public ETA.

Think of it less like opening a chat and more like texting a chief of staff who already sees your calendar and inbox.

Hands-on: get Claude Duet running and hand it work

Most of the win is the first clean handoff. Do these in order.

1. Join the waitlist with the right email

  1. Open the Claude Duet product page → Join the waitlist.
  2. Use the exact email on your US Claude Pro or Max account.
  3. Pick plan + phone type. Optional note on what you’d hand off first.
  4. Submit. Invite comes in waves – no fixed date.

Invite on phone: iPhone → TestFlight from the email; Android → Google Play tester flow, same address. Sign into Duet with the Claude account. A few minutes of lag after accept is normal per the get-started help article.

Pro tip: waitlist email, Claude login, and the Apple/Google account on the phone must match. Mismatch is a common lockout after invite. Fix the match before you file a support ticket.

2. Connect only what the first task needs

Duet inherits connectors you already set in Claude (Gmail, Google Calendar, Drive, Slack, QuickBooks, HubSpot, Docusign, Calendly, Stripe, plus Marketplace plugins – official materials cite 6,000+). Manage under Claude settings → Customize → Connectors. You start every link; you can cut them anytime.

Gmail + Calendar is enough for day one. Add HubSpot, Docusign, or Slack only when a prompt needs them. Deliverables land in Make; long-running jobs show under Tasks.

3. Three safe first messages (not the usual demos)

Talk to it like a person – text or voice – in the main thread. Keep real sends and money off-stage until you’ve watched a few approval cards.

Scan my calendar for the next 7 days.
List every double-booking or back-to-back block under 15 minutes gap.
For each conflict, propose 2 resolution options I can pick.
Do not move events or email anyone.
From connected HubSpot (or CRM notes in email if HubSpot is off),
list deals with no activity in 14+ days.
Draft a short internal status line and one external nudge per deal.
Keep drafts here. Do not send or change deal stages.
Check Docusign for envelopes waiting on me or stalled outbound.
Table: envelope name, age, who needs to act, risk if it slips a week.
Draft reminder copy only. Do not send, void, or sign.

Watch Tasks. Only you mark complete. Can’t approve right now? It finishes what it can and brings the approval back later – that’s how the help docs describe the loop.

Why these three: they force triage + draft-only muscle without touching the invoice-reminder / morning-brief patterns everyone else ships in screenshots. You still learn Make vs Tasks, connector scope, and the approval card UI.

Common pitfalls to avoid with Claude Duet

  • Usage burn: Background briefs and account checks (every few hours by design) hit the same Pro/Max five-hour session and weekly limits as normal chats, same rate. Big jobs – decks, models – cost more turns. Continuous watching would empty the pool; spacing is the brake.
  • One-time reset easy to miss: On admission you get one full limit reset (session + weekly), only until November 30, 2026. Join late or ignore the banner and it’s gone.
  • Logo vs docs gap: Product-page ecosystems can flash Microsoft 365 and 1Password. Help center: Microsoft 365 isn’t available yet; 1Password sign-in is coming soon. Slack inside Duet has extra limits. Don’t plan a migration on logos.
  • Money and irreversible actions on day one: It asks before send/pay/sign/delete. Some moves stay blocked even with approval – securities trading, moving money between accounts. Link and Shop Pay use one-time virtual cards and still need your ok. Drafts first anyway.

Hard limits from the same docs: no model picker, no watch/take over of its cloud browser, gaps between checks are real, personal errands run weaker than work triage, no local-file access, and it only reads main Claude project work – it doesn’t edit those projects.

What results actually look like

Official framing is work triage across tools you already connected: conflict lists, stalled-deal drafts, envelope tables, longer jobs returning as files in Make while the phone stays in a pocket. Personal errands (tickets, one-off bookings) are the weak lane. It can still misread a thread or overrate urgency.

No public independent success-rate benchmark as of late October 2026. First week = calibration. Tighten what gets briefed, how often it pings, which connectors stay on.

Open question after the docs: how fast does “what needs you” judgment improve once thousands of users correct it in the wild?

When NOT to use this (yet)

Outside the US? Team/Enterprise? Free tier? Skip – waitlist path isn’t for you right now.

Need live browser takeover or a firehose inbox watched second-by-second? Checks are periodic on purpose. Banking moves, securities, or anything that must be perfect on the first unreviewed pass – keep that human. Pure Microsoft 365 stack today hits a real connector hole.

Long-form writing, coding sessions, one-off analysis: plain Claude (or Claude Code) is still the better surface. Duet earns its keep on ongoing attention across connected tools – not on single-shot prompts.

FAQ

Is Claude Duet free?

With US Pro or Max during the research preview, yes – no add-on fee. Background work still burns the same plan limits.

How do I get access faster?

You don’t skip the waitlist. Someone I talked through setup joined on the right Claude email, then stalled a full day because TestFlight was on a different Apple ID than the waitlist address. Match those three (waitlist, Claude, phone store), keep Pro/Max active, watch the invite waves. After the email lands, finish phone setup before you invent a “priority” request to support.

Will it send email or spend money without me?

No – not if the product behaves as documented. Misconception: “approval mode” means you can zone out. You shouldn’t. It shows the action and waits on send, pay, sign, delete. Link/Shop Pay purchases use one-time virtual cards and still need a yes. Prompt injection and bad thread reads aren’t solved problems; read every card.

Next action: submit the waitlist with your Claude email, then in regular Claude connect Gmail + Calendar (only). Day the invite lands, you’re one conflict-scan prompt away from a real Tasks entry.