Documentation Index
Fetch the complete documentation index at: https://zite.com/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Multi-chat lets you create separate chat threads inside a Zite project. Each chat has its own context, so you can keep different tasks, features, fixes, or experiments separate.
Use multi-chat when you want Zite to focus on the current task without carrying forward every message from an earlier conversation.
In a long chat, the context window moves forward as the conversation grows. Recent messages stay in context, while older messages can fall out of the active window or be summarized through compaction.
Why use a new chat
Starting a new chat gives you more control over context.
| Benefit | What it means |
|---|
| Better focus | Previous messages no longer influence the current task. |
| Lower credit usage | Smaller context windows reduce the number of input tokens Zite needs to process. |
| Faster responses | Less context can improve performance, though speed still depends on request complexity. |
When to create a new chat
| Start a new chat when | Why |
|---|
| Starting a different feature | Keeps the new work separate from older decisions. |
| Moving on after a bug fix | Prevents the next task from being shaped by troubleshooting context. |
| A thread feels long or unfocused | Gives Zite a cleaner context window. |
| Testing a different approach | Lets you explore without older messages steering the result. |
| Organizing separate tasks | Creates a clearer record of work inside the same project. |
When to keep using the same chat
Keep using the same chat when the next request depends on the previous conversation.
For example, stay in the same chat if Zite just made a change and you want to refine it, fix something from the same build, or ask a follow-up question about the same task.
Auto-compaction
Zite automatically compacts long chats when they reach around 90% of chat usage. This helps keep the conversation usable when the context gets large.
Multi-chat does not replace auto-compaction. If you keep working in a long chat, auto-compaction will still happen when needed.
The difference is control: multi-chat lets you decide when to start fresh instead of waiting for compaction to happen automatically.
If you are about to start a new feature or unrelated fix, create a new chat first. If you are still refining the same change, stay in the current chat.
Related topics
