Files
cline/docs/model-config/context-windows.mdx
T
Juan Pablo FloresandCopilot 8f8c4561a6 Docs upgrade (#6907)
* style(docs): update background color scheme to neutral tones

Update documentation background colors from purple-tinted theme to neutral gray tones. Changed light mode from lavender (#F0E6FF) to off-white (#fafaf9) and dark mode from pure black (#000000) to dark gray (#0f0f0f) for improved visual consistency.

* refactor(docs): remove gradient decoration from theme config

Remove the "decoration": "gradient" property from the documentation
theme configuration. This simplifies the theme settings by removing
the gradient decoration option from the color configuration object.

* docs: change documentation font family to Geist Mono

Replace Roboto with Geist Mono as the default font family in the documentation configuration. This updates the visual styling of the documentation to use a monospace font, which may improve readability for code-heavy content.

* docs: update branding and restructure navigation

- Replace robot panel logos with new Cline brand logos
- Add icons to navbar links (Docs, GitHub, Discord)
- Restructure navigation from groups to tabs format
- Add icons to navigation items for improved UX
- Include new Docs link in navbar with book icon

This update modernizes the documentation appearance and improves navigation hierarchy for better user experience.

* docs: restructure navigation with hierarchical groups and pages

Restructured documentation navigation from flat menu to organized groups:
- Removed redundant "Docs" link from navbar
- Migrated from "menu" to "groups/pages" structure
- Added comprehensive page organization with nested groups:
  * Introduction, Getting Started, Features
  * Prompting Skills, Cline's Tools, Enterprise Solutions
  * MCP Servers, Provider Configuration
- Organized features into logical subgroups (@ Mentions, Commands,
  Customization, Slash Commands)
- Improved documentation discoverability and hierarchy

This change provides better content organization and easier navigation
for users exploring different aspects of Cline documentation.

* docs: remove contextual options from documentation config

Remove the contextual configuration section containing the "copy" option from docs.json. This simplifies the documentation configuration by removing unused contextual menu options.

* docs(multiroot): improve workspace documentation with limitations and technical details

- Add important note about experimental limitations affecting Cline rules and checkpoints
- Add "How it works" section explaining automatic workspace detection and tracking
- Reorganize technical behavior section with detailed subsections for workspace detection, path resolution, and command execution
- Document workspace hint syntax for explicit file references (@workspaceName:path)
- Standardize heading capitalization to sentence case for consistency
- Improve overall content organization and clarity for better user understanding

This update provides users with clearer information about the multiroot feature's current state, its limitations, and how to effectively use workspace hints when working with multiple project folders.

* docs: restructure overview page with enhanced visual layout

- Convert plain markdown sections to CardGroup and Card components with icons
- Add tabbed interface for Plan & Act Mode explanation
- Update description from "development assistant" to "coding agent"
- Reorganize content for improved readability and visual hierarchy
- Enhance feature presentations with icon-based cards

Improves user experience by transforming the overview documentation into a more visually appealing and scannable format using modern documentation components.

* docs: improve installation guide with enhanced structure and UX

Restructure the Cline installation documentation to improve readability and user experience:

- Add prominent note highlighting 2-minute installation time
- Convert prerequisites into visual card components for better clarity
- Transform installation steps into structured Step components for easier following
- Add manual installation instructions for JetBrains IDEs
- Include feature compatibility accordion for JetBrains users
- Enhance visual hierarchy with improved component usage (CardGroup, Steps, Accordion)
- Simplify language and improve descriptions throughout

This makes the installation process clearer for new users and reduces friction during onboarding.

* style(docs): remove text opacity reduction for better readability

* docs: refactor model selection guide with visual step-by-step instructions

- Replace tab-based layout with linear step-by-step flow
- Add screenshots for each configuration step (config, provider, API, model)
- Reorganize content structure for improved clarity and user experience
- Add quickstart options and streamlined provider recommendations
- Improve navigation with visual aids to help users configure Cline faster

* docs: add installation screenshots and context management guide

* docs: flatten provider config structure in documentation

Remove the "Alternative Providers" grouping and move all provider configuration pages (OpenRouter, Cerebras, DeepSeek, Groq, xAI Grok, Mistral AI, Doubao, Fireworks, and ZAI) to the main provider configuration list. This simplifies the documentation navigation by treating all providers equally rather than categorizing some as alternatives.

* docs: restructure context management docs and improve content clarity

**Changes:**
- Reorganized documentation structure by moving context management from
  `/best-practices` to `/prompting` section for better categorization
- Added URL redirect to maintain backward compatibility for old links
- Updated navigation references in welcome page to point to new location
- Improved readability of context management explanations with more
  narrative, conversational prose
- Enhanced context window documentation by adding cache tokens indicator
  and using emoji-based formatting for better visual clarity
- Streamlined Cline Memory Bank setup instructions from 4 to 3 steps
- Updated context bar screenshot to use newer image asset

**Why:**
Better documentation organization and improved user experience through
clearer explanations of how Cline builds and manages context during tasks.

* docs(context-management): convert Quick Reference to Info component

Replace blockquote formatting with Info component for the Quick Reference
section in the context management documentation. This improves visual
presentation and maintains consistency with documentation standards.

Also removes trailing whitespace at the end of the file for cleaner
formatting.

* docs: add Cline Enterprise overview and restructure enterprise section

- Add comprehensive enterprise overview documentation covering security,
  governance, observability, and developer experience features
- Rename "Enterprise & Security" navigation group to "Enterprise"
- Consolidate enterprise documentation by replacing 4 pages with 2:
  new overview page and security concerns
- Document BYOI (Bring Your Own Inference), SSO authentication, and
  role-based access control capabilities

This restructuring provides a clearer entry point for enterprise users
and consolidates previously scattered enterprise information into a
cohesive overview document.

* docs(enterprise): streamline enterprise overview and update font

- Change documentation font from Geist Mono to Geist Sans
- Add enterprise website link card for detailed information
- Remove Developer Experience, Proven at Scale, and Pricing sections
- Consolidate Flexible Inference section content
- Simplify enterprise overview to focus on core capabilities

These changes reduce redundancy by directing users to the enterprise
website for pricing and detailed features while keeping the docs
focused on technical implementation and core capabilities.

* clean-images

* Update docs/getting-started/installing-cline.mdx

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

* Update docs/styles.css

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

* docs(cline-cli): add platform availability warning to overview

Add a prominent warning callout indicating that Cline CLI is currently in preview and only supports macOS and Linux, with Windows support coming soon. This sets clear expectations for users about platform compatibility.

Also remove redundant introductory text in the "What you can build with this" section to improve content clarity.

---------

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
2025-10-16 11:51:20 -07:00

160 lines
5.3 KiB
Plaintext

---
title: "Context Window Guide"
description: "Understanding and managing AI model context windows"
---
## What is a Context Window?
A context window is the maximum amount of text an AI model can process at once. Think of it as the model's "working memory" - it determines how much of your conversation and code the model can consider when generating responses.
<Note>
**Key Point**: Larger context windows allow the model to understand more of your codebase at once, but may increase costs and response times.
</Note>
## Context Window Sizes
### Quick Reference
| Size | Tokens | Approximate Words | Use Case |
|------|--------|------------------|----------|
| **Small** | 8K-32K | 6,000-24,000 | Single files, quick fixes |
| **Medium** | 128K | ~96,000 | Most coding projects |
| **Large** | 200K | ~150,000 | Complex codebases |
| **Extra Large** | 400K+ | ~300,000+ | Entire applications |
| **Massive** | 1M+ | ~750,000+ | Multi-project analysis |
### Model Context Windows
| Model | Context Window | Effective Window* | Notes |
|-------|---------------|------------------|-------|
| **Claude Sonnet 4.5** | 1M tokens | ~500K tokens | Best quality at high context |
| **GPT-5** | 400K tokens | ~300K tokens | Three modes affect performance |
| **Gemini 2.5 Pro** | 1M+ tokens | ~600K tokens | Excellent for documents |
| **DeepSeek V3** | 128K tokens | ~100K tokens | Optimal for most tasks |
| **Qwen3 Coder** | 256K tokens | ~200K tokens | Good balance |
*Effective window is where model maintains high quality
## Managing Context Efficiently
### What Counts Toward Context
1. **Your current conversation** - All messages in the chat
2. **File contents** - Any files you've shared or Cline has read
3. **Tool outputs** - Results from executed commands
4. **System prompts** - Cline's instructions (minimal impact)
### Optimization Strategies
#### 1. Start Fresh for New Features
```
/new - Creates a new task with clean context
```
Benefits:
- Maximum context available
- No irrelevant history
- Better model focus
#### 2. Use @ Mentions Strategically
Instead of including entire files:
- `@filename.ts` - Include only when needed
- Use search instead of reading large files
- Reference specific functions rather than whole files
#### 3. Enable Auto-compact
Cline can automatically summarize long conversations:
- Settings → Features → Auto-compact
- Preserves important context
- Reduces token usage
## Context Window Warnings
### Signs You're Hitting Limits
| Warning Sign | What It Means | Solution |
|-------------|---------------|----------|
| **"Context window exceeded"** | Hard limit reached | Start new task or enable auto-compact |
| **Slower responses** | Model struggling with context | Reduce included files |
| **Repetitive suggestions** | Context fragmentation | Summarize and start fresh |
| **Missing recent changes** | Context overflow | Use checkpoints to track changes |
### Best Practices by Project Size
#### Small Projects (< 50 files)
- Any model works well
- Include relevant files freely
- No special optimization needed
#### Medium Projects (50-500 files)
- Use 128K+ context models
- Include only working set of files
- Clear context between features
#### Large Projects (500+ files)
- Use 200K+ context models
- Focus on specific modules
- Use search instead of reading many files
- Break work into smaller tasks
## Advanced Context Management
### Plan/Act Mode Optimization
Leverage Plan/Act mode for better context usage:
- **Plan Mode**: Use smaller context for discussion
- **Act Mode**: Include necessary files for implementation
Configuration:
```
Plan Mode: DeepSeek V3 (128K) - Lower cost planning
Act Mode: Claude Sonnet (1M) - Maximum context for coding
```
### Context Pruning Strategies
1. **Temporal Pruning**: Remove old conversation parts
2. **Semantic Pruning**: Keep only relevant code sections
3. **Hierarchical Pruning**: Maintain high-level structure, prune details
### Token Counting Tips
#### Rough Estimates
- **1 token ≈ 0.75 words**
- **1 token ≈ 4 characters**
- **100 lines of code ≈ 500-1000 tokens**
#### File Size Guidelines
| File Type | Tokens per KB |
|-----------|---------------|
| **Code** | ~250-400 |
| **JSON** | ~300-500 |
| **Markdown** | ~200-300 |
| **Plain text** | ~200-250 |
## Context Window FAQ
### Q: Why do responses get worse with very long conversations?
**A:** Models can lose focus with too much context. The "effective window" is typically 50-70% of the advertised limit.
### Q: Should I use the largest context window available?
**A:** Not always. Larger contexts increase cost and can reduce response quality. Match the context to your task size.
### Q: How can I tell how much context I'm using?
**A:** Cline shows token usage in the interface. Watch for the context meter approaching limits.
### Q: What happens when I exceed the context limit?
**A:** Cline will either:
- Automatically compact the conversation (if enabled)
- Show an error and suggest starting a new task
- Truncate older messages (with warning)
## Recommendations by Use Case
| Use Case | Recommended Context | Model Suggestion |
|----------|-------------------|------------------|
| **Quick fixes** | 32K-128K | DeepSeek V3 |
| **Feature development** | 128K-200K | Qwen3 Coder |
| **Large refactoring** | 400K+ | Claude Sonnet 4.5 |
| **Code review** | 200K-400K | GPT-5 |
| **Documentation** | 128K | Any budget model |