Skip to content

armgit / alook

Public Imported from GitHub
0

Multi-Agent Collaboration for Team and Friends

docs(blog): publish paired agent comparisons

Generb8e8b403ffb4
diff --git a/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/alook-coworker-detail.png b/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/alook-coworker-detail.png
new file mode 100644
index 000000000..e9221a6ca
Binary files /dev/null and b/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/alook-coworker-detail.png differ
diff --git a/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/alook-server-official.webp b/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/alook-server-official.webp
new file mode 100644
index 000000000..7e778bce6
Binary files /dev/null and b/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/alook-server-official.webp differ
diff --git a/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/cue-group-detail.png b/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/cue-group-detail.png
new file mode 100644
index 000000000..6f6185359
Binary files /dev/null and b/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/cue-group-detail.png differ
diff --git a/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/cue-group-original-view.jpg b/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/cue-group-original-view.jpg
new file mode 100644
index 000000000..9f119e67d
Binary files /dev/null and b/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/cue-group-original-view.jpg differ
diff --git a/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/cue-review-detail.png b/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/cue-review-detail.png
new file mode 100644
index 000000000..d9fc47f16
Binary files /dev/null and b/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/cue-review-detail.png differ
diff --git a/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/grok-group-demo.jpg b/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/grok-group-demo.jpg
new file mode 100644
index 000000000..c7be8ddb7
Binary files /dev/null and b/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/grok-group-demo.jpg differ
diff --git a/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/grok-group-detail.png b/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/grok-group-detail.png
new file mode 100644
index 000000000..f7f196025
Binary files /dev/null and b/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/grok-group-detail.png differ
diff --git a/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/grok-handoff-routine-demo.jpg b/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/grok-handoff-routine-demo.jpg
new file mode 100644
index 000000000..582587716
Binary files /dev/null and b/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/grok-handoff-routine-demo.jpg differ
diff --git a/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/grok-review-detail.png b/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/grok-review-detail.png
new file mode 100644
index 000000000..e1439e116
Binary files /dev/null and b/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/grok-review-detail.png differ
diff --git a/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/group-chat-comparison.png b/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/group-chat-comparison.png
new file mode 100644
index 000000000..8cdc8b928
Binary files /dev/null and b/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/group-chat-comparison.png differ
diff --git a/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/hero.webp b/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/hero.webp
new file mode 100644
index 000000000..f48616b9c
Binary files /dev/null and b/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/hero.webp differ
diff --git a/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/muse-approval-detail.png b/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/muse-approval-detail.png
new file mode 100644
index 000000000..2a346d3bf
Binary files /dev/null and b/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/muse-approval-detail.png differ
diff --git a/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/progress-approval-comparison.png b/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/progress-approval-comparison.png
new file mode 100644
index 000000000..d02e305bd
Binary files /dev/null and b/src/web/blog/public/blog/grok-bot-vs-meta-muse-vs-manus-cue/progress-approval-comparison.png differ
diff --git a/src/web/blog/public/blog/personal-agents-vs-coding-agents/hero.webp b/src/web/blog/public/blog/personal-agents-vs-coding-agents/hero.webp
new file mode 100644
index 000000000..e79c992db
Binary files /dev/null and b/src/web/blog/public/blog/personal-agents-vs-coding-agents/hero.webp differ
diff --git a/src/web/blog/public/blog/personal-agents-vs-coding-agents/manual-handoff.png b/src/web/blog/public/blog/personal-agents-vs-coding-agents/manual-handoff.png
new file mode 100644
index 000000000..08df11828
Binary files /dev/null and b/src/web/blog/public/blog/personal-agents-vs-coding-agents/manual-handoff.png differ
diff --git a/src/web/blog/public/blog/personal-agents-vs-coding-agents/muse-goals.png b/src/web/blog/public/blog/personal-agents-vs-coding-agents/muse-goals.png
new file mode 100644
index 000000000..baed4e599
Binary files /dev/null and b/src/web/blog/public/blog/personal-agents-vs-coding-agents/muse-goals.png differ
diff --git a/src/web/blog/src/content/grok-bot-vs-meta-muse-vs-manus-cue.mdx b/src/web/blog/src/content/grok-bot-vs-meta-muse-vs-manus-cue.mdx
new file mode 100644
index 000000000..35029c5fd
--- /dev/null
+++ b/src/web/blog/src/content/grok-bot-vs-meta-muse-vs-manus-cue.mdx
@@ -0,0 +1,221 @@
+export const metadata = {
+ slug: "grok-bot-vs-meta-muse-vs-manus-cue",
+ title: "Grok Bot vs Meta Muse vs Manus Cue: Which to Choose?",
+ date: "2026-10-19",
+ author: "Alook Team",
+ excerpt: "Compare Grok Bot, Meta Muse and Manus Cue by tools, collaboration, approvals and access. Choose a setup for the work you need.",
+ readingTime: "9 min read",
+ draft: false,
+ image: "/blog/grok-bot-vs-meta-muse-vs-manus-cue/hero.webp",
+};
+
+Try Grok Bot if you want persistent roles or a Bot your team can share. Muse puts ongoing personal and business goals at the center of the work. With Manus Cue, you give agents separate communication identities and bring them together for handoffs. **Start with the task and the tools you need to keep.**
+
+*Based on official documentation, public demos and official UI images checked October 19, 2026. This is a documentation comparison, without a matched-task performance test.*
+
+![Grok Bot, Meta Muse and Manus Cue logos, with Alook in the lower right.](/blog/grok-bot-vs-meta-muse-vs-manus-cue/hero.webp)
+
+<div className="max-w-full overflow-x-auto thin-scrollbar" tabIndex={0} role="region" aria-label="Product work organization comparison; scroll horizontally to read" style={{ overflowWrap: "normal" }}>
+ <table style={{ display: "table", width: "100%", minWidth: "760px", maxWidth: "none" }}>
+ <thead>
+ <tr>
+ <th>Product</th>
+ <th>How it organizes work</th>
+ <th>Check before trying it</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td><span style={{ whiteSpace: "nowrap" }}>Grok Bot</span></td>
+ <td>Named roles, personal multi-Bot conversations and shared Team Bots</td>
+ <td>Required accounts, team configuration and usage plan</td>
+ </tr>
+ <tr>
+ <td><span style={{ whiteSpace: "nowrap" }}>Meta Muse</span></td>
+ <td>Ongoing goals, a main conversation and side chats</td>
+ <td>Connectors, computer permissions and who needs to participate</td>
+ </tr>
+ <tr>
+ <td><span style={{ whiteSpace: "nowrap" }}>Manus Cue</span></td>
+ <td>Agents with separate identities and group handoffs</td>
+ <td>Required services, current access and Cue-specific plan terms</td>
+ </tr>
+ </tbody>
+ </table>
+</div>
+
+Use these differences to plan a trial. All three can handle personal and business tasks, with overlapping capabilities.
+
+## Grok Bot vs Meta Muse vs Manus Cue: What features do they offer?
+
+You can use all three for work that continues beyond a chat reply. Their interfaces organize that work differently: Grok around Bot responsibilities, Muse around ongoing goals, and Cue around agents with separate identities and roles.
+
+### Grok Bot: persistent roles and a shared team option
+
+Give a Grok Bot a name and a job, such as research, outbound sales or expense management, then connect the services it needs. It keeps context over time and can pass work to other Bots. [Grok's overview](https://docs.x.ai/grok-bot/overview) describes the product separately from the Grok chatbot and Grok Build coding tool.
+
+### Meta Muse: ongoing personal and business goals
+
+Muse learns your preferences as it pursues goals over time. Keep the main conversation for ongoing work. Open side chats for separate topics. Meta's [design explanation](https://introducing.muse.ai/) puts goals and activity beside the conversation. It also shows suggested tasks, so you can check what Muse is doing while you are elsewhere.
+
+### Manus Cue: separate agent identities and group handoffs
+
+Each Cue agent gets its own email, phone number, wallet and computer; give several agents different responsibilities and put them in a group chat. The [Manus 2.0 announcement](https://www.manus.im/blog/introducing-manus-2-0) describes Cue as a standalone app. Check Cue-specific documentation before assuming it includes a feature from Manus Studio.
+
+## App integrations and computer access: What can each agent use?
+
+Grok Bot combines a cloud computer with authorized local commands. If you need Mac apps or business connectors, Muse supports both alongside its cloud environment. Cue provides an agent computer and connected services. Check your required accounts and files against each setup.
+
+Suppose your customer briefing needs a CRM, email and a project folder. Use that list to check the documentation. We have not run this task as a comparison test.
+
+<div className="max-w-full overflow-x-auto thin-scrollbar" tabIndex={0} role="region" aria-label="Product access and configuration comparison; scroll horizontally to read" style={{ overflowWrap: "normal" }}>
+ <table style={{ display: "table", width: "100%", minWidth: "760px", maxWidth: "none" }}>
+ <thead>
+ <tr>
+ <th>Product</th>
+ <th>What it can access</th>
+ <th>What you need to configure</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td><span style={{ whiteSpace: "nowrap" }}>Grok Bot</span></td>
+ <td>A persistent cloud browser, terminal and files; authorized commands on your computer</td>
+ <td>Service logins and the policy for local commands; personal Bots share cloud files and signed-in sessions</td>
+ </tr>
+ <tr>
+ <td><span style={{ whiteSpace: "nowrap" }}>Meta Muse</span></td>
+ <td>A cloud environment, Mac files and apps, and personal or business services</td>
+ <td>Permissions for Mac access; connectors such as Shopify, QuickBooks, Slack or Notion, or a custom connector</td>
+ </tr>
+ <tr>
+ <td><span style={{ whiteSpace: "nowrap" }}>Manus Cue</span></td>
+ <td>An agent computer and connected services</td>
+ <td>Confirm the specific service in Cue; the broader Manus catalog does not establish Cue access</td>
+ </tr>
+ </tbody>
+ </table>
+</div>
+
+Sources: [Grok computer access](https://docs.x.ai/grok-bot/computer-and-apps), [Muse Mac](https://ai.meta.com/muse/download/), [Muse business connectors](https://about.fb.com/news/2026/09/introducing-muse-small-business/) and [Cue](https://cue.im/).
+
+**Local file access, self-hosting the agent and running its model locally are different capabilities.** For the briefing, confirm the CRM connection and how the agent reaches the project folder.
+
+## Team Bots and group chat: How does collaboration work?
+
+In Grok Bot, you can use personal multi-Bot conversations or share a Team Bot. Cue shows agents dividing work in a group chat. Muse has side chats and business connections; the reviewed sources leave its multi-owner arrangement unclear. Check which people and accounts need to join.
+
+- Grok Bot: A [Team Bot](https://docs.x.ai/grok-bot/team-bots) gives teammates a shared role and expertise, including access through Slack. **Shared team memory and personal notes have separate treatment.** Check the shared configuration and credentials; publishing a Team Bot differs from sharing a template someone copies.
+- Meta Muse: [Side chats](https://introducing.muse.ai/) separate topics. Business connectors provide service access. If several owners need to participate, ask for a demonstration with their actual accounts; those features alone do not establish that arrangement.
+- Manus Cue: The [official group-chat image](https://cue.im/) shows an itinerary agent handing work to a booking agent and a packing agent contributing a file. Named speakers and an @mention are visible. You can also see separate deliverables. The image does not establish every multi-owner permission arrangement.
+
+<figure className="my-6 overflow-hidden rounded-lg border border-border" style={{ margin: "24px 0", border: "1px solid var(--border)", borderRadius: "8px", overflow: "hidden" }}>
+<h3 style={{ margin: 0, padding: "12px 16px", fontSize: "18px" }}>Grok Bot · Named speakers and follow-ups</h3>
+<p style={{ margin: 0, padding: "6px 16px", fontSize: "13px" }}>Scroll the image sideways on a small screen, or open the detail.</p>
+<div className="overflow-x-auto thin-scrollbar" tabIndex={0} role="region" style={{ maxWidth: "100%", overflowX: "auto", overscrollBehaviorX: "contain" }} aria-label="Grok Bot · Named speakers and follow-ups official UI detail; scroll horizontally to read"><picture><source srcSet="/blog/grok-bot-vs-meta-muse-vs-manus-cue/grok-group-detail.png" /><img src="/blog/grok-bot-vs-meta-muse-vs-manus-cue/grok-group-detail.png" alt="Chief assigns follow-ups to Account Manager and Inbox Manager." width={520} height={140} style={{ display: "block", width: "520px", minWidth: "520px", maxWidth: "none", height: "auto", margin: 0, borderRadius: 0 }} /></picture></div>
+<figcaption style={{ padding: "12px 16px", fontSize: "14px", lineHeight: 1.5 }}>Chief assigns follow-ups to Account Manager and Inbox Manager. Official display. <a href="https://x.ai/bot">Source</a> · <a href="/blog/grok-bot-vs-meta-muse-vs-manus-cue/grok-group-demo.jpg">Full original</a> · <a href="/blog/grok-bot-vs-meta-muse-vs-manus-cue/grok-group-detail.png">Open detail</a></figcaption>
+</figure>
+
+<figure className="my-6 overflow-hidden rounded-lg border border-border" style={{ margin: "24px 0", border: "1px solid var(--border)", borderRadius: "8px", overflow: "hidden" }}>
+<h3 style={{ margin: 0, padding: "12px 16px", fontSize: "18px" }}>Manus Cue · Role handoff and files</h3>
+<p style={{ margin: 0, padding: "6px 16px", fontSize: "13px" }}>Scroll the image sideways on a small screen, or open the detail.</p>
+<div className="overflow-x-auto thin-scrollbar" tabIndex={0} role="region" style={{ maxWidth: "100%", overflowX: "auto", overscrollBehaviorX: "contain" }} aria-label="Manus Cue · Role handoff and files official UI detail; scroll horizontally to read"><picture><source srcSet="/blog/grok-bot-vs-meta-muse-vs-manus-cue/cue-group-detail.png" /><img src="/blog/grok-bot-vs-meta-muse-vs-manus-cue/cue-group-detail.png" alt="Travel agents exchange an itinerary, packing list and booking request." width={620} height={365} style={{ display: "block", width: "620px", minWidth: "620px", maxWidth: "none", height: "auto", margin: 0, borderRadius: 0 }} /></picture></div>
+<figcaption style={{ padding: "12px 16px", fontSize: "14px", lineHeight: 1.5 }}>Travel agents exchange an itinerary, packing list and booking request. Official display. <a href="https://cue.im/">Source</a> · <a href="/blog/grok-bot-vs-meta-muse-vs-manus-cue/cue-group-original-view.jpg">Full original</a> · <a href="/blog/grok-bot-vs-meta-muse-vs-manus-cue/cue-group-detail.png">Open detail</a></figcaption>
+</figure>
+
+*Official examples with different tasks, not a performance test. Each detail keeps its source and original image. On a narrow screen, scroll inside a detail to read the full message. [Open full group comparison](/blog/grok-bot-vs-meta-muse-vs-manus-cue/group-chat-comparison.png).*
+
+For more background on the distinction between agents exchanging messages and the environment people share with them, see [AI agent communication](/blog/ai-agent-communication).
+
+## Task tracking, Goals and approvals: How do you manage ongoing tasks?
+
+You can follow Grok's work in conversations, drafts and its computer view. For Muse, look at activity, Goals, Artifacts and approval cards. Cue's published group examples show files moving between roles and decisions returning to the user. Check the deliverable as well as the point where work waits for you.
+
+- Grok Bot: The [public sales demo](https://x.ai/bot) shows a login request, messages from other Bots and drafts before a routine is created. The computer view lets the person watch or take control. The demo's counts and completed actions are example content.
+- Meta Muse: [Official UI images](https://introducing.muse.ai/) show activity, Goals and purchase approval cards, with documents and interactive outputs in Artifacts. You can inspect a document in Artifacts or respond to a pending approval card.
+- Manus Cue: The [launch example](https://www.manus.im/blog/introducing-manus-2-0) describes agents researching venues, making a shortlist and preparing a deck. The user makes the final call. Its published group image also shows files and a booking agent promising confirmation before payment.
+
+<figure className="my-6 overflow-hidden rounded-lg border border-border" style={{ margin: "24px 0", border: "1px solid var(--border)", borderRadius: "8px", overflow: "hidden" }}>
+<h3 style={{ margin: 0, padding: "12px 16px", fontSize: "18px" }}>Grok Bot · Draft review</h3>
+<p style={{ margin: 0, padding: "6px 16px", fontSize: "13px" }}>Scroll the image sideways on a small screen, or open the detail.</p>
+<div className="overflow-x-auto thin-scrollbar" tabIndex={0} role="region" style={{ maxWidth: "100%", overflowX: "auto", overscrollBehaviorX: "contain" }} aria-label="Grok Bot · Draft review official UI detail; scroll horizontally to read"><picture><source srcSet="/blog/grok-bot-vs-meta-muse-vs-manus-cue/grok-review-detail.png" /><img src="/blog/grok-bot-vs-meta-muse-vs-manus-cue/grok-review-detail.png" alt="The demo presents queued drafts before the user approves the next step." width={680} height={300} style={{ display: "block", width: "680px", minWidth: "680px", maxWidth: "none", height: "auto", margin: 0, borderRadius: 0 }} /></picture></div>
+<figcaption style={{ padding: "12px 16px", fontSize: "14px", lineHeight: 1.5 }}>The demo presents queued drafts before the user approves the next step. Official display. <a href="https://x.ai/bot">Source</a> · <a href="/blog/grok-bot-vs-meta-muse-vs-manus-cue/grok-handoff-routine-demo.jpg">Full original</a> · <a href="/blog/grok-bot-vs-meta-muse-vs-manus-cue/grok-review-detail.png">Open detail</a></figcaption>
+</figure>
+
+<figure className="my-6 overflow-hidden rounded-lg border border-border" style={{ margin: "24px 0", border: "1px solid var(--border)", borderRadius: "8px", overflow: "hidden" }}>
+<h3 style={{ margin: 0, padding: "12px 16px", fontSize: "18px" }}>Meta Muse · Purchase approval</h3>
+<p style={{ margin: 0, padding: "6px 16px", fontSize: "13px" }}>Scroll the image sideways on a small screen, or open the detail.</p>
+<div className="overflow-x-auto thin-scrollbar" tabIndex={0} role="region" style={{ maxWidth: "100%", overflowX: "auto", overscrollBehaviorX: "contain" }} aria-label="Meta Muse · Purchase approval official UI detail; scroll horizontally to read"><picture><source srcSet="/blog/grok-bot-vs-meta-muse-vs-manus-cue/muse-approval-detail.png" /><img src="/blog/grok-bot-vs-meta-muse-vs-manus-cue/muse-approval-detail.png" alt="An order card shows the total, Review order and Allow / Deny controls." width={786} height={1050} style={{ display: "block", width: "min(100%, 524px)", minWidth: "390px", maxWidth: "none", height: "auto", margin: 0, borderRadius: 0 }} /></picture></div>
+<figcaption style={{ padding: "12px 16px", fontSize: "14px", lineHeight: 1.5 }}>An order card shows the total, Review order and Allow / Deny controls. Official display. <a href="https://introducing.muse.ai/">Source</a> · <a href="/blog/grok-bot-vs-meta-muse-vs-manus-cue/muse-approval-detail.png">Open detail</a></figcaption>
+</figure>
+
+<figure className="my-6 overflow-hidden rounded-lg border border-border" style={{ margin: "24px 0", border: "1px solid var(--border)", borderRadius: "8px", overflow: "hidden" }}>
+<h3 style={{ margin: 0, padding: "12px 16px", fontSize: "18px" }}>Manus Cue · Deliverables and confirmation</h3>
+<p style={{ margin: 0, padding: "6px 16px", fontSize: "13px" }}>Scroll the image sideways on a small screen, or open the detail.</p>
+<div className="overflow-x-auto thin-scrollbar" tabIndex={0} role="region" style={{ maxWidth: "100%", overflowX: "auto", overscrollBehaviorX: "contain" }} aria-label="Manus Cue · Deliverables and confirmation official UI detail; scroll horizontally to read"><picture><source srcSet="/blog/grok-bot-vs-meta-muse-vs-manus-cue/cue-review-detail.png" /><img src="/blog/grok-bot-vs-meta-muse-vs-manus-cue/cue-review-detail.png" alt="Files appear in the chat; the booking agent promises confirmation before payment." width={620} height={280} style={{ display: "block", width: "620px", minWidth: "620px", maxWidth: "none", height: "auto", margin: 0, borderRadius: 0 }} /></picture></div>
+<figcaption style={{ padding: "12px 16px", fontSize: "14px", lineHeight: 1.5 }}>Files appear in the chat; the booking agent promises confirmation before payment. Official display. <a href="https://cue.im/">Source</a> · <a href="/blog/grok-bot-vs-meta-muse-vs-manus-cue/cue-group-original-view.jpg">Full original</a> · <a href="/blog/grok-bot-vs-meta-muse-vs-manus-cue/cue-review-detail.png">Open detail</a></figcaption>
+</figure>
+
+*Official examples, not our task results. [Open the full three-product comparison](/blog/grok-bot-vs-meta-muse-vs-manus-cue/progress-approval-comparison.png). Each full original remains available above.*
+
+Email and payments are available in more than one of these products. Grok's [October 11 changelog](https://x.ai/changelog/bot) also added Bot email addresses and payments through X Money or Stripe Link, so compare the approval flow and account access you would actually use.
+
+## Grok Bot, Meta Muse and Manus Cue: Pricing and availability
+
+Grok publishes individual monthly prices and usage limits, while Muse offers free and subscription access. Muse's business offer also has eligibility conditions. **We have not confirmed Cue's current price schedule**, so we cannot compare total costs on the same basis.
+
+<div className="max-w-full overflow-x-auto thin-scrollbar" tabIndex={0} role="region" aria-label="Product price and access comparison; scroll horizontally to read" style={{ overflowWrap: "normal" }}>
+ <table style={{ display: "table", width: "100%", minWidth: "760px", maxWidth: "none" }}>
+ <thead>
+ <tr>
+ <th>Product</th>
+ <th>Price and usage information checked October 19, 2026</th>
+ <th>Access conditions to confirm</th>
+ </tr>
+ </thead>
+ <tbody>
+ <tr>
+ <td><span style={{ whiteSpace: "nowrap" }}>Grok Bot</span></td>
+ <td>Included with individual X Subscription plans: Premium $30, Super $100, Ultra $200 per month; usage limits apply</td>
+ <td>Current X Subscription uses a shared weekly pool and prepaid extra usage; legacy Cursor plans differ</td>
+ </tr>
+ <tr>
+ <td><span style={{ whiteSpace: "nowrap" }}>Meta Muse</span></td>
+ <td>Free use and subscription options; exact current subscription amounts not confirmed here</td>
+ <td>The business page lists US and Canada, age 18+; check the offer in your account</td>
+ </tr>
+ <tr>
+ <td><span style={{ whiteSpace: "nowrap" }}>Manus Cue</span></td>
+ <td>Current Cue-specific price schedule not confirmed; the launch described free early access</td>
+ <td>Launch access was invitation-based; confirm current access and platform availability</td>
+ </tr>
+ </tbody>
+ </table>
+</div>
+
+The X Subscription bundles Cursor and Grok, including Grok Bot on Premium, Super and Ultra. Eligible legacy Cursor plans can also provide Grok Bot access. Check the billing terms for the plan you actually use.
+
+Sources: [Grok prices](https://x.ai/bot), [Grok billing](https://cursor.com/help/grok-bot/plans), [Muse business offer](https://muse.ai/business) and [Cue launch](https://www.manus.im/blog/introducing-manus-2-0). Dollar figures are USD per month for the individual X Subscription plans that include Grok Bot, not comparable prices for all three products. The general Manus pricing page does not establish Cue pricing.
+
+Choose a plan against the workload you expect. Check its limits and the services you will connect.
+
+## Which personal agent should you choose?
+
+- Try Grok Bot when **persistent roles and a shared Team Bot** fit how your colleagues work.
+- Try Meta Muse for **ongoing goals across supported personal or business tools**, with goals, activity and approvals to review.
+- Look at Manus Cue when **separate agent identities and group handoffs** are central to the task.
+
+Already using Claude Code or Codex? Read [Personal agents vs coding agents](/blog/personal-agents-vs-coding-agents) to check whether adding a personal-agent product would address a gap in your current setup.
+
+If your bot already works with your files and tools, [Alook](https://alook.ai/) lets **colleagues and their bots join the conversation**. Keep a supported execution tool, such as Claude Code or Codex, so a coworker can ask the bot about its work. Each owner controls their runtime and tools, but you need to set up the connection and leave the execution machine online. We have not established native Alook connections to Grok Bot, Muse or Cue. See the [coworker example](/blog/ask-coworker-codex-claude-code) for that interaction, or the [Grok Bot comparison](/blog/alook-vs-grok-bot) for the two-product decision.
+
+<figure className="my-6 overflow-hidden rounded-lg border border-border" style={{ margin: "24px 0", border: "1px solid var(--border)", borderRadius: "8px", overflow: "hidden" }}>
+<h3 style={{ margin: 0, padding: "12px 16px", fontSize: "18px" }}>Alook · A coworker follows up</h3>
+<p style={{ margin: 0, padding: "6px 16px", fontSize: "13px" }}>Scroll the image sideways on a small screen, or open the detail.</p>
+<div className="overflow-x-auto thin-scrollbar" tabIndex={0} role="region" style={{ maxWidth: "100%", overflowX: "auto", overscrollBehaviorX: "contain" }} aria-label="Alook · A coworker follows up official UI detail; scroll horizontally to read"><picture><source srcSet="/blog/grok-bot-vs-meta-muse-vs-manus-cue/alook-coworker-detail.png" /><img src="/blog/grok-bot-vs-meta-muse-vs-manus-cue/alook-coworker-detail.png" alt="Alook homepage demo: Gus asks for a larger headline, Alli reports a preview, and Ruthann follows up." width={805} height={225} style={{ display: "block", width: "805px", minWidth: "805px", maxWidth: "none", height: "auto", margin: 0, borderRadius: 0 }} /></picture></div>
+<figcaption style={{ padding: "12px 16px", fontSize: "14px", lineHeight: 1.5 }}>Alook homepage demo: Gus asks for a larger headline, Alli reports a preview, and Ruthann follows up. Official display. <a href="https://alook.ai/">Source</a> · <a href="/blog/grok-bot-vs-meta-muse-vs-manus-cue/alook-server-official.webp">Full original</a> · <a href="/blog/grok-bot-vs-meta-muse-vs-manus-cue/alook-coworker-detail.png">Open detail</a></figcaption>
+</figure>
+
+*Official homepage demonstration, not a task we ran. It illustrates shared participation; the image does not show which runtime is connected.*
+
+For the customer briefing, check whether the agent can read the right records and produce a usable file. Have the next person in the workflow review it. Use that result to decide whether to keep the setup or change it.
diff --git a/src/web/blog/src/content/personal-agents-vs-coding-agents.mdx b/src/web/blog/src/content/personal-agents-vs-coding-agents.mdx
new file mode 100644
index 000000000..591e296c0
--- /dev/null
+++ b/src/web/blog/src/content/personal-agents-vs-coding-agents.mdx
@@ -0,0 +1,129 @@
+export const metadata = {
+ slug: "personal-agents-vs-coding-agents",
+ author: "Alook Team",
+ date: "2026-10-19",
+ excerpt: "See when Claude Code or Codex is enough, what Grok Bot or Meta Muse adds, and how to assess the setup for your work.",
+ draft: false,
+ title: "Personal agents vs coding agents: Do you need both?",
+ readingTime: "8 min read",
+ image: "/blog/personal-agents-vs-coding-agents/hero.webp",
+};
+
+Your current setup may be enough. If Claude Code or Codex already handles the work you want to delegate, check what Grok Bot or Meta Muse would change. Add another product when a specific feature solves a recurring problem, such as keeping track of ongoing requests or reviewing pending actions.
+
+**Check what you would gain before taking on another setup to maintain.**
+
+![Two pixel helpers and a person share a project book beneath the question personal agents or coding agents?](/blog/personal-agents-vs-coding-agents/hero.webp)
+
+## Personal agents vs coding agents: what do the names mean?
+
+An agent can use tools and take several steps toward a task. For example, it can read permitted messages and produce a file for you to review.
+
+A **personal agent** is organized around your background, preferences and ongoing responsibilities, including work and business tasks. For instance, you might ask Grok Bot or Meta Muse to prepare a recurring customer-feedback brief from permitted sources and bring the findings back for review.
+
+A **coding agent** starts with a software project and its tools. Claude Code, Codex, Cursor and OpenCode work with project files and commands. You might ask one to investigate a reported bug, propose a change and return test evidence. You review the result in the context of that project.
+
+The capabilities overlap: Claude Code can prepare the feedback brief too, and Muse can write code. The labels describe the products' main focus; your task determines which configuration fits.
+
+## Can Claude Code or Codex handle personal tasks?
+
+Yes, with access to the required information and tools. Claude Code or Codex can research a topic, read customer messages and write a brief. A weekly feedback summary is a useful example: first check whether the source messages are accessible through your current connections.
+
+- Claude Code can connect through MCP to external sources such as Google Drive, Jira and Slack. [Claude Code documentation](https://code.claude.com/docs/en/overview)
+- Codex CLI supports plugins and MCP tools, which can extend the work you do in the terminal. [Codex CLI documentation](https://learn.chatgpt.com/docs/codex/cli)
+- Cursor can use MCP services such as Linear or Notion. [Cursor MCP documentation](https://cursor.com/help/customization/mcp)
+- OpenCode provides file and command tools and supports custom tools and MCP servers. [OpenCode tools](https://opencode.ai/docs/tools/)
+
+Test your actual connection. MCP support by itself does not mean that a product can access every service or account.
+
+Background work is available here too. Codex Cloud runs tasks in configured remote repository environments, while Claude Code routines support scheduled and triggered work. Claude's routines remain a research preview with access and execution conditions. [Codex Cloud](https://learn.chatgpt.com/docs/cloud), [Claude Code routines](https://code.claude.com/docs/en/routines)
+
+**Compare the specific setup you would use.** Check whether the feature belongs to a desktop app, a cloud service or a CLI; their configurations differ.
+
+## Why add Grok Bot or Meta Muse to Claude Code or Codex?
+
+Consider Grok Bot or Muse when their task-management interface or supplied environment addresses a problem you still have. For the weekly brief, that could mean seeing which requests remain open and where your approval is needed.
+
+Muse puts ongoing responsibilities in a Goals view. You can also inspect activity and permission history, use structured approval controls, and read or edit its memory files. If you lose track of several requests, try following one through these views before moving more work into Muse. [Muse product design](https://introducing.muse.ai/)
+
+<figure className="overflow-hidden rounded-lg border border-border" style={{ maxWidth: "392px", margin: "24px auto" }}>
+ <h3 style={{ margin: 0, padding: "12px 16px", fontSize: "18px" }}>Muse Goals: an official product example</h3>
+ <p style={{ margin: 0, padding: "0 16px 12px", fontSize: "14px" }}>Scroll sideways if needed, or open the full image.</p>
+ <div className="overflow-x-auto thin-scrollbar" tabIndex={0} role="region" aria-label="Muse Goals: an official product example; scroll horizontally to read" style={{ maxWidth: "100%", overflowX: "auto", overscrollBehaviorX: "contain" }}>
+ <picture><source srcSet="/blog/personal-agents-vs-coding-agents/muse-goals.png" /><img src="/blog/personal-agents-vs-coding-agents/muse-goals.png" alt="Official Muse Goals interface showing example family tasks and their tracking status." width={786} height={1130} style={{ display: "block", width: "390px", minWidth: "390px", maxWidth: "none", height: "auto", margin: 0, borderRadius: 0 }} /></picture>
+ </div>
+ <figcaption style={{ padding: "12px 16px", fontSize: "14px" }}>Official September 2026 demonstration. The family tasks are Meta's examples, not a workflow we ran. · <a href="https://introducing.muse.ai/">Official source</a> · <a href="/blog/personal-agents-vs-coding-agents/muse-goals.png">Open full image</a></figcaption>
+</figure>
+
+For the feedback brief, give Muse access to the relevant information and explain what counts as a useful finding. Check the sources. Confirm that the brief follows your rules. The interface helps you inspect the task; its presence alone cannot establish time savings or accuracy.
+
+Grok Bot supplies a persistent cloud computer with a browser, files and a terminal. Named bots can take on jobs and join group conversations. Under your account, they share the computer and its logged-in sessions. Each bot keeps its own conversation context and memory. [Grok Bot overview](https://docs.x.ai/grok-bot/overview)
+
+That may suit someone who wants to organize several responsibilities through those named bots. You still grant access, define the job and respond when a website requires a human step. For a recurring brief, Grok Bot also documents skills and routines with schedules or event triggers. [Grok Bot routines](https://docs.x.ai/grok-bot/skills-routines-and-automations)
+
+If your only problem is keeping a task running remotely, compare the remote options in Codex or Claude Code first. As of October 19, 2026, Cursor Cloud Agents also provide remote environments and can use configured MCP services. [Cursor Cloud capabilities](https://cursor.com/docs/cloud-agent/capabilities)
+
+**Name the operation or maintenance you expect the new product to remove.** You might find pending work easier to inspect in Muse's goal view, or prefer assigning responsibilities through Grok Bot's named conversations. Try that part of your workflow and see whether it helps.
+
+## How can I check whether my current setup is enough?
+
+Run a small version of the feedback brief in Claude Code, Codex, Cursor or OpenCode, whichever you already use. Start with a limited set of messages you are allowed to share:
+
+> Review this week's customer-feedback messages. Link each finding to its source. Separate bug reports from requests that need clarification. List any supplied reproduction steps and mark unverified reports as unverified. Prepare a brief for me to review. Do not send replies or change code.
+
+This is a suggested trial, not a comparison we have run. Inspect the resulting brief before trying to repeat the task. You can test your current connections without subscribing to every product.
+
+| Check | Evidence to look for |
+|---|---|
+| It read the intended material | The brief links to accessible source messages and covers the requested period |
+| It understood your rules | Bug reports and unclear requests are separated; supplied reproduction steps and verification status are visible |
+| You can correct the result | You can inspect the brief, change the instructions and review another attempt |
+| The next run has a defined path | You know what starts it, where it executes and which settings apply |
+| Someone can recover a failed run | A named person can notice an expired login or missing output and restart the work |
+
+A good brief today still leaves next Friday's run to check. Verify what will start it and where you will see the result. If missing source material made the first brief poor, changing products may leave that problem unresolved.
+
+Write down the missing step. For instance, look for a control in Muse, Grok Bot or your existing setup that clearly shows which requests still need approval.
+
+## Should I keep Claude Code or Codex, switch, or use both?
+
+Keep Claude Code or Codex when the task works and you can maintain and review it. If a specific feature in Grok Bot or Muse addresses a recurring problem, try that feature before switching. Your existing setup matters more than your job title.
+
+| Your situation | What to try first |
+|---|---|
+| Claude Code or Codex already produces the brief through working connections | Keep that workflow and fix any remaining gap directly |
+| You want Muse's goal and approval interface, or Grok Bot's way of organizing named bots | Try one bounded responsibility there before moving more work |
+| Your Cursor project already contains the relevant tools and review process | Test the task in that project before rebuilding the setup elsewhere |
+| OpenCode already has the tools and permissions you need | Test that configuration and decide who will maintain it |
+| You only need occasional answers | Check whether your existing chat tool is sufficient |
+
+A person without development experience may prefer a particular interface, but the label "personal" does not make every task easy to supervise. If you cannot assess a code change, arrange technical review. Likewise, a developer may prefer Muse for tracking personal responsibilities. There is no rule that developers should use one category and everyone else the other.
+
+If the brief leads to software work, you can hand an approved finding to the project where Claude Code, Codex, Cursor or OpenCode is already configured:
+
+1. Review the source-linked feedback and select a bug report to investigate.
+2. Give the project the observed behavior, expected behavior and any supplied reproduction steps. Ask it to verify the report before proposing a fix.
+3. Review the proposed patch and test evidence before deciding whether to merge or release it.
+
+<figure className="overflow-hidden rounded-lg border border-border" style={{ margin: "24px 0" }}>
+ <h3 style={{ margin: 0, padding: "12px 16px", fontSize: "18px" }}>A suggested manual handoff</h3>
+ <p style={{ margin: 0, padding: "0 16px 12px", fontSize: "14px" }}>Scroll sideways if needed, or open the full image.</p>
+ <div className="overflow-x-auto thin-scrollbar" tabIndex={0} role="region" aria-label="A suggested manual handoff; scroll horizontally to read" style={{ maxWidth: "100%", overflowX: "auto", overscrollBehaviorX: "contain" }}>
+ <picture><source srcSet="/blog/personal-agents-vs-coding-agents/manual-handoff.png" /><img src="/blog/personal-agents-vs-coding-agents/manual-handoff.png" alt="Feedback brief, human selection and scope, coding tool verification with patch and tests only if confirmed, then human review." width={1200} height={450} style={{ display: "block", width: "1200px", minWidth: "1200px", maxWidth: "none", height: "auto", margin: 0, borderRadius: 0 }} /></picture>
+ </div>
+ <figcaption style={{ padding: "12px 16px", fontSize: "14px" }}>Suggested workflow. A person transfers the brief and reviews the result; this is not a verified native integration. · <a href="/blog/personal-agents-vs-coding-agents/manual-handoff.png">Open full image</a></figcaption>
+</figure>
+
+**This is a suggested manual handoff, not a verified native integration with Grok Bot or Muse.** If one tool handles the full task well, you do not need to split it merely to use both.
+
+If you decide to add a personal-agent product, [compare Grok Bot, Meta Muse and Manus Cue](/blog/grok-bot-vs-meta-muse-vs-manus-cue) for their different tools, approval flows and ways of organizing work.
+
+## What if coworkers need to review or continue the work?
+
+Give the relevant people access to the brief and a place to discuss the proposed fix. The colleague prioritizing a reported bug may need answers before anyone changes the code.
+
+Alook is an option when you want coworkers and their bots to participate while retaining supported runtimes such as Claude Code or Codex. They can discuss the evidence and ask follow-up questions in a shared conversation they can access. [Alook](https://alook.ai/)
+
+Each participant keeps their own tool permissions. Alook does not create a native connection to Grok Bot or Muse. A runtime executing on your computer still needs that machine online.
+
+For the next feedback review, identify the step you cannot complete comfortably in your current setup. Check that step in the product you are considering, including who will maintain access and review the result.
diff --git a/src/web/blog/src/lib/blog/image-assets.json b/src/web/blog/src/lib/blog/image-assets.json
index 5aa6431c8..76ab612a7 100644
--- a/src/web/blog/src/lib/blog/image-assets.json
+++ b/src/web/blog/src/lib/blog/image-assets.json
@@ -37,6 +37,13 @@
"/blog/claude-code-subagents-vs-independent-agents/architecture-compare.webp": {"width":1400,"height":933,"srcSet":"/blog/_generated/5898f03690f372b0-480.webp 480w, /blog/_generated/5898f03690f372b0-960.webp 960w, /blog/claude-code-subagents-vs-independent-agents/architecture-compare.webp 1400w"},
"/blog/claude-code-subagents-vs-independent-agents/hero.webp": {"width":1200,"height":630,"srcSet":"/blog/_generated/2a0837c3d61bfdca-480.webp 480w, /blog/_generated/2a0837c3d61bfdca-960.webp 960w, /blog/claude-code-subagents-vs-independent-agents/hero.webp 1200w"},
"/blog/claude-code-subagents-vs-independent-agents/three-layers.webp": {"width":1400,"height":933,"srcSet":"/blog/_generated/622dcce0a4478293-480.webp 480w, /blog/_generated/622dcce0a4478293-960.webp 960w, /blog/claude-code-subagents-vs-independent-agents/three-layers.webp 1400w"},
+ "/blog/grok-bot-vs-meta-muse-vs-manus-cue/alook-coworker-detail.png": {"width":805,"height":225,"srcSet":"/blog/_generated/13f41b3af8abf49b-480.webp 480w, /blog/grok-bot-vs-meta-muse-vs-manus-cue/alook-coworker-detail.png 805w"},
+ "/blog/grok-bot-vs-meta-muse-vs-manus-cue/cue-group-detail.png": {"width":620,"height":365,"srcSet":"/blog/_generated/76c2d061b3e3d4bf-480.webp 480w, /blog/grok-bot-vs-meta-muse-vs-manus-cue/cue-group-detail.png 620w"},
+ "/blog/grok-bot-vs-meta-muse-vs-manus-cue/cue-review-detail.png": {"width":620,"height":280,"srcSet":"/blog/_generated/c7addad259859afe-480.webp 480w, /blog/grok-bot-vs-meta-muse-vs-manus-cue/cue-review-detail.png 620w"},
+ "/blog/grok-bot-vs-meta-muse-vs-manus-cue/grok-group-detail.png": {"width":520,"height":140,"srcSet":"/blog/_generated/e6d6d218fe5c64e4-480.webp 480w, /blog/grok-bot-vs-meta-muse-vs-manus-cue/grok-group-detail.png 520w"},
+ "/blog/grok-bot-vs-meta-muse-vs-manus-cue/grok-review-detail.png": {"width":680,"height":300,"srcSet":"/blog/_generated/da824a83b5b48be6-480.webp 480w, /blog/grok-bot-vs-meta-muse-vs-manus-cue/grok-review-detail.png 680w"},
+ "/blog/grok-bot-vs-meta-muse-vs-manus-cue/hero.webp": {"width":1200,"height":630,"srcSet":"/blog/_generated/ee4ad7647f1f87a6-480.webp 480w, /blog/_generated/ee4ad7647f1f87a6-960.webp 960w, /blog/grok-bot-vs-meta-muse-vs-manus-cue/hero.webp 1200w"},
+ "/blog/grok-bot-vs-meta-muse-vs-manus-cue/muse-approval-detail.png": {"width":786,"height":1050,"srcSet":"/blog/_generated/d8ec24d47af47425-480.webp 480w, /blog/grok-bot-vs-meta-muse-vs-manus-cue/muse-approval-detail.png 786w"},
"/blog/how-to-delegate-tasks-to-ai-agents/hero.webp": {"width":1200,"height":630,"srcSet":"/blog/_generated/98e567ac5790158d-480.webp 480w, /blog/_generated/98e567ac5790158d-960.webp 960w, /blog/how-to-delegate-tasks-to-ai-agents/hero.webp 1200w"},
"/blog/humans-and-ai-agents-in-one-room/access-vs-attention.webp": {"width":800,"height":400,"srcSet":"/blog/_generated/aba2338d4f6c5e61-480.webp 480w, /blog/humans-and-ai-agents-in-one-room/access-vs-attention.webp 800w"},
"/blog/humans-and-ai-agents-in-one-room/addressing-vs-authority.webp": {"width":800,"height":400,"srcSet":"/blog/_generated/f7c991657d0976da-480.webp 480w, /blog/humans-and-ai-agents-in-one-room/addressing-vs-authority.webp 800w"},
@@ -60,6 +67,9 @@
"/blog/multiple-ai-agents-edit-same-repository/git-handles.webp": {"width":1536,"height":1024,"srcSet":"/blog/_generated/070c822fb230caef-480.webp 480w, /blog/_generated/070c822fb230caef-960.webp 960w, /blog/multiple-ai-agents-edit-same-repository/git-handles.webp 1536w"},
"/blog/multiple-ai-agents-edit-same-repository/hero.webp": {"width":1536,"height":1024,"srcSet":"/blog/_generated/a7f3a407c17b234e-480.webp 480w, /blog/_generated/a7f3a407c17b234e-960.webp 960w, /blog/multiple-ai-agents-edit-same-repository/hero.webp 1536w"},
"/blog/no-code-automation-ai-agents/hero.webp": {"width":1200,"height":630,"srcSet":"/blog/_generated/014f046b2b151b54-480.webp 480w, /blog/_generated/014f046b2b151b54-960.webp 960w, /blog/no-code-automation-ai-agents/hero.webp 1200w"},
+ "/blog/personal-agents-vs-coding-agents/hero.webp": {"width":1200,"height":630,"srcSet":"/blog/_generated/6569317b40362b06-480.webp 480w, /blog/_generated/6569317b40362b06-960.webp 960w, /blog/personal-agents-vs-coding-agents/hero.webp 1200w"},
+ "/blog/personal-agents-vs-coding-agents/manual-handoff.png": {"width":1200,"height":450,"srcSet":"/blog/_generated/9ffa3a61e2c8d990-480.webp 480w, /blog/_generated/9ffa3a61e2c8d990-960.webp 960w, /blog/personal-agents-vs-coding-agents/manual-handoff.png 1200w"},
+ "/blog/personal-agents-vs-coding-agents/muse-goals.png": {"width":786,"height":1130,"srcSet":"/blog/_generated/3c32374f14fe835b-480.webp 480w, /blog/personal-agents-vs-coding-agents/muse-goals.png 786w"},
"/blog/personal-ai-company/comparison.webp": {"width":1200,"height":630,"srcSet":"/blog/_generated/c013b6a1e62aa7d7-480.webp 480w, /blog/_generated/c013b6a1e62aa7d7-960.webp 960w, /blog/personal-ai-company/comparison.webp 1200w"},
"/blog/personal-ai-company/hero.webp": {"width":1200,"height":630,"srcSet":"/blog/_generated/00a72af97ff1a5f3-480.webp 480w, /blog/_generated/00a72af97ff1a5f3-960.webp 960w, /blog/personal-ai-company/hero.webp 1200w"},
"/blog/personal-ai-company/timeline.webp": {"width":1200,"height":630,"srcSet":"/blog/_generated/5408f87223e0696c-480.webp 480w, /blog/_generated/5408f87223e0696c-960.webp 960w, /blog/personal-ai-company/timeline.webp 1200w"},
diff --git a/src/web/blog/src/lib/blog/topics.test.ts b/src/web/blog/src/lib/blog/topics.test.ts
index ab9d9613f..cc0f90675 100644
--- a/src/web/blog/src/lib/blog/topics.test.ts
+++ b/src/web/blog/src/lib/blog/topics.test.ts
@@ -47,17 +47,19 @@ describe("blogTopics", () => {
expect(registrySlugs).toEqual(publishedSlugs);
});
- it("covers all 30 published slugs exactly once", () => {
+ it("covers all 32 published slugs exactly once", () => {
const orderedSlugs = blogTopics.map((topic) =>
topic.entries.map((entry) => entry.slug)
);
const slugs = orderedSlugs.flat();
- expect(slugs).toHaveLength(30);
- expect(new Set(slugs).size).toBe(30);
+ expect(slugs).toHaveLength(32);
+ expect(new Set(slugs).size).toBe(32);
expect(orderedSlugs).toEqual([
[
"ai-agent-vs-chatbot",
+ "grok-bot-vs-meta-muse-vs-manus-cue",
+ "personal-agents-vs-coding-agents",
"local-ai-agents",
"how-to-delegate-tasks-to-ai-agents",
"ai-agent-team",
@@ -118,6 +120,8 @@ describe("blogTopics", () => {
"prevent-codex-opencode-duplicating-work": "Prevent Codex and OpenCode from duplicating work",
"prevent-claude-code-opencode-duplicating-work": "Prevent Claude Code and OpenCode from duplicating work",
"ai-agent-vs-chatbot": "Decide whether I need an agent or a chatbot",
+ "personal-agents-vs-coding-agents": "Decide whether my existing coding tools cover the work or I need another agent product",
+ "grok-bot-vs-meta-muse-vs-manus-cue": "Choose a personal-agent product by tools, ongoing work and review controls",
"local-ai-agents":
"Choose which parts of an AI agent should run locally",
"how-to-delegate-tasks-to-ai-agents":
@@ -196,8 +200,8 @@ describe("topic discovery", () => {
)
).toEqual([
"ai-agent-vs-chatbot",
- "local-ai-agents",
- "how-to-delegate-tasks-to-ai-agents",
+ "grok-bot-vs-meta-muse-vs-manus-cue",
+ "personal-agents-vs-coding-agents",
]);
});
diff --git a/src/web/blog/src/lib/blog/topics.ts b/src/web/blog/src/lib/blog/topics.ts
index 40af773aa..71f93d073 100644
--- a/src/web/blog/src/lib/blog/topics.ts
+++ b/src/web/blog/src/lib/blog/topics.ts
@@ -23,6 +23,8 @@ export const blogTopics = [
pillarSlug: "ai-agent-team",
entries: [
{ slug: "ai-agent-vs-chatbot", userJob: "Decide whether I need an agent or a chatbot" },
+ { slug: "grok-bot-vs-meta-muse-vs-manus-cue", userJob: "Choose a personal-agent product by tools, ongoing work and review controls" },
+ { slug: "personal-agents-vs-coding-agents", userJob: "Decide whether my existing coding tools cover the work or I need another agent product" },
{ slug: "local-ai-agents", userJob: "Choose which parts of an AI agent should run locally" },
{ slug: "how-to-delegate-tasks-to-ai-agents", userJob: "Package a task so an agent can run it reliably" },
{ slug: "ai-agent-team", userJob: "Design a multi-agent team with roles and handoffs" },