---
name: caac-go
description: Install, verify, and configure the CAAC Go AI chat agent on a website. Use when asked to add CAAC Go, add an AI chat agent or live chat widget to a site, when a CAAC Go widget key (data-key) or caacgo.cresclab.com snippet appears, or when a CAAC Go install needs debugging.
---

# CAAC Go

CAAC Go is an AI agent that answers a website's visitors from that business's own
content, captures leads, and escalates what needs a human. This skill covers
putting it on a site, proving it works, and driving a workspace from an agent.

Product: https://caacgo.cresclab.com · Docs: https://caacgo.cresclab.com/developers

## Install the chat widget (the common task)

You need the workspace's **widget key**. It is a *public* embed key — it ships in
the HTML of every installed site, so it needs no env var and no server-side
proxy. The owner copies it from https://caacgo.cresclab.com/app/channels/website. **Never invent or
guess a key.** If you don't have one, stop and ask.

Paste this **once**, immediately before the closing `</body>` tag, in the file
that renders the shared layout for the whole site:

```html
<script src="https://caacgo.cresclab.com/widget.js" data-key="YOUR_WIDGET_KEY" data-color="#5090FF" async></script>
```

That is the entire install. The widget then appears on every page.

Attributes: `src` (required, must point at `https://caacgo.cresclab.com/widget.js`), `data-key`
(required, the public widget key), `data-color` (optional 6-digit hex accent),
`async` (recommended).

### Rules that prevent the usual mistakes

- **Site-wide, not per-page.** Put it in the root layout / base template / footer
  include. Installing it on one route is the single most common failure.
- **Verbatim.** Don't edit `data-key`, rename attributes, or reformat the tag.
- **Once.** A second copy renders a second launcher.
- **Don't vendor it.** Never download, bundle, or proxy `widget.js` — it is served
  `max-age=0` so fixes reach installed sites immediately.
- **No wrapper component** unless the framework genuinely can't take a raw
  `<script>` in the layout; then use that framework's standard script hook with
  the same `src` and `data-*` attributes, still loading site-wide.
- **Single-page apps** need no special handling: a plain tag in the HTML shell is
  correct, and the widget does not need re-running per client-side navigation.

### Inline variant (rare)

When the chat should sit *inside* a page's content instead of floating, use this
on that one page only — never in the shared layout:

```html
<iframe src="https://caacgo.cresclab.com/widget/YOUR_WIDGET_KEY" width="100%" height="600" style="border:0;border-radius:12px" title="Chat"></iframe>
```

### Website builders

- **Shopify** — Easiest: connect Shopify in Integrations — the widget turns on from your theme editor, no code. Or paste the snippet via Online Store → Themes → ⋯ → Edit code → theme.liquid, just before </body>.
- **WordPress** — Install a header/footer scripts plugin (e.g. WPCode) and paste this into the Footer.
- **Wix** — Settings → Custom Code → + Add Custom Code → paste → place in “Body - end”.
- **Squarespace** — Settings → Advanced → Code Injection → Footer → paste there.
- **Google Tag Manager** — Tags → New → Custom HTML → paste the snippet → trigger “All Pages” → Save → Submit.

## Verify

Confirm the tag is in the **deployed** HTML, not just the source:

```bash
curl -s https://the-site.example | grep -o 'widget\.js[^>]*'
```

Then tell the owner to click **Test my install** at
https://caacgo.cresclab.com/app/channels/website — that fetches their live site, looks for the
snippet, and marks the widget live, so a correct install on a zero-traffic site
is confirmed without waiting for a visitor. It scans the homepage source, so it
can't confirm the inline-frame variant or a tag-manager install — those register
when someone opens the page.

If the tag is present but no launcher appears, check in this order: the widget is
switched off in the dashboard; the site's domain isn't allowed under Settings →
Security; host CSS is hiding the launcher.

## Configure a workspace from an agent (optional, Growth plan and up)

The Developer API and the MCP server both authenticate with a workspace API key
(`Authorization: Bearer cwa_…`, created at https://caacgo.cresclab.com/app/settings/api) and are a
Growth-plan-and-up entitlement — a free or Starter workspace gets a 403 with an
upgrade message, which is expected, not a bug.

- MCP endpoint: `https://caacgo.cresclab.com/api/mcp` — tools to read the install snippet, run the
  install check, update widget appearance, and list or add knowledge sources.
- REST + OpenAPI: https://caacgo.cresclab.com/developers · https://caacgo.cresclab.com/api/v1/openapi.json

Unlike the API, **installing the widget needs no key and works on every plan.**
Don't send an owner to upgrade in order to install.

## Full reference

https://caacgo.cresclab.com/llms-install.txt