# Whose memory does Claude Duet run on? One person's, and a business needs more > Claude Duet carries over one Pro or Max account's memory and connectors. What a business knows needs a home the business owns, with members, not one login. Source: https://baalda.com/blog/claude-duet-memory Site: Baalda, https://baalda.com Published: 2026-10-22 **Short answer.** Claude Duet runs on one person's Claude account. Opened as a research preview on 21 October 2026 for US Pro and Max subscribers, it carries over that account's memory, skills and connectors, and Team and Enterprise plans are not included yet. What the business knows belongs in notes the business owns, which every member's agent can read. Claude Duet is Anthropic's agent that works for you while you are not looking at it. The question it raises for a business is not whether the agent is good. It is whose account the agent's memory belongs to, and what happens to that memory when the business has more than one person in it. ## What is Claude Duet? Anthropic opened Claude Duet as a research preview on 21 October 2026. Its announcement calls it "a new app where Claude works as a proactive agent": it sends a morning brief, checks your connected accounts every few hours, works on tasks in its own virtual machine in the cloud so your laptop does not have to be on, and waits for your approval before it sends a message, makes a payment, signs a document or deletes anything. As of 22 October 2026 the facts that matter here are these, all from Anthropic's own pages: - It is built "for professionals and small business owners". - It is waitlist-only, "starting with US Pro and Max subscribers". The product page says "Team and Enterprise plans are not included yet", and the help article says Anthropic plans to bring it to those plans later. - It runs on Claude Opus 5.5, and you cannot pick another model. - It can use "the over 6,000 connectors and plugins in the Claude Marketplace", with Gmail, Slack, QuickBooks, Stripe, Gusto, HubSpot and Docusign among the examples. - During the preview it is included in Pro and Max at no extra cost and shares the plan's usage limits, background check-ins included. ## What does Claude Duet remember, and where does it keep it? It remembers what your Claude account remembers. The announcement says Duet "carries over your memory, skills, and connected apps from your Claude account", and the help article says they "are there from your first message". The help article fills in the edges. Duet can search your Duet chats and your Claude chats outside of projects, controlled by the same Search and reference chats setting in Settings, Memory. It "can read your work in Claude but can't change it", and it cannot see all of your projects. Separate channels inside Duet share one memory. Disconnecting an app stops Duet reaching it from then on, but "memory of past information from earlier conversations is kept." What the help article does not give you is a way to view, edit or export Duet's memory, and it says nothing about what happens to that memory if the account later moves to a Team plan. Those may well exist or arrive. As of today they are not documented, so this post does not assume either way. ## Why is one person's account the wrong home for what a business knows? Think about who Duet is aimed at. A small business owner connects Gmail, QuickBooks and HubSpot, and within a few weeks the agent knows which supplier is late every month, which client pays on 60-day terms, and why the March invoice was split in two. That is real operating knowledge, and it now sits in the owner's personal Pro or Max account, because that is the only kind of account Duet runs on. The bookkeeper cannot see it. The new hire cannot read it on their first day. If the owner hands the business on, or simply stops paying for Max, there is no documented route for that knowledge to go with the business. The agent was the right worker. The account was the wrong filing cabinet. This is the problem [Baalda](https://baalda.com) is built for. Baalda is a team second brain made of plain markdown files on each member's own disk, edited by several people at once over a CRDT, and served to AI agents over MCP. The part that answers Duet is not the markdown, though. It is that a synced vault belongs to the business, not to whoever signed up first. ## What changes when the business owns the memory? In Baalda a synced vault is an organisation on the server, and the people in it are its members, each with a role: | Role | What it can do | |---|---| | Owner | everything, including billing, deleting the vault and resetting anyone's access | | Admin | manage members, access and the vault's settings | | Member | read and write what they have been given | A small business's vault might look like this, with access set per folder: ``` Clients/ everyone, can edit Suppliers/ everyone, can edit Decisions/ everyone, can view Payroll/ owner and bookkeeper only ``` Three properties follow from that, and none of them depend on any one person's subscription. **People join the knowledge, not the other way round.** The owner invites the bookkeeper by email with a role and an access level. What a new member can see of the notes that existed before them is set by the vault's New members level at the moment they join, and changing that level later does not reach back to them. **People leave and the knowledge stays.** Removing someone ends their membership. Their readable set empties at once rather than when a token expires, every document they held is disconnected, and their local copies of what they lost are moved to that device's trash. The notes themselves remain in the vault for everyone else. **An agent reads as a person, not as the business.** Every MCP connection sees the same tools, `read_note`, `search_notes`, `append_note` and the rest, but what a call may touch is decided by the per-folder access of the person the token belongs to. The bookkeeper's agent can read `Payroll/`. A contractor's agent cannot, and neither can the contractor. So the line between Duet and the vault is clean. Duet works for one person. The vault is what that person's work leaves behind for everyone else. If the concepts are new, [what a team second brain is](/blog/team-second-brain) covers the category. ## Can Claude Duet read a Baalda vault today? Not that anyone can confirm as of 22 October 2026. This is the honest gap and it matters. Anthropic's Duet pages describe connectors from the Claude Marketplace and "the apps you've already connected in Claude". None of the three pages mentions MCP or custom connectors. Claude itself does take a remote MCP server as a custom connector on paid plans, which is how [Baalda connects to Claude Desktop](/blog/claude-desktop-second-brain), but whether a custom connector you added in Claude carries into Duet is not stated anywhere, and a guess is not worth writing down as a setup step. Until that is documented, the working pattern is a step by hand: when Duet produces something the business should keep (a supplier's new terms, a client decision, the reason behind a refund), the owner or the next Claude session with the Baalda connector writes it into the vault. That is friction, and it is fair to say so. ## Where is Baalda the wrong answer? Baalda has no proactive agent. Nothing in it checks your inbox every few hours, writes a morning brief, pays an invoice or runs while you sleep, and it does not connect to 6,000 services. If what you want is the work done, Duet is the product and a vault does not replace it. There is also no mobile app yet (macOS, Windows and Linux only), while Duet runs on iOS and Android. And a vault only holds what someone writes into it. A business whose owner never moves anything out of the agent's memory has gained nothing from owning the folder. ## How should a small business run Duet and a vault together? Give each the job it is good at. Duet is the worker for one person: it watches, drafts, chases and waits for approval. The vault is the record for the business: clients, suppliers, decisions and how things are done, in files the business owns and every member's agent reads as that member. This is the same split OpenAI's dots raised on 29 September 2026, which [the post on where agent memory lives](/blog/shared-agent-memory-whose-disk) covers from the editing side. Duet makes the other half of it plain. A memory inside one person's account, however good the agent on top of it, is still one person's memory, and a business is never one person for long. ## FAQ ### What is Claude Duet? A proactive agent app from Anthropic, opened as a research preview on 21 October 2026. It sends a morning brief, checks connected accounts every few hours, works in its own cloud virtual machine, and asks for approval before it sends a message, makes a payment, signs a document or deletes anything. As of 22 October 2026 it is waitlist-only for US Pro and Max subscribers, runs on Claude Opus 5.5, and is available on iOS, Android and claude.ai. ### Is Claude Duet available on Team or Enterprise plans? Not yet. Anthropic's product page says "Team and Enterprise plans are not included yet", and the help article says it plans to bring Duet to those plans later. It gives no date, and it does not say what happens to a Pro or Max account's Duet memory if the account moves to a Team plan. ### Can Claude Duet connect to a Baalda vault over MCP? Not that anyone can confirm as of 22 October 2026. Anthropic's Duet pages describe Marketplace connectors and apps you have connected in Claude, and none of them mentions MCP or custom connectors. Claude itself accepts Baalda as a custom connector at /api/mcp on paid plans, but whether that carries into Duet is not documented. ### What happens to a business's notes in Baalda when someone leaves? They stay with the vault. Removing a member ends their membership, their readable set empties at once rather than when a token expires, every document they held is disconnected, and their local copies of what they lost are moved to that device's trash. Everyone else keeps the notes, and an agent connected with the departed person's token reaches nothing.