/chat-agent-builder

Agent 87/89: Chat Agents, Any Platform (S7 Builders)

Builds AI chat agents on any platform other than GHL: a website-embedded widget added to the site /build-website already built, and (Slack mode, #89) a real two-way Slack app via Slack's Events API and Web API -- never the one-way webhook bridge /ghl-chat-agent-builder's Slack mode (#88) uses. AI disclosure opens every conversation as a non-removable default.

verified (fixture) 2026-09-08 · needs-connector: slackv0.1.0

Run it All agents

Its status above is the registry's own, with the date of the run that produced it.

What it is for

Contract A

#87 — Build chat agents (any platform) · as #85
#89 — Chat agents for Slack (any platform) · mode `slack`

Example requests

“build us a chat agent that isn't on GHL”
“add an AI chat widget to our site”
“get our chat agent talking on Slack for real”
“chat agent builder”

What it needs, and what it hands back

Needs connected

vercel

Better with: slack.

Uses create_repository, create_git_project, get_deployment, which exist in Claude Code. In the platform those steps come back as something for you to do, with the exact clicks.

Hands back

clients/<business-slug>/plans/chat-agent/<date>.md (agent spec, widget route, and once connected: Slack read-back)

Stops and asks

Nothing this agent does is irreversible on its own, so it asks for no approval of its own. Spending, sending and publishing are approved wherever they happen.

Steps it cannot do through an API, and hands you instead: the user creates the Slack app at api.slack.com and enables Event Subscriptions + chat:write -- Slack's own official flow, never performed on the user's behalf.

How it runs

These are the headings of its own written instructions — 218 lines you can read and change.

Step 0 — Environment, connection, and profile
Step 1 — Design the agent
Step 2 — Website widget (once a site exists)
Step 3 — Slack mode (#89): a real two-way app