From 1ebabef486a7cef290f44a5f05fc6cb6e5988881 Mon Sep 17 00:00:00 2001 From: Rhys Sullivan <39114868+RhysSullivan@users.noreply.github.com> Date: Mon, 3 Aug 2026 14:59:52 -0700 Subject: [PATCH] Lead landing page with agent sprawl and multi-account --- apps/marketing/src/pages/index.astro | 110 +++++++++++++++++++++++++-- 1 file changed, 102 insertions(+), 8 deletions(-) diff --git a/apps/marketing/src/pages/index.astro b/apps/marketing/src/pages/index.astro index cd0940b87..81eaffd6a 100644 --- a/apps/marketing/src/pages/index.astro +++ b/apps/marketing/src/pages/index.astro @@ -138,9 +138,10 @@ Source (and the place to start if something breaks): https://github.com/UsefulSo

- Executor is an MCP gateway. Anything that speaks MCP, like Claude - Code, Cursor, or Codex, points at one endpoint and reaches every - tool you connect. + Every agent you run wants its own connections to your email, + calendar, and tools. Connect them once in Executor; anything that + speaks MCP, like Claude Code, Cursor, or Codex, points at one + endpoint and has them all.

@@ -220,12 +221,85 @@ Source (and the place to start if something breaks): https://github.com/UsefulSo

- Wiring tools to agents is fiddly, per-client, and easy to get wrong. - Executor makes every tool, from any protocol, look the - same: one name, one input - schema, one output schema, so any agent can call any of them - the same way. + You don't have one agent anymore. You have Claude Code, Cursor, a + ChatGPT account, something running in a closet. Each one wants its + own OAuth into everything, and each one is missing + something when you need it.

+

+ Executor ends the re-wiring. Connect a service once and every agent + reaches it through one endpoint, with every tool in the same shape: + one name, one input schema, one output schema. +

+
+ + + {/* ─── MULTI-ACCOUNT ─── */} +
+
+
+
+
Every account
+

+ All your accounts. Not just one. +

+
+

+ Most agent connectors stop at one account per service: one + Google login, so your agent sees your work calendar or your + personal one, never both. Your flights land in one inbox and + your meetings in the other, and no agent can reason over your + actual day. +

+

+ Executor treats accounts as connections: add as many as you + have, per service, side by side. Work and personal Gmail, two + calendars, a staging and a production Stripe. Every agent you + point at Executor sees all of them at once. +

+
+
+
+
+ Connections · google-calendar +
+
+ {[ + { account: "you@company.com", note: "work" }, + { account: "you@gmail.com", note: "personal" }, + ].map(({ account, note }) => ( +
+ {account} + {note} +
+ ))} +
+
+ Connections · gmail +
+
+ {[ + { account: "you@company.com", note: "work" }, + { account: "you@gmail.com", note: "personal" }, + ].map(({ account, note }) => ( +
+ {account} + {note} +
+ ))} +
+

+ One question — "what does my day look like?" — answered across + every account you have. +

+
+
@@ -527,6 +601,26 @@ Source (and the place to start if something breaks): https://github.com/UsefulSo
+
+ + Can I replace my agents' built-in connectors with Executor? + + +
+ Yes, and that is the intended setup: connect your accounts in + Executor, point each agent at it, and disconnect the per-agent + integrations so everything flows through one place. You keep the + same tools and gain what first-party connectors don't offer: + multiple accounts per service, per-tool policies, and one place + to see and revoke access. +
+
+
What can call Executor?