Personal AI Agents Compared: Claude Duet, Dots, Muse and Grok Bot

Updated October 23, 2026. Start with the work you want to hand over and the apps you already use. Our recommendations focus on workflow fit, connected tools and access. Availability can depend on your country, subscription and workspace settings.

The sections below explain the strengths and limitations behind this overview. If your main need is automatic time blocking or appointment booking, our AI calendar and planner comparison covers tools built specifically for those jobs.

A personal agent can take an ongoing responsibility, use connected tools and continue between conversations. You might ask it to prepare a morning briefing, track a research project or assemble a weekly content plan. Its usefulness depends on the information it can access and the actions you allow.

Background work also needs somewhere to run. A cloud agent can work while your laptop is closed; a task that needs a file or app on your own computer may have to wait until that computer is available. Usage allowances, expired connections and requests for approval still shape what gets done. See our guide to agentic calendar assistants for examples of tools turning an instruction into calendar actions.

Anthropic’s Claude Duet introduction puts professional work at the centre: briefings, business administration and substantial deliverables such as research or financial models. Duet runs in the cloud and carries over the memory, skills and connectors you have already configured in Claude.

That continuity is its strongest attraction. A small-business owner could ask for a briefing before a customer meeting, then have Duet prepare a document using the connected business tools. Someone already working in Claude has less context to recreate.

• Pros: existing Claude context and connectors carry over; cloud work can continue with your devices closed; briefings and business tasks fit naturally into the experience.
• Cons: the research preview is limited to invited US Pro and Max users and shares the account’s usage limits. Team and Enterprise access is not yet included. Anthropic also describes personal errands as less developed than professional work.
• Our recommendation: start with Duet if you already rely on Claude and want help with the administrative work around clients, projects or a small business.

The Duet setup guide explains access, connected apps and when it asks for input. Treat its proactive briefings as a way to bring decisions to you, while keeping the important business decisions in your hands.

OpenAI describes Dots as agents that take on continuing responsibilities. A dot can coordinate work in separate threads, use its own cloud computer and draw on supported plugins connected to your account. It can also work through ChatGPT Work and Codex.

For example, you could give a dot responsibility for a product launch: collect research, track open questions and coordinate a document or coding task. The appeal is having a continuing point of contact as the project moves through different kinds of work.

• Pros: useful continuity across projects; cloud execution; coordination with Work and Codex; optional access to work on your own computer.
• Cons: access is rolling out by plan and region. Personal Pro availability excludes the EEA, UK and Switzerland, while business and workspace eligibility differs. Local-computer tasks need the computer online with the ChatGPT app open.
• Our recommendation: choose Dots if ChatGPT is already your workspace and your projects combine research, documents, data or software work.

Check getting started with Dots for current eligibility. Its computer and app guide explains an important distinction: cloud work can continue independently, but local files, skills and apps depend on the connected computer. Plugin access also follows the account’s permissions.

Meta presents Muse as a personal agent for ongoing goals and everyday tasks. Its conversational approach makes it a natural candidate for research, planning and follow-through across connected services.

Muse also has a business side. Meta’s small-business announcement describes work with business tools and Meta business-account context. A local business could use that combination to research an offer, prepare a promotion and organize the work around it.

• Pros: combines everyday and business assistance; fits users already working across Meta’s apps; can connect services and build custom connectors when asked.
• Cons: Meta’s launch material lists US and Canada availability. Free usage has limits, with subscriptions expanding access. Custom integrations can require more setup than choosing an existing connector.
• Our recommendation: consider Muse for personal planning or a small business whose daily work already involves Meta services. Check the connectors you need before choosing it for a recurring workflow.

Meta’s connector guide explains permissions, approvals and custom connectors. Muse the personal agent and Muse Code are separate products; their integration setup should be considered separately.

Grok Bot lets you organize work around persistent Bots with defined responsibilities. You could have one handle research, another prepare content and another maintain the operational checklist. Routines give recurring work a reusable starting point.

This makes sense when you can describe a job clearly: prepare the weekly competitor digest, check the same sources or assemble the next campaign plan. The work documentation describes connected apps and cloud execution. Coding is one use case; research and business workflows can also begin with plain-language instructions.

• Pros: several reusable roles; recurring routines; persistent cloud work; an explicit route for adding custom remote MCP servers.
• Cons: Bots within one account share the cloud computer’s files, browser sessions and app logins. Separate roles do not provide separate access boundaries. Subscription and usage conditions still apply.
• Our recommendation: choose Grok Bot when you want a small set of specialist assistants doing repeatable jobs. Define each Bot’s responsibility clearly so their work stays coordinated.

For external tools, Cursor’s staff instructions describe adding a public MCP server directly through a Bot conversation. This is especially useful when your workflow depends on a service beyond the built-in app selection.

Choose the first agent around a concrete recurring job. For a business owner already using Claude, Duet is a sensible starting point. For someone coordinating research, documents and coding in ChatGPT, Dots fits that existing workflow. Muse is attractive for everyday goals and businesses rooted in Meta’s apps. Grok Bot suits people who want to divide repeatable work among specialist Bots.

Before subscribing, check three things: can you access it in your region, can it connect to the services the job requires, and can it run in the environment where your files live? Then compare the usage allowance with the amount of work you expect. A useful first assignment is narrow enough that you can tell whether it was completed well.

The same choice applies to scheduling. Your agent may be excellent at developing a plan, but the people who need its dates may use entirely different tools. That is where a shared calendar becomes useful.

Imagine a project owner working with Duet, a colleague using Dots and a freelancer who only checks Google Calendar. They all need the same workshop dates and deadlines. Requiring everyone to use the owner’s AI assistant would add friction.

Smart Calendars AI MCP connects the planning conversation to a shareable calendar feed. The assistant prepares structured events and uses Smart Calendars tools to create or update the feed in your account. You share its subscription link, and other people follow the schedule in their own calendar apps.

MCP stands for Model Context Protocol. It gives an assistant a standard way to use a service’s tools. For this workflow, the two connections have different jobs:

• Agent → Smart Calendars AI, through MCP: create, read and update the shared schedule using the connected account.
• Smart Calendars AI → calendar apps, through an ICS/iCalendar subscription: display the schedule in Apple Calendar, Google Calendar, Outlook or another app that supports calendar subscriptions.

The people following the calendar do not need your AI assistant. They receive updates when their calendar provider refreshes the subscription. This also means that changes are not necessarily instant, and a one-time ICS file import behaves differently from a continuing subscription.

The connection manages your Smart Calendars feeds. It does not give an agent access to everyone’s personal calendars. The MCP setup page explains account access and the available calendar tools.

Use the connection route offered by your agent. The Smart Calendars AI server address is https://api.smartcalendars.ai/mcp. Sign in to the Smart Calendars account that should own the schedule when the connection asks you to authorize access.

• Claude Duet: configure Smart Calendars as a custom remote connector in your Claude account. Duet inherits the account’s connectors. Anthropic’s remote MCP guide covers the setup.
• OpenAI Dots: use a supported, enabled MCP plugin connected to your account. OpenAI documents MCP-backed plugins and custom MCP registration. Access depends on the plugin and execution environment.
• Grok Bot: ask your Bot to add the public Smart Calendars MCP server, then follow the connection and authorization prompts. Its custom-server route supports public HTTPS endpoints.
• Meta Muse: ask Muse to build a custom connector for the service. Providers such as NetworkOS describe MCP connections made this way. Muse can construct its own client, so authentication and setup depend on the integration.

For the guided Smart Calendars connection flow, open Connect your assistant. It includes the server address, account sign-in and a first request for reading your existing calendars.

Suppose your team has agreed three milestones: a kickoff on November 3, a draft review on November 10 and a launch on November 17. Start with the agreed dates, owners and times. Give the agent the project plan, paste the relevant text or attach the source document where your assistant supports it.

Create a Smart Calendars AI feed called “November project milestones” from this plan. Show me the proposed events, dates, times and time zone first. Ask about missing details. After I confirm, create the calendar and give me its subscription link.

1. Prepare the events. Ask the agent to extract only the agreed milestones. Keep tentative dates clearly identified and resolve missing times before saving.
2. Review and create. Check the dates, time zone, all-day entries and event descriptions, then confirm the feed creation.
3. Share the subscription link. Colleagues can subscribe using Apple Calendar, Google Calendar or Outlook. They can keep their own provider and AI tools.
4. Maintain the same feed. When a milestone moves, ask the agent to update the existing event. Subscribers receive the change on a later refresh.

A follow-up request can be precise:

In “November project milestones”, move the draft review from November 10 to November 12 at 14:00 Europe/Berlin. Keep its duration and the other events unchanged. Show me the change before applying it.

Updating the existing feed preserves one place for everyone to follow. A new export sent after every change would leave colleagues deciding which version to keep. For a public schedule with a webpage or embed, see how to publish a calendar feed.

• School and club dates: turn a term letter or fixture list into a schedule parents can subscribe to. Add only the dates relevant to the group.
• Content production: share agreed draft, review and publication dates with collaborators. Our content calendar guide explains how to prepare the schedule.
• Workshops and events: publish confirmed sessions with locations and time zones, then maintain the schedule as arrangements change.
• Team shifts: extract the relevant rota into a shared feed, with a clear owner for later corrections. The team schedule guide covers the sharing workflow.

Connecting an assistant and reading feeds are free. Creation and editing follow your Smart Calendars allowance, editing window or subscription; see current plans. Source monitoring is a separate feature: a calendar does not start watching the original PDF or website simply because an agent created it.

Can these personal AI agents use MCP servers? Grok Bot explicitly supports custom remote MCP servers. Claude Duet inherits Claude connectors, including the custom-connector route. Dots uses supported MCP-backed plugins. Muse can build custom connectors, with MCP usage reported by integration providers; its setup differs from a native MCP-server configuration.

Do calendar subscribers need the same AI agent? No. The agent manages the Smart Calendars feed. Recipients subscribe in Apple Calendar, Google Calendar, Outlook or another app that supports ICS/iCalendar subscriptions.

Will changes appear immediately in every calendar app? Each provider controls its subscription refresh timing. Updates appear after the app refreshes the feed. Importing an ICS file once does not create the same ongoing connection as subscribing.

Does the MCP connection access my personal Google or Apple calendars? The Smart Calendars AI MCP connection manages feeds and events in your Smart Calendars account. It does not itself grant access to unrelated personal calendar accounts.

Duet, Dots, Muse and Grok Bot offer different ways to delegate work. Choose the one that fits your tools and the responsibilities you want it to take on. When that work produces a schedule, Smart Calendars AI gives the dates a shared home that colleagues, customers or family can follow in their own calendar apps.

Connect your assistant with Smart Calendars AI MCP to start with your next project plan, timetable or event programme.