Skip to main content
Summer Engine runs on many providers rather than one. Which one handles a given request depends on what you asked for and what you picked in the model selector.

The chat agent

The agent that writes your code and drives the editor is whatever model is selected in the chat composer.
  • Auto (the default, on every plan) routes to a fast long-context coding model chosen for the balance of quality, cost, and reliability. The specific model changes as we improve the routing.
  • MAX (paid plans) routes to a frontier model and maxes out context and tool calls. It uses more of your credits.
  • Picking a model yourself gives you a specific model from OpenAI, Anthropic, DeepSeek, GLM, Kimi, Grok, or Qwen.
The model selector is the live list. It is rendered from the running catalog and it tells you each model’s context window and cost warning. See Models for how selection and plan access work.

Asset generation

Asset generation does not use the chat model. Each asset type has its own backends, and Summer picks one based on the job: In Summer Studio you choose the backend yourself from a picker. In chat, the agent picks one for the job. Some backends use more of your credits than others.

Choosing models

You choose the chat model in the selector next to the composer. Asset backends are chosen per generation inside Summer Studio, where the model list is shown live. Summer does not accept your own provider API keys for hosted generation — hosted AI runs on your plan’s usage. If you want to run your own model against your project, use the MCP server instead: point Cursor, Claude Code, or any other harness at Summer and drive the editor with whatever model you already pay for. We add new models as they come out. The model selector always shows the current list.