Rename Max Mode to Burn Mode throughout code and docs (#31668)

Follow up to https://github.com/zed-industries/zed/pull/31470.

I started looking at config and changed preferred_completion_mode to
burn to only find its max so made changes to align it better with
rebrand. As this is in preview build now.

This doesn't touch zed_llm_client. Only the Zed changes the code and doc
to match the new UI of burn mode. There are still more things to be
renamed, though.

Release Notes:

- N/A

---------

Signed-off-by: Umesh Yadav <git@umesh.dev>
Co-authored-by: Danilo Leal <daniloleal09@gmail.com>
This commit is contained in:
Umesh Yadav 2025-05-29 18:42:42 +05:30 committed by GitHub
parent f792827a01
commit 703ee29658
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
8 changed files with 44 additions and 39 deletions

View file

@ -3,41 +3,44 @@
Zeds plans offer hosted versions of major LLMs, generally with higher rate limits than individual API keys.
Were working hard to expand the models supported by Zeds subscription offerings, so please check back often.
| Model | Provider | Max Mode | Context Window | Price per Prompt | Price per Request |
| ----------------- | --------- | -------- | -------------- | ---------------- | ----------------- |
| Claude 3.5 Sonnet | Anthropic | ❌ | 60k | $0.04 | N/A |
| Claude 3.7 Sonnet | Anthropic | ❌ | 120k | $0.04 | N/A |
| Claude 3.7 Sonnet | Anthropic | ✅ | 200k | N/A | $0.05 |
| Claude Sonnet 4 | Anthropic | ❌ | 120k | $0.04 | N/A |
| Claude Sonnet 4 | Anthropic | ✅ | 200k | N/A | $0.05 |
| Model | Provider | Burn Mode | Context Window | Price per Prompt | Price per Request |
| ----------------- | --------- | --------- | -------------- | ---------------- | ----------------- |
| Claude 3.5 Sonnet | Anthropic | ❌ | 60k | $0.04 | N/A |
| Claude 3.7 Sonnet | Anthropic | ❌ | 120k | $0.04 | N/A |
| Claude 3.7 Sonnet | Anthropic | ✅ | 200k | N/A | $0.05 |
| Claude Sonnet 4 | Anthropic | ❌ | 120k | $0.04 | N/A |
| Claude Sonnet 4 | Anthropic | ✅ | 200k | N/A | $0.05 |
## Usage {#usage}
The models above can be used with the prompts included in your plan. For models not marked with [Max Mode”](#max-mode), each prompt is counted against the monthly limit of your plan.
The models above can be used with the prompts included in your plan. For models not marked with [Burn Mode”](#burn-mode), each prompt is counted against the monthly limit of your plan.
If youve exceeded your limit for the month, and are on a paid plan, you can enable usage-based pricing to continue using models for the rest of the month. See [Plans and Usage](./plans-and-usage.md) for more information.
Non-Max Mode usage will use up to 25 tool calls per one prompt. If your prompt extends beyond 25 tool calls, Zed will ask if youd like to continue, which will consume a second prompt.
Non-Burn Mode usage will use up to 25 tool calls per one prompt. If your prompt extends beyond 25 tool calls, Zed will ask if youd like to continue, which will consume a second prompt.
## Max Mode {#max-mode}
## Burn Mode {#burn-mode}
In Max Mode, we enable models to use [large context windows](#context-windows), unlimited tool calls, and other capabilities for expanded reasoning, to allow an unfettered agentic experience.
> Note: "Burn Mode" is the new name for what was previously called "Max Mode".
> Currently, the new terminology is only available in Preview and will follow to Stable in the next version.
Because of the increased cost to Zed, each subsequent request beyond the initial user prompt in Max Mode models is counted as a prompt for metering.
In Burn Mode, we enable models to use [large context windows](#context-windows), unlimited tool calls, and other capabilities for expanded reasoning, to allow an unfettered agentic experience.
In addition, usage-based pricing per request is slightly more expensive for Max Mode models than usage-based pricing per prompt for regular models.
Because of the increased cost to Zed, each subsequent request beyond the initial user prompt in Burn Mode models is counted as a prompt for metering.
> Note that the Agent Panel using a Max Mode model may consume a good bit of your monthly prompt capacity, if many tool calls are used.
In addition, usage-based pricing per request is slightly more expensive for Burn Mode models than usage-based pricing per prompt for regular models.
> Note that the Agent Panel using a Burn Mode model may consume a good bit of your monthly prompt capacity, if many tool calls are used.
> We encourage you to think through what model is best for your needs before leaving the Agent Panel to work.
By default, all threads and [text threads](./text-threads.md) start in normal mode.
However, you can use the `agent.preferred_completion_mode` setting to have Max Mode activated by default.
However, you can use the `agent.preferred_completion_mode` setting to have Burn Mode activated by default.
## Context Windows {#context-windows}
A context window is the maximum span of text and code an LLM can consider at once, including both the input prompt and output generated by the model.
In [Max Mode](#max-mode), we increase context window size to allow models to have enhanced reasoning capabilities.
In [Burn Mode](#burn-mode), we increase context window size to allow models to have enhanced reasoning capabilities.
Each Agent thread and text thread in Zed maintains its own context window.
The more prompts, attached files, and responses included in a session, the larger the context window grows.
@ -47,5 +50,7 @@ For best results, its recommended you take a purpose-based approach to Agent
## Tool Calls {#tool-calls}
Models can use [tools](./tools.md) to interface with your code, search the web, and perform other useful functions.
In [Max Mode](#max-mode), models can use an unlimited number of tools per prompt, with each tool call counting as a prompt for metering purposes.
For non-Max Mode models, you'll need to interact with the model every 25 tool calls to continue, at which point a new prompt will be counted against your plan limit.
In [Burn Mode](#burn-mode), models can use an unlimited number of tools per prompt, with each tool call counting as a prompt for metering purposes.
For non-Burn Mode models, you'll need to interact with the model every 25 tool calls to continue, at which point a new prompt will be counted against your plan limit.

View file

@ -15,7 +15,7 @@ Please note that if youre interested in just using Zed as the worlds faste
- A `request` in Zed is a response to a `prompt`, plus any tool calls that are initiated as part of that response. There may be one `request` per `prompt`, or many.
Most models offered by Zed are metered per-prompt.
Some models that use large context windows and unlimited tool calls ([Max Mode”](./models.md#max-mode)) count each individual request within a prompt against your prompt limit, since the agentic work spawned by the prompt is expensive to support.
Some models that use large context windows and unlimited tool calls ([Burn Mode”](./models.md#burn-mode)) count each individual request within a prompt against your prompt limit, since the agentic work spawned by the prompt is expensive to support.
See [the Models page](./models.md) for a list of which subset of models are metered by request.