Summer

npx add-mcp 'https://api.gosummer.ai/mcp'

Dê ao seu agente de programação o prompt de configuração do Summer AI e deixe-o conduzir a instalação no seu projeto de site. Ele pode adicionar o Messenger de suporte, conectar seus usuários autenticados, enviar políticas da empresa em Markdown e ajudar a configurar as ferramentas por trás dos seus casos de suporte. O prompt também abrange guias para clientes, capturas de tela, vídeos e uploads de arquivos, com verificações separadas de pré-visualização, publicação e hospedagem.

Use o Claude Code, Codex, Cursor ou outro agente de programação capaz de editar seu projeto e executar comandos de terminal. O agente usa a Summer AI CLI, mostra as alterações propostas e pede que você faça login pelo navegador.

Já tem o Summer AI configurado? Conecte seu cliente MCP para ler casos, solicitar investigações e gerenciar o conhecimento da empresa a partir do seu assistente de IA.

Comece com um fluxo de trabalho útil

Diga ao agente o que sua equipe atende e quais ferramentas você usa. Por exemplo:

Adicione o suporte do Summer AI a este site. Usamos o Intercom para conversas e o Stripe para cobrança. Leia o guia de configuração do Summer AI, inspecione nosso projeto e me mostre um plano para instalar o Messenger e conectar esses serviços. Use o ambiente de staging primeiro e me diga o que ainda precisa ser verificado.

O diretório de conexões de serviços abrange centrais de atendimento, plataformas clínicas, farmácias, cobrança e envio. Escolha um caso de suporte representativo para verificar o fluxo de trabalho completo antes da implantação.

As credenciais vão para o gerenciador de segredos integrado do Summer AI pela interface ou pela CLI. Um cliente MCP pode inspecionar os metadados das credenciais e orientar a configuração, com a inserção de segredos pela interface ou por uma transferência local via CLI. Não é necessária uma conta Doppler. O agente usa variáveis de ambiente locais para uploads via CLI, a menos que você escolha uma conexão Doppler existente.

Copie o prompt

Abra Company setup → Set up with your AI agent. Selecione Open in ChatGPT Desktop ou Open in Claude Code para abrir o aplicativo com seu prompt de configuração preenchido. Escolha seu projeto de site e revise o prompt antes de enviá-lo. Esses links não fazem login nem concedem acesso ao Summer AI. Se a configuração não estiver disponível para sua implantação, entre em contato com o suporte do Summer AI.

Use Copy setup prompt para um chat existente, para o Cursor ou se o navegador não conseguir abrir o aplicativo. A versão de Company setup inclui o ID da sua empresa. O prompt genérico abaixo também está disponível como Markdown quando a configuração está habilitada.

Verifique a conexão

Execute summer doctor --json antes do login para verificar se o endereço da API e o serviço de login estão acessíveis. Em seguida, execute summer login --scope setup --json e aprove a conexão no navegador. Execute summer whoami --json para verificar o acesso. Você não precisa copiar um token do painel do Summer AI nem colá-lo no chat.

# Set up Summer in this project

Set up Summer for this business in this repository. Use authorized company knowledge and tools to understand workflows and test them. Configure Summer through its API, CLI or MCP. Keep service credentials separate; Summer tokens are only for Summer.

Test how Summer handles the business's support cases. A capability passes when Summer can find and use its API, browser, knowledge or connected-tool path. Tool names are hints. Complete available setup and record precise blockers.

Summer details:
- API: https://api.gosummer.ai
- Company ID: YOUR_COMPANY_ID
- Environment for this setup: staging
- Summer CLI: run \`npx --yes @gosummerai/cli@0.1.1 <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

If the Company ID is \`YOUR_COMPANY_ID\`, run \`summer companies --json\` after sign-in and use the selected company's ID in every command and setup file. If more than one company is available and the project does not identify one, ask me to choose.

Use Summer's built-in secrets manager for provider credentials. Customers can save values in Settings → Integrations with **Store in Summer**, or through the CLI using \`--from-env\`, \`--from-file\` or \`--from-stdin\`. If using MCP, list credential metadata there and use \`summer_credentials_set\` with \`source: local_value\` for a local CLI handoff. Never put secret values in MCP arguments or chat. Doppler is optional; do not ask me to set up Doppler or a vault unless I choose it.

The original setup consent covers normal Messenger installation, embed changes and activation within the selected company/environment and current spending limit. Do not add a separate installation approval or escalate routine setup to another agent. A setup grant does not approve customer business actions, investigations, budget increases or clinical directions.

## Write for the reader

Address customers in guides and staff in procedures. Follow ASD-STE100 about 80%: instructions under 20 words, descriptions under 25, active voice, one idea per sentence, consistent terms, no metaphors or slang. Keep necessary facts and uncertainty.

## Steps

1. Inspect this project and relevant company guidance first. Identify products, customer requests, care and fulfillment flows, billing, refunds, subscriptions, support channels, policies, promises and existing tools. Find where operational facts live and how an agent can discover them. Identify the framework, sign-in and server-side secret configuration too. Do not print or dump environment files or secret values. Use only relevant company material; keep patient records in their authorized case.
2. Run \`summer doctor --json\` to check the API address and sign-in service. If it reports a failed check, explain the returned reason before continuing. Check access with \`summer whoami --json\`. If you are not signed in, run \`summer login --json\` and ask me to approve the connection in my browser. Wait for the browser consent or my explicit approval of that connection. Use an existing authorized connection without asking again. If the result says access is pending, stop and tell me.
3. Read \`summer capabilities --company YOUR_COMPANY_ID --environment staging --json\`, \`summer status --company YOUR_COMPANY_ID --environment staging --json\` and \`summer capability-checks list --company YOUR_COMPANY_ID --environment staging --json\`. \`operational_readiness\` is the same checklist shown in Company setup → What Summer can do. Read each expectation, concrete test, prior evidence and discovery hints. Treat unavailable permissions as real. A missing named provider tool can have an available browser or knowledge alternative; discover and test those within your authority.
4. Match each checklist gap to useful setup work. Write a non-secret \`summer.setup.json\` with the company settings, Messenger installation (when needed), selected credential environment-variable names and knowledge files to create or edit. Each knowledge entry has \`id\`, \`file\` and \`reason\`; a new document can also set \`path\` under \`company/\` and \`tags\`. Reuse current documents rather than duplicate policies. Upload current policies, workflow guides, escalation contacts and discovery instructions that Summer needs. Explain original sources and known gaps. Keep unrelated files and existing setup; set \`replace: true\` on credentials 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. If this business needs Messenger, integrate the 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. For a Messenger installation, 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\`. Run \`summer verify --company YOUR_COMPANY_ID --environment staging --json\` for the configured connections. A check reported as \`unsupported\` has not passed.
9. Inspect \`summer integrations\` and \`summer credentials list\`. For missing providers, use \`integrations save custom-NAME --from-file integration.json --expected-version N\` with a name and fields (name, label, required), never values. Transfer secrets through the local CLI. Create guidance with \`knowledge create ID --from-file guide.md --path company/guide.md --reason TEXT\`, or edit its current revision. Verify Summer can discover and use each connection; saved configuration alone is insufficient.
10. Check each capability against its concrete test and authorized sample. Use original live records where needed. Local-only tools cannot pass Summer runtime access. Record Blocked with the missing path. \`capability-checks test ID --case CASE_ID --expected-version N\` requests an existing read-only investigator (needs setup and investigations.request; cases.read reads results). Obtain missing grants through consent. Inspect effect paths without executing them. Never replace case work or resume the backlog.
11. Save findings with \`summer capability-checks report ID --from-file result.json --expected-version N --company YOUR_COMPANY_ID --environment staging --json\` at the latest version. The file has \`state\` (\`passed\`, \`failed\`, \`blocked\`, \`not_checked\`, \`not_applicable\`), \`notes\`, \`evidence\` and, for a pass, \`fulfillment: {kind: api|browser|knowledge|other|combined, discovery: "how Summer finds it", location: "guide, tool or portal reference"}\`. Keep evidence references and observation times, without secrets or patient details. Reports are agent-reported. An assumed integration, saved secret, untested guide or different path cannot pass. Inspect action paths and exact approval requirements without executing effects.
12. Add important business-specific capabilities from actual products, workflows and recurring support needs. Prefer customer/team outcomes over endpoints. Create a definition with \`id\` (starting \`custom_\`), \`title\`, \`group\`, \`mode\` (\`read\` or \`approval\`), \`expectation\`, \`test\` and \`examples\` (discovery hints or an empty string). Save with \`summer capability-checks save ID --from-file definition.json --expected-version 0 --reason TEXT --company YOUR_COMPANY_ID --environment staging --json\`. Record the original business source, concrete test and passing evidence. Add supporting knowledge/integrations and assess it like the starter checks. Improve existing definitions at their current version rather than duplicate them. Explain inapplicable starters.

## Check versions

If the last successful check is unknown or seven days old, or a tool/command is
missing, run \`summer version --check --json\` and \`summer client-status --json\`
(MCP: \`summer_client_status\`). Update from published npm releases. Refresh MCP
initialization and tools/list when its version changes. Keep existing scopes on
reconnect; updates never grant permissions.

## Support email

Read https://gosummer.ai/docs/support-email before configuring support email. Test reading, replies and DNS separately; Intercom's account check tests neither inbox nor replies. Gmail/Outlook connectors and email DNS commands are not released. Record evidence and gaps in capability checks. Contact capture sends no email.

## Customer guides, Markdown and media

Read \`summer guides authoring --company YOUR_COMPANY_ID --json\` (MCP:
\`summer_guides_authoring\`) for instructions, schemas, media syntax and draft
context. Use native file, browser and media tools. Guides need CLI 0.2.0+ and its matching
deployment. Report release gaps; never invent uploads or hosted URLs.

Inventory the full product, conditional features and account controls. Reuse
existing guides. Write task-focused Markdown with direct product links, sources
and check dates. Capture real UI with synthetic or authorized data and label
examples. Keep private procedures, personal data and medication directions out
of public articles. Use \`--company YOUR_COMPANY_ID --json\` with this journey:

1. Read \`guides get\`, \`guides article get ID\` and \`assets list\`. Configure the
   guide with \`guides save\` at the current version.
2. Upload actual files with \`assets upload --from-file PATH --metadata-file
   media.json\`, including alt text, provenance and captions/transcripts. Confirm
   ready asset IDs; resume the same file with \`--resume ASSET_ID\`. The trusted
   local CLI transfers bytes; no binaries/base64 or credentials in MCP context.
3. Save Markdown with \`guides article save ID --from-file article.md
   --metadata-file article.json --revision N --reason TEXT\`. New articles use
   revision 0. Open \`guides preview\`; check media, downloads, search, section
   links, phone/desktop layout and product links through sign-in.
4. Show the exact preview. Publishing needs human authority and separate
   \`guides.publish\` consent. When requested, use \`summer login --scope
   setup,guides.publish --json\`, then \`guides publish --from-file release.json
   --expected-version N --reason TEXT\` with exact article revisions. Verify
   public/Markdown URLs. Saved drafts are not public.
5. If requested, use \`guides hosting get/save/verify\`, follow returned DNS
   instructions and verify ownership, provider setup and HTTPS separately.

All roles use the same published articles. Humans edit them in Knowledge with history.

## Check Summer first

Ask before adding this rule to the end of AGENTS.md or CLAUDE.md:
"For a customer, ticket or order question, first run \`summer cases search TEXT --company YOUR_COMPANY_ID --json\` (name, email, phone, ID; \`--dob\`, \`--messages\`) or MCP \`summer_cases_search\`. Read the case before investigating locally. Results are leads."

## Report back

Use the shared operation catalog for workspace setup as well as installation.
Guest attachment and abuse limits live in installation settings; chat concurrency
and daily limits live in assistant settings. Use \`messenger.conversations.list\`
for the complete inbox, including visitors without Ops cases. Business hours,
saved replies/views, assignment, reports, quality scenarios and privacy-request
tracking have named API/MCP operations. Read current revisions before saving.
Members can grant \`workspace.write\` for personal views and quality assessments;
shared views and administrator settings keep their existing role checks.

Refresh \`summer status\` and \`summer capability-checks list\`. Report actual setup/capability states, evidence, discovered paths, business-specific additions, blockers and next steps. Saved is not verified; an agent report is not independent execution verification. Keep dashboard records current for human review.

Report guide topics, revisions, returned URLs and gaps. Distinguish drafts, uploads and verified publication.

## Limits

- Do not commit, push or deploy unless I ask. Complete authorized Messenger setup, including production, without asking for the same permission again. Use a returned local CLI handoff yourself when available. Ask only for missing company access, environment access or authority.
- Do not overwrite agent instructions or install unrelated tools.
- With actions.approve, approve exact prepared work I authorize using its review hash; no repeated UI approval. Never invent authorization. Secret reveal, access/role grants, spending increases, identity attestations and clinical directions stay restricted.
- Do not perform customer effects during onboarding tests. Only clinicians provide medication directions; do not write, quote, paraphrase or calculate them in guides, test reports or replies. Route those questions to the authenticated clinical channel.

O que o agente faz

1. Lê seu projeto para encontrar seu framework, configuração de login e de servidor, sem exibir segredos.
2. Conecta-se com summer login depois que você aprova no navegador.
3. Lê os recursos e a configuração atual do Summer AI e respeita cada item indisponível.
4. Grava um summer.setup.json sem segredos, planeja as alterações e mostra a você.
5. Aplica o plano. A CLI envia as credenciais selecionadas diretamente ao Summer AI e grava a chave de assinatura do Messenger no seu arquivo de configuração de servidor ignorado.
6. Adiciona o widget do Messenger usando seu login existente. Consulte Install the messenger e Connect signed-in accounts.
7. Testa o uso como convidado, login, logout e troca de conta com contas sintéticas.
8. Percorre a mesma lista de verificação de capacidades operacionais exibida no Summer AI. Ele pode enviar guias da empresa, definir integrações personalizadas, salvar segredos selecionados pela CLI e testar caminhos de API, navegador ou conhecimento que possam ser descobertos.
9. Registra evidências e lacunas restantes na lista de verificação, rotuladas visivelmente como relatadas pelo agente de configuração. Uma credencial ou um guia salvo, por si só, não aprova uma capacidade.
10. Adiciona capacidades importantes com base nos produtos, fluxos de trabalho e solicitações de suporte recorrentes exclusivos da empresa, com testes concretos e instruções de descoberta de apoio.

O que fica com você

O agente não faz commit, push nem implantação, a menos que você peça. Com actions.approve delegado, ele pode aprovar trabalhos de caso preparados e exatos que você autorizar. Ele não pode inventar autorização, revelar credenciais salvas, aprovar acesso ao Summer AI nem aumentar limites de gastos. O envio de mensagens em produção precisa de sua própria permissão concedida. Revise a conexão dele a qualquer momento em Your account → Security → Agent connections.

O que devo ter quando a configuração estiver concluída?

Você deve ter um Messenger funcionando no seu site de teste, o comportamento de login e logout verificado e os guias da empresa salvos no Summer AI. O agente deve mostrar quais conexões de serviços testou, as evidências que encontrou e o que ainda está faltando.

Peça a ele para mostrar o inventário de tarefas do cliente, o Markdown preparado, capturas de tela, imagens ou vídeos e os links de produtos verificados. Consulte Prepare customer guides para o escopo atual. Seu agente deve mostrar os recibos de upload concluídos e a pré-visualização exata do guia. A publicação precisa da permissão separada guides.publish. Um arquivo local ou rascunho salvo não é um guia publicado; verifique o endereço público retornado. Domínios personalizados também precisam de DNS verificado e HTTPS funcionando.

Experimente uma solicitação de suporte representativa e compare as descobertas do Summer AI com os registros originais. Revise as lacunas restantes antes de habilitar o envio de mensagens em produção. Consulte Security and testing para as verificações de implantação.