| name | windsurf-rate-limits |
| description | Understand and manage Windsurf credit system, usage limits, and model selection.
Use when running out of credits, optimizing AI usage costs,
or understanding the credit-per-model pricing structure.
Trigger with phrases like "windsurf credits", "windsurf rate limit",
"windsurf usage", "windsurf out of credits", "windsurf model costs".
|
| allowed-tools | Read, Grep |
| version | 1.11.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","windsurf","credits","pricing","usage"] |
| compatibility | Designed for Claude Code, also compatible with Codex and OpenClaw |
Windsurf Rate Limits & Credits
Overview
Windsurf uses a credit-based system for AI features. Each prompt to Cascade consumes credits, with different models costing different amounts. Understanding the credit system prevents mid-session interruptions and optimizes your AI budget.
Prerequisites
- Windsurf account (Free, Pro, or Teams)
- Access to account dashboard at windsurf.com/account
Instructions
Step 1: Understand Credit Allocation by Plan
| Plan | Monthly Credits | Unlimited Features | Price |
|---|
| Free | 25 | Supercomplete (SWE-1 Lite), Tab completions | $0 |
| Pro | 500 | Supercomplete, Tab, Commands, Previews | $15/mo |
| Teams | 500/user | All Pro features + admin controls | $30/user/mo |
| Enterprise | Custom | All features + SSO, RBAC, audit | Custom |
Step 2: Credit Cost per Model
Different models consume different credit amounts per prompt:
| Model | Credits/Prompt (approx) | Best For |
|---|
| SWE-1 Lite | 0 (unlimited) | Quick questions, simple tasks |
| SWE-1 | 1 | Standard coding tasks |
| SWE-1.5 | 2 | Complex multi-file tasks |
| Claude Sonnet | 2 | Nuanced reasoning, architecture |
| GPT-4o | 2 | General purpose |
| Gemini Pro | 2 | Large context windows |
Step 3: Monitor Credit Usage
In-IDE: Click the Windsurf widget (status bar) > shows remaining credits
Dashboard: windsurf.com/account > Usage tab shows:
- Credits consumed today/this month
- Credits remaining
- Per-model breakdown
- Usage trend over time
Step 4: Credit Conservation Strategies
1. Use SWE-1 Lite for simple tasks (free, unlimited):
Quick questions about syntax
Simple completions
Code explanations
Use premium models for complex tasks:
Multi-file refactoring
Architecture decisions
Debugging complex issues
Write better prompts to reduce back-and-forth:
Include file paths, constraints, and expected output
Reference files with @ mentions instead of describing them
One well-structured prompt > five vague ones
Use Workflows for repetitive tasks:
Workflows consume credits but eliminate wasted retry prompts
A 5-step workflow costs less than 5 separate conversations
Leverage free features:
Supercomplete (Tab) is unlimited on all plans
Command mode (Cmd+I) is unlimited on Pro
Only Cascade Write/Chat consumes credits
