Skip to content
Summer Docs
DocumentationOpen Summer ↗
Documentation /

Set up with your AI agent

Copy the setup prompt and let a coding agent connect your website to Summer.

Use a coding agent, such as Claude Code, Codex or Cursor, to connect your website project to Summer. The agent uses the Summer CLI and asks you to approve its connection in your browser. You keep the decisions that matter: production messaging, credential replacement and business actions.

Copy the prompt

In Summer, open Company setup and select Copy setup prompt under Set up with your AI agent. That version already includes your company ID. The generic version is below, and as Markdown at /docs/agent-setup.md.

# Set up Summer in this project

You are helping me connect this project to Summer, our customer support platform. Work in this repository and use the Summer CLI. Summer is a separate service with its own API; do not use any other company's API or credentials for this.

Summer details:
- API: https://api.gosummer.ai
- Company ID: YOUR_COMPANY_ID
- Environment for this setup: staging
- Summer CLI: run `npx --yes @gosummer/cli@0.1.0 <command>`. The steps below write this as `summer <command>`. Add `--api https://api.gosummer.ai` to each command if that is not `https://api.gosummer.ai`.
- Optional MCP server: https://api.gosummer.ai/mcp

## Steps

1. Inspect this project first. Identify the framework, how pages are rendered, how users sign in and sign out, and where server-side secrets are configured. Do not print or dump environment files or secret values.
2. Check access with `summer whoami --json`. If you are not signed in, run `summer login --scope setup --json` and ask me to approve the connection in my browser. Wait for my approval; do not try to complete sign-in or consent yourself. If the result says access is pending, stop and tell me.
3. Read what Summer can do here: `summer capabilities --company YOUR_COMPANY_ID --environment staging --json` and `summer status --company YOUR_COMPANY_ID --environment staging --json`. Treat every `unavailable` item and its reason as real. Do not work around it.
4. Write a `summer.setup.json` file that describes only what this project needs: the website Messenger installation (exact site origins), the provider credentials to save by environment-variable name, and any edits to existing company knowledge with a reason. Never put a secret value in this file. Keep existing installations, credentials, knowledge and unrelated project files; set `replace: true` on a credential only if I ask.
5. Run `summer setup plan --file summer.setup.json --out summer.plan.json --json` and show me the plan summary. Company settings and knowledge are company-wide: an edit there affects every environment, including production. Tell me before applying such a step.
6. Apply with `summer setup apply --plan summer.plan.json --file summer.setup.json --json`. Credentials are read by the CLI from the environment variables you name and are sent straight to Summer; the Messenger signing key is written by the CLI to the server-side file you chose (for example `.env.local`, which must be ignored by Git). Never read, echo or copy these values yourself. If a step is `stale`, plan again. If a step is `uncertain`, read the current state and follow the returned next step instead of retrying blindly.
7. Integrate the Messenger widget using the existing sign-in system of this project: load the Summer loader, boot it with the installation ID, and add a small server endpoint that signs the identity assertion for the signed-in user with the signing key from server configuration. Follow https://gosummer.ai/docs/install-messenger and https://gosummer.ai/docs/verified-identity. Do not replace this project's authentication.
8. Test locally with synthetic accounts: guest use, sign-in, sign-out and switching accounts, and the site's Content-Security-Policy. Run `summer messenger check --url <local page> --installation <id> --json` and `summer verify --company YOUR_COMPANY_ID --environment staging --json`. A check reported as `unsupported` has not passed.

## Report back

Report each item separately as saved, verified, pending, unavailable or enabled, with the resource IDs and the next step for anything not finished. Saved is not verified.

## Limits

- Do not commit, push or deploy unless I ask. Do not change production or enable production messaging; those need my explicit approval in Summer.
- Do not install global tools or skills, and do not overwrite AGENTS.md or other agent instructions.
- You cannot approve business actions, reveal saved credentials, approve Summer access or raise spending limits. Ask me to do those in Summer.

What the agent does

  1. Reads your project to find its framework, sign-in and server configuration, without printing secrets.
  2. Connects with summer login after you approve it in your browser.
  3. Reads Summer's capabilities and current setup, and respects every unavailable item.
  4. Writes a non-secret summer.setup.json, plans the changes and shows them to you.
  5. Applies the plan. The CLI sends selected credentials directly to Summer and writes the Messenger signing key into your ignored server configuration file.
  6. Adds the Messenger widget using your existing sign-in. See Install the messenger and Connect signed-in accounts.
  7. Tests guest use, sign-in, sign-out and account switching with synthetic accounts, then reports what is saved, verified, pending, unavailable or enabled.

What stays with you

The agent does not commit, push or deploy unless you ask. It cannot approve business actions, reveal saved credentials, approve Summer access, raise spending limits or turn on production messaging without the permission you grant for that. Review its connection any time in Your account → Security → Agent connections.

UP NEXTTroubleshooting and support →