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.

Credentials go into Summer's built-in secrets manager through the UI or CLI. An MCP client can inspect credential metadata and guide setup, with secret entry through the UI or a local CLI handoff. A Doppler account is not required. The agent uses local environment variables for CLI uploads unless you choose an existing Doppler connection.

Copy the prompt

When agent setup is available for your workspace, open Company setup → Set up with your AI agent. Select Open in ChatGPT Desktop or Open in Claude Code to open the app with your setup prompt filled in. Choose your website project and review the prompt before sending it. These links do not sign you in or grant Summer access.

Use Copy setup prompt for an existing chat, Cursor, or if your browser cannot open the app. The Company setup version includes your company ID. This guide provides a generic version and Markdown at /docs/agent-setup.md once setup is released.

Check the connection

Run summer doctor --json before sign-in to check that the API address and sign-in service are reachable. Then run summer login --scope setup --json and approve the connection in your browser. Run summer whoami --json to verify access. You do not need to copy a token from the Summer dashboard or paste it into chat.

Agent-assisted setup is not released for this deployment yet. The install prompt and app links will appear here when it is available.

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 NEXTConnect an MCP client →