Use your own Composio

Run Hermes and OpenClaw on Pusk with your own Composio API key: a forkable kit with a Composio MCP proxy you host, per-agent account isolation, OAuth connect, and per-agent tool-call metering.

Every instance ships with managed Composio: zero setup, and Pusk meters the agent's tool calls from your wallet. When you'd rather own the integration layer (your COMPOSIO_API_KEY, your Composio project, your users' connected accounts, your own per-user metering), the hermes-openclaw-composio kit is the supported path. It's a complete forkable app in which Hermes and OpenClaw agents reach Gmail, Slack, Notion, GitHub, and hundreds of other apps through a Composio MCP proxy hosted in your own app.

Managed Composio or your own?

Either way the model stays managed: agents chat on Pusk's built-in LLM credentials and that spend is billed per instance as usual. Only the integration layer moves.

How it works

agent instance (Hermes or OpenClaw, on Pusk Cloud)
  └─ MCP client: apps → https://your-app.com/api/composio-mcp   (per-agent token)
        └─ your app: token → agent → Composio tool-router session
             scoped to one Composio user per agent (isolated accounts)
             every tools/call metered per agent, per day
                └─ Composio → Gmail / Slack / Notion / …

• Your key stays home. The instance only ever holds a revocable per-agent proxy token; the Composio API key lives in your app's environment and never reaches an instance or the browser.
• Per-user isolation. Each agent maps to its own Composio user, and Composio binds account resolution server-side, so one user's Gmail can never surface in another user's agent.
• Per-user metering. The proxy counts every billable tools/call into Postgres, shown per agent in the kit's Integrations tab, the basis for your own limits or billing.
• Clean base images. The kit publishes two workspace templates built on Pusk's hermes-base and openclaw-base images. The stock templates rewrite their integration wiring on every boot; these never do, so your Composio config survives restarts and updates. The bases themselves boot with no model or integration config; the kit's post-create bootstrap writes both the managed model and your Composio MCP endpoint into each agent.

Get started

1. Get your keys

   Three secrets, each behind a login: an sk_live_ API key from a funded workspace (see Billing), your COMPOSIO_API_KEY from platform.composio.dev, and a Supabase access token; the kit provisions a free Supabase project for you.

2. Clone it

   git clone https://github.com/pusk-platform/hermes-openclaw-composio
   cd hermes-openclaw-composio
   

3. Run setup

   The fastest path is agent-driven: open the folder in Claude Code or Codex and paste the setup prompt from the README. It asks for your three keys, provisions Supabase, publishes the kit's two agent templates into your workspace (the Hermes one via an Pusk cloud build, so no local Docker is needed), and starts the app.

   By hand: npm install, then npm run setup twice. The first run creates .env.local and exits asking for the keys; paste them in and run it again, then run npm run templates:publish.

4. Run it

   npm run dev
   

   Open http://localhost:3000, sign up, and create an agent. Agents run on Pusk Cloud, so tool calls need your app on a public URL. In dev, npm run dev starts a free cloudflared quick tunnel automatically (it needs the cloudflared binary, brew install cloudflared, but no Cloudflare account) and agents wire themselves to it; in production it's just your deployed URL. The repo's SETUP.md has the authoritative steps and the Vercel deploy guide.

What you get

The kit is the Pusk white-label dashboard with the integration layer swapped: the same multi-tenant app (email sign-in, workspaces, instance management, native Chat and Files tabs) plus an Integrations tab that browses your Composio catalog, runs OAuth connects against your project, and shows each agent's tool calls over the last 30 days. Fork it, rebrand it (src/config/branding.ts), and ship it.