From 33051b95bf0c33d81df7737911f00596a000312b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Alejandro=20Guti=C3=A9rrez?= <35082514+alezmad@users.noreply.github.com> Date: Mon, 4 May 2026 23:10:27 +0100 Subject: [PATCH] =?UTF-8?q?feat(web):=20marketing=20audit=20=E2=80=94=20Ag?= =?UTF-8?q?ent=20Teams=20positioning,=20MCP/dashboard=20claims=20fixed?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Comprehensive review of all home-page marketing components against the post-correction positioning. Five surgical fixes, zero hand-waving. CTA copy. The previous "Anthropic built Claude Code per developer. The next unlock is between developers." was a strong line in 2025 but Anthropic Agent Teams (Feb 2026) IS now between-developers within one machine. Replaced with the accurate distinction: "Anthropic Agent Teams stops at the edge of one laptop. claudemesh starts there — across machines, users, and organizations." WhereMeshFits — new "vs. Agent Teams" comparison card. The single most important card the page can have right now. Most readers arriving in May 2026 know about Agent Teams; the comparison they want to read is exactly this one. Also tightened the "What claudemesh is" claim card to lean into "across machines, users, orgs" instead of the narrower "peer network for Claude Code" framing. FAQ — three updates: 1. "How is this different from MCP?" was claiming "43 tools that let peers message, share files…" which contradicted v1.5.0's ship of tool-less MCP (tools/list returns []). Replaced with the actual current architecture: thin push-pipe + resource- noun-verb CLI bundled as a skill. 2. New entry "How is this different from Anthropic's Agent Teams?" — the biggest gap in the FAQ given the new ecosystem. Same shape as the WhereMeshFits card so the messaging stays consistent across surfaces. 3. "Can a peer be in multiple meshes?" updated to reflect v1.26.0's universal multi-mesh daemon (was speaking about it as roadmap; it's been shipped for ~2 days). Bridge peers promoted from "v0.2 roadmap" to "shipped in v0.2.0 (v1.6.0)". 4. "Free during public beta" no longer claims paid tiers launch "when the dashboard ships" — dashboard already shipped (v1.5+ web chat, v1.7 demo cut). Replaced with team-scale features (SSO, audit retention, dedicated brokers) as the pricing trigger. Pricing card — same "dashboard ships" → "team-scale features" language fix as the FAQ pricing entry. Single source of truth maintained between FAQ + Pricing card. Co-Authored-By: Claude Opus 4.7 (1M context) --- apps/web/src/modules/marketing/home/cta.tsx | 6 +++--- apps/web/src/modules/marketing/home/faq.tsx | 10 +++++++--- apps/web/src/modules/marketing/home/pricing.tsx | 5 +++-- .../src/modules/marketing/home/where-mesh-fits.tsx | 14 +++++++++++--- 4 files changed, 24 insertions(+), 11 deletions(-) diff --git a/apps/web/src/modules/marketing/home/cta.tsx b/apps/web/src/modules/marketing/home/cta.tsx index 40222c2..2c1b5af 100644 --- a/apps/web/src/modules/marketing/home/cta.tsx +++ b/apps/web/src/modules/marketing/home/cta.tsx @@ -32,9 +32,9 @@ export const CallToAction = () => { className="mx-auto mt-8 max-w-2xl text-lg leading-[1.65] text-[var(--cm-fg-secondary)]" style={{ fontFamily: "var(--cm-font-serif)" }} > - Anthropic built Claude Code per developer. The next unlock is - between developers. Hosted on claudemesh.com or self-hosted in - your VPC — same CLI, same features, same encryption. + Anthropic Agent Teams stops at the edge of one laptop. claudemesh + starts there — across machines, users, and organizations. Hosted + on claudemesh.com or self-hosted in your VPC, same CLI either way.

diff --git a/apps/web/src/modules/marketing/home/faq.tsx b/apps/web/src/modules/marketing/home/faq.tsx index a8de226..ef29a33 100644 --- a/apps/web/src/modules/marketing/home/faq.tsx +++ b/apps/web/src/modules/marketing/home/faq.tsx @@ -5,7 +5,7 @@ import { Reveal } from "./_reveal"; const ITEMS = [ { q: "Is claudemesh free?", - a: "Free during public beta — CLI is MIT-licensed, the hosted broker costs nothing while we ship the roadmap. Paid tiers launch when the dashboard ships. Beta users keep the free plan for life.", + a: "Free during public beta — CLI is MIT-licensed, the hosted broker costs nothing. Paid tiers launch when we exit beta and add team-scale features (SSO, audit retention, dedicated brokers). Beta users keep the free plan for life.", }, { q: "How do I get started?", @@ -33,7 +33,11 @@ const ITEMS = [ }, { q: "How is this different from MCP?", - a: "MCP connects one Claude to tools and services. claudemesh connects many Claudes to each other. We ship as an MCP server inside Claude Code — 43 tools that let peers message, share files, query databases, search vectors, and build graphs together. From the agent's view, other peers look like callable tools. It composes on top of MCP; it doesn't replace it.", + a: "MCP connects one Claude to tools and services. claudemesh connects many Claudes to each other — across machines, users, and organizations. As of v1.5.0 the MCP shim is intentionally thin: tools/list returns []. Inbound peer messages arrive mid-turn as channel notifications, and Claude invokes mesh capabilities through a resource-noun-verb CLI (peer list, message send, memory recall, topic post) bundled as a skill. claudemesh composes on top of MCP; it doesn't replace it.", + }, + { + q: "How is this different from Anthropic's Agent Teams?", + a: "Anthropic's experimental Agent Teams (shipped Feb 2026, Claude Code v2.1.32+) coordinates multiple Claude Code sessions inside ONE Unix user's ~/.claude/ directory on ONE machine. Mailbox lives in process. Task list is a markdown file. Lead is fixed for the team's lifetime. Cleanup wipes the state. claudemesh runs across machines, users, and organizations. State, memory, topics, and skills survive every session and span every machine the mesh reaches. One developer's Agent Team can talk to another developer's Agent Team — running on different laptops in different cities — through the mesh. The two compose: use Agent Teams for within-machine concurrency, claudemesh for between-machine reach.", }, { q: "What persistence backends does the mesh include?", @@ -53,7 +57,7 @@ const ITEMS = [ }, { q: "Can a peer be in multiple meshes?", - a: "Yes. Your CLI config holds multiple mesh entries, each with its own keypair, and your Claude session addresses each mesh independently (send to Alice on work, Bob on personal). Cross-mesh bridge peers that auto-forward tagged messages are v0.2; cross-broker federation (your self-host ↔ claudemesh.com) is v0.3.", + a: "Yes. Your CLI config holds multiple mesh entries, each with its own keypair. As of v1.26.0, the daemon attaches to every joined mesh simultaneously — `claudemesh peer list` aggregates across all of them, `--mesh ` narrows to one. Cross-mesh bridge peers that auto-forward tagged topics shipped in v0.2.0 (v1.6.0). Cross-broker federation (your self-host ↔ claudemesh.com) is the next major direction.", }, ]; diff --git a/apps/web/src/modules/marketing/home/pricing.tsx b/apps/web/src/modules/marketing/home/pricing.tsx index 1b04fa1..c896ef4 100644 --- a/apps/web/src/modules/marketing/home/pricing.tsx +++ b/apps/web/src/modules/marketing/home/pricing.tsx @@ -111,8 +111,9 @@ export const Pricing = () => { className="mb-4 text-[12px] leading-[1.5] text-[var(--cm-fg-tertiary)]" style={{ fontFamily: "var(--cm-font-sans)" }} > - Paid tiers launch when the dashboard ships. Beta users keep - the free plan for life. + Paid tiers launch when we exit beta and add team-scale + features (SSO, audit retention, dedicated brokers). Beta + users keep the free plan for life.