Vibecode Windsurf
track this build5 steps, step by step0%NOT REALLY · don't bother
price $20/moyou'd save $240/yrbuild time closest consolation build: one sittingcategory 🛠️ dev toolsreplaced by 0 people
⌨️ featured in the best vibe coding tools
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Windsurf, build a VS Code extension that proposes and applies reviewed multi-file patches. The hard boundary is proprietary coding models, agent context, ide integration, and hosted inference, plus frontier models, context infrastructure, and execution safety.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of Windsurf. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Windsurf indie build ## Goal Build the smallest trustworthy replacement for the core Windsurf workflow for one developer or a tiny team. ## Scope Build a bounded VS Code coding assistant that indexes the current repository, proposes and applies reviewed multi-file patches, runs approved commands, and preserves an auditable session log. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - proprietary coding models, agent context, IDE integration, and hosted inference - frontier proprietary model - large-scale code retrieval - cloud sandbox fleet - enterprise policy and support If those capabilities are essential, use Continue instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build a closest honest personal substitute for Windsurf in an empty repository. Use TypeScript, Node.js 22, a VS Code extension, SQLite, and one user-supplied model API; do not offer alternative stacks. The core loop is: build a bounded VS Code coding assistant that indexes the current repository, proposes and applies reviewed multi-file patches, runs approved commands, and preserves an auditable session log. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Create a VS Code sidebar with chat, selected-code actions, repository search, and a patch preview. Index only the open repository and respect .gitignore plus a separate assistant ignore file. Require explicit approval before reading outside the workspace or running any command. Represent edits as unified diffs with accept, reject, partial apply, undo, and Git status checks. Capture tool calls, model requests, command output, and patch decisions in a local session log. Add token and cost estimates, provider errors, cancellation, tests, and an offline data-flow diagram. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure. Deliberately leave out training or reproducing a frontier coding model. Deliberately leave out unattended command execution outside a sandbox. Deliberately leave out cloud workspaces, team policy, and enterprise support. Finish by running the tests and listing the exact commands used. ## Required capabilities - VS Code - OpenAI or Anthropic API key - Git repository - local command sandbox ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a lean indie version of Windsurf. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Windsurf indie build ## Goal Build the smallest trustworthy replacement for the core Windsurf workflow for one developer or a tiny team. ## Scope Build a bounded VS Code coding assistant that indexes the current repository, proposes and applies reviewed multi-file patches, runs approved commands, and preserves an auditable session log. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - proprietary coding models, agent context, IDE integration, and hosted inference - frontier proprietary model - large-scale code retrieval - cloud sandbox fleet - enterprise policy and support If those capabilities are essential, use Continue instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief Build a closest honest personal substitute for Windsurf in an empty repository. Use TypeScript, Node.js 22, a VS Code extension, SQLite, and one user-supplied model API; do not offer alternative stacks. The core loop is: build a bounded VS Code coding assistant that indexes the current repository, proposes and applies reviewed multi-file patches, runs approved commands, and preserves an auditable session log. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Create a VS Code sidebar with chat, selected-code actions, repository search, and a patch preview. Index only the open repository and respect .gitignore plus a separate assistant ignore file. Require explicit approval before reading outside the workspace or running any command. Represent edits as unified diffs with accept, reject, partial apply, undo, and Git status checks. Capture tool calls, model requests, command output, and patch decisions in a local session log. Add token and cost estimates, provider errors, cancellation, tests, and an offline data-flow diagram. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure. Deliberately leave out training or reproducing a frontier coding model. Deliberately leave out unattended command execution outside a sandbox. Deliberately leave out cloud workspaces, team policy, and enterprise support. Finish by running the tests and listing the exact commands used. ## Required capabilities - VS Code - OpenAI or Anthropic API key - Git repository - local command sandbox ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a production product version of Windsurf. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== PRODUCT.md ===== # Windsurf product brief ## Problem A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Windsurf, build a VS Code extension that proposes and applies reviewed multi-file patches. The hard boundary is proprietary coding models, agent context, ide integration, and hosted inference, plus frontier models, context infrastructure, and execution safety. ## Product outcome Build a bounded VS Code coding assistant that indexes the current repository, proposes and applies reviewed multi-file patches, runs approved commands, and preserves an auditable session log. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - VS Code - OpenAI or Anthropic API key - Git repository - local command sandbox ## Explicit non-goals for v1 - proprietary coding models, agent context, IDE integration, and hosted inference - frontier proprietary model - large-scale code retrieval - cloud sandbox fleet - enterprise policy and support ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees. ===== ARCHITECTURE.md ===== # Architecture ## Starting brief Build a closest honest personal substitute for Windsurf in an empty repository. Use TypeScript, Node.js 22, a VS Code extension, SQLite, and one user-supplied model API; do not offer alternative stacks. The core loop is: build a bounded VS Code coding assistant that indexes the current repository, proposes and applies reviewed multi-file patches, runs approved commands, and preserves an auditable session log. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Create a VS Code sidebar with chat, selected-code actions, repository search, and a patch preview. Index only the open repository and respect .gitignore plus a separate assistant ignore file. Require explicit approval before reading outside the workspace or running any command. Represent edits as unified diffs with accept, reject, partial apply, undo, and Git status checks. Capture tool calls, model requests, command output, and patch decisions in a local session log. Add token and cost estimates, provider errors, cancellation, tests, and an offline data-flow diagram. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure. Deliberately leave out training or reproducing a frontier coding model. Deliberately leave out unattended command execution outside a sandbox. Deliberately leave out cloud workspaces, team policy, and enterprise support. Finish by running the tests and listing the exact commands used. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it. ===== AGENTS.md ===== # Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone. ===== MILESTONES.md ===== # Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations. ===== OPERATIONS.md ===== # Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Windsurf capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# Windsurf indie build ## Goal Build the smallest trustworthy replacement for the core Windsurf workflow for one developer or a tiny team. ## Scope Build a bounded VS Code coding assistant that indexes the current repository, proposes and applies reviewed multi-file patches, runs approved commands, and preserves an auditable session log. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - proprietary coding models, agent context, IDE integration, and hosted inference - frontier proprietary model - large-scale code retrieval - cloud sandbox fleet - enterprise policy and support If those capabilities are essential, use Continue instead of pretending the gap is solved.
AGENTS.md
# Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs".
BUILD_PLAN.md
# Build plan ## Original build brief Build a closest honest personal substitute for Windsurf in an empty repository. Use TypeScript, Node.js 22, a VS Code extension, SQLite, and one user-supplied model API; do not offer alternative stacks. The core loop is: build a bounded VS Code coding assistant that indexes the current repository, proposes and applies reviewed multi-file patches, runs approved commands, and preserves an auditable session log. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Create a VS Code sidebar with chat, selected-code actions, repository search, and a patch preview. Index only the open repository and respect .gitignore plus a separate assistant ignore file. Require explicit approval before reading outside the workspace or running any command. Represent edits as unified diffs with accept, reject, partial apply, undo, and Git status checks. Capture tool calls, model requests, command output, and patch decisions in a local session log. Add token and cost estimates, provider errors, cancellation, tests, and an offline data-flow diagram. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure. Deliberately leave out training or reproducing a frontier coding model. Deliberately leave out unattended command execution outside a sandbox. Deliberately leave out cloud workspaces, team policy, and enterprise support. Finish by running the tests and listing the exact commands used. ## Required capabilities - VS Code - OpenAI or Anthropic API key - Git repository - local command sandbox ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden.
.env.example
# Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
PRODUCT.md
# Windsurf product brief ## Problem A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Windsurf, build a VS Code extension that proposes and applies reviewed multi-file patches. The hard boundary is proprietary coding models, agent context, ide integration, and hosted inference, plus frontier models, context infrastructure, and execution safety. ## Product outcome Build a bounded VS Code coding assistant that indexes the current repository, proposes and applies reviewed multi-file patches, runs approved commands, and preserves an auditable session log. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - VS Code - OpenAI or Anthropic API key - Git repository - local command sandbox ## Explicit non-goals for v1 - proprietary coding models, agent context, IDE integration, and hosted inference - frontier proprietary model - large-scale code retrieval - cloud sandbox fleet - enterprise policy and support ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees.
ARCHITECTURE.md
# Architecture ## Starting brief Build a closest honest personal substitute for Windsurf in an empty repository. Use TypeScript, Node.js 22, a VS Code extension, SQLite, and one user-supplied model API; do not offer alternative stacks. The core loop is: build a bounded VS Code coding assistant that indexes the current repository, proposes and applies reviewed multi-file patches, runs approved commands, and preserves an auditable session log. Make the first run work locally with one documented command. Store all user data locally by default and make export straightforward. Put secrets in .env, ship .env.example, and never commit credentials. Create a VS Code sidebar with chat, selected-code actions, repository search, and a patch preview. Index only the open repository and respect .gitignore plus a separate assistant ignore file. Require explicit approval before reading outside the workspace or running any command. Represent edits as unified diffs with accept, reject, partial apply, undo, and Git status checks. Capture tool calls, model requests, command output, and patch decisions in a local session log. Add token and cost estimates, provider errors, cancellation, tests, and an offline data-flow diagram. Include clear empty, loading, success, and recoverable error states. Add input validation, safe filenames, and graceful handling of unavailable APIs. Write focused tests for the core transformation and one end-to-end happy path. Create a README with setup, architecture, permissions, data location, and backup steps. Do not add accounts, billing, telemetry, analytics, or a hosted control plane. Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure. Deliberately leave out training or reproducing a frontier coding model. Deliberately leave out unattended command execution outside a sandbox. Deliberately leave out cloud workspaces, team policy, and enterprise support. Finish by running the tests and listing the exact commands used. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.
AGENTS.md
# Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone.
MILESTONES.md
# Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.
OPERATIONS.md
# Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Windsurf capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
$ choose a build depth, inspect the files, then open the complete pack in your agent · this prompt is generated from the build plan · improve it via PR
People still pay for Windsurf because the UI can be copied, but high-quality code models, context ranking, safe execution, and constant evaluation are the product. The recurring cost buys model changes, indexing, prompt injection, tool permissions, sandboxing, evaluation, telemetry choices, and IDE compatibility, not just the visible interface.
xproprietary coding models, agent context, IDE integration, and hosted inference
xfrontier proprietary model
xlarge-scale code retrieval
xcloud sandbox fleet
xenterprise policy and support
share on X ↗"I just replaced Windsurf ($20/mo) with one prompt"
Don't feel like building it? These folks already made it free.
OpenCodeA fast local coding agent with no loyalty to any model vendor.open source↗
ZedA fast open editor with agents built in, not a VS Code costume.open source↗
ClineA code agent in your editor; the model bill is still yours.open source↗all 6 free alternatives to Windsurf →· no votes, no pay-to-list · just what's real
Windsurf pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| free | $0/user | $0/user | Light daily and weekly agent quotas; exact numeric allowance is not published; unlimited inline edits and Tab. |
| pro | $20/user | — | Daily and weekly quotas; estimated daily messages vary by model: 7-27 Premium Plus, 8-101 Premium, or 47-190 Lightweight. |
| teams | $40/user | — | Same published model-dependent estimated daily ranges as Pro, with team administration. |
| max | $200/user | — | Estimated daily messages: 42-170 Premium Plus, 47-631 Premium, or 291-1,190 Lightweight. |
| enterprise | custom | — | Custom ACU allocation, controls and support. |
free tierlight daily and weekly quotas with no published numeric amount; unlimited inline edits and Tab completion
billingcurrent public plans are monthly; legacy annual subscriptions may remain until renewal
hidden costsDaily and weekly quotas both apply and reset separately; extra usage is model-priced. Existing $15 Pro and $30 Teams customers were explicitly grandfathered, so two customers can pay different prices for the same named plan.
price historyPro per user per month: $15 → $20 (2026-03) · Teams per user per month: $30 → $40 (2026-03)
verified 2026-08-14 · source ↗
Vibecode Windsurf
Not really. Windsurf's value is not the code: Recheck price before merge. See the honest breakdown above.
How much does Windsurf cost?
Windsurf costs about $20/month (Pro, checked 2026-08-14), which is $240 per year.
What do I lose by replacing Windsurf?
Honestly: proprietary coding models, agent context, IDE integration, and hosted inference; frontier proprietary model; large-scale code retrieval; cloud sandbox fleet; enterprise policy and support. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Windsurf?
Yes: OpenCode (A fast local coding agent with no loyalty to any model vendor.) Zed (A fast open editor with agents built in, not a VS Code costume.) Cline (A code agent in your editor; the model bill is still yours.) All 6 curated free alternatives are at vibecodeit.com/windsurf/alternatives. The prompt is for when you want it exactly your way.