Claude Connectors
Claude Duet Runs on 6,000 Connectors — the Approval Gate Is What Makes It Governable
On October 21, 2026, Anthropic opened a research preview of Claude Duet, a standing, proactive agent that checks a person's connected apps on its own schedule rather than waiting to be asked. It is the first product built to act continuously across the full Claude connectors catalog, which is exactly why the one setting it leans on hardest — the approval gate — is worth more attention than the feature list.
What shipped
Claude Duet is a standalone app — iOS, Android, and claude.ai — powered by Claude Opus 5.5. Per Anthropic's own product page, Duet “tells you what needs your attention each morning, takes tasks you hand it by message, and reaches out when one is done or needs your approval.” It checks connected apps on its own cadence, sends a morning brief, and keeps working on a task after a person steps away — a meaningfully different shape than a chat session that only acts the moment someone types a prompt. It is currently a research preview, gated behind a waitlist, and limited to Pro and Max subscribers in the United States; Team and Enterprise plans are not yet included.
The catalog underneath it quadrupled in four weeks
Duet does not bring its own integrations — it draws on the Claude Marketplace, which Anthropic opened on September 23, 2026 with more than 2,000 connectors and plugins from launch partners including Atlassian, Google, Microsoft, Notion, and Salesforce, all built on the Model Context Protocol (MCP) and Agent Skills. By the time Duet launched less than a month later, Anthropic's own product page put the number at “more than 6,000 connectors and plugins,” including Gmail, Google Calendar, Slack, Notion, Microsoft 365, QuickBooks, DocuSign, HubSpot, Gusto, Canva, Stripe, and Shopify. That growth rate matters for the governance question: a catalog quadrupling in weeks means the set of systems an agent could plausibly touch is moving faster than most businesses' access-review cycles.
The approval gate, specifically
Anthropic built a specific control into Duet rather than leaving it to a general permissions screen: per the product page, “Claude Duet asks you before sensitive operations like sending messages or paying,” and those approval decisions are processed on what Anthropic describes as a private cloud computer dedicated to the session, specifically to protect sensitive details from being exposed in the course of approving an action. That is the load-bearing design choice in the whole product. A proactive agent that checks six thousand connectors' worth of systems on a schedule is only as safe as the set of actions it is willing to take without asking first — and Anthropic has drawn that line at the actions with the most externally visible or financially consequential blast radius: outbound messages and payments.
What a business should scope before anyone joins the waitlist
Duet is a consumer research preview today, gated to individual Pro and Max accounts, not a Team or Enterprise rollout — so no admin console decision is on the table yet. But the pattern it previews is the one every connector-heavy Claude deployment eventually runs into, and it is worth scoping in advance rather than after an employee has already joined the waitlist on a personal account connected to work systems:
Which connectors a standing agent gets, versus a one-off session
A connector that is safe for a person to invoke deliberately, once, inside a chat session is not automatically safe to leave authorized for an agent that checks it unprompted every few hours. The allowlist for a proactive agent is a narrower, more deliberate list than the allowlist for ad hoc Claude use.
Who reviews the approval queue
The approval gate only works as a control if a specific person is actually looking at what it surfaces — a message about to be sent, a payment about to go out — and not reflexively tapping approve. That review responsibility needs an owner before a proactive agent is connected to anything consequential.
Whether a personal account is quietly becoming a business access point
Duet ships today on individual Pro and Max subscriptions. An employee linking a work Gmail, calendar, or QuickBooks account to a personal research-preview app is a real possibility the moment the waitlist opens wider — and it is exactly the kind of shadow-AI exposure a business should be looking for before it is looking for it after the fact.
Still the same protocol underneath
Nothing about Duet changes the plumbing: every connector in the Marketplace, whether invoked by a person mid-chat or checked by a standing agent on a schedule, runs on the Model Context Protocol, the open standard Anthropic introduced and now co-stewards, documented at modelcontextprotocol.io. A business standardizing its own connector decisions on MCP is standardizing on the same substrate Duet itself is built on, which keeps governance choices — who connects what, under which credentials, reviewed by whom — portable across whatever surface the business ends up using, whether that is chat, Claude Code, or eventually a proactive agent like Duet. Anthropic's published enterprise controls at Claude for Enterprise and its security posture at the Trust Center are the artifacts a security review cites once a proactive agent is actually on the table for a Team or Enterprise plan, not a feature announcement.
Where Skoor fits
Skoor implements and manages Claude on business devices, and the connector-scoping work this post describes is the standing part of that engagement: role-based permission profiles with connectors allowlisted per role, continuous drift scoring that catches a profile violation inside a committed review window, and an audit trail of what was connected, by whom, under what profile — the same discipline that will matter the day a proactive agent like Duet reaches a Team or Enterprise plan. The current catalog of what we cover is public at Skoor Solutions.
Learn More
Connect Claude to your stack — governed
Role-based connector allowlists and an audit trail, scoped before a standing agent ever gets a seat.
See how Skoor implements Claude