Keep coding after your API budget runs out

API budget spent? Keep coding with an eligible browser-backed AI subscription. See how it works

One coding agent for browser subscriptions and APIs

Keep coding, even after
your API budget runs out.

Turn supported browser subscriptions you already pay for into a repository-aware coding agent in VS Code. Switch between available browser and API models without leaving your context, local tools, or workflow behind.

No model API key required for an eligible browser-backed connection · Local actions follow your approval settings

ChatGPTClaudeGeminiGrokDeepSeek

Current and planned browser connections · Availability rolls out by provider and account type · Provider limits and terms apply

One agent. More than one way to power it.

Move beyond API-only coding

Use an eligible browser subscription when API credits are gone, or choose an available API-backed model when it fits. wcagent keeps the coding workflow anchored in VS Code.

01 / CONNECT

Use the AI access you already have

Pair a supported browser subscription or select an available API-backed model. Both can power the same wcagent coding workflow.

See your connection options ↗

payments-api · Visual Studio Code

refund.ts refund.test.ts

export async function retryRefund(id) {
  return withBackoff(async () => {
    const result = await capture(id);
    if (!result.ok) throw result;
    return result;
  }, { attempts: 3 });
}

WebCodingAgent

Make refund retries safe, then prove they work.

✓ Read refund flow
✓ Edit retry boundary
✓ Run pnpm test
✓ Review concurrency risk

✓ Verified · 18 tests passed · diff recorded

Add direction while WebCodingAgent works

02 / SWITCH

Change the model, not your setup

When API spend reaches its limit, choose another eligible connection for your next task or follow-up. Your files, instructions, diagnostics, and local tools stay in the same editor workflow.

See how switching works ↗

Context map Ready · 1.4s

▾ src
▾ billing
refund.ts
retry.ts
checkout.ts
▾ tests
refund.test.ts
package.json

Ranked for “safe refund retries”

src/billing/refund.ts

tests/refund.test.ts

src/billing/retry.ts

package.json

2 diagnostics5 symbolsAGENTS.mdactive editor

03 / FINISH

Keep the full coding-agent workflow

Whichever connection you select, wcagent can inspect code, apply approved changes, run tests and builds locally, and record the diff. You change the source of AI reasoning, not how work gets done.

See the trust model ↗

Test suite18 / 18All required checks passed

Change set+48 −64 files · hashes verified

Specialist review

✓

Concurrency boundary cleared

Completion gateReadyEvery acceptance criterion has evidence

API OR WEB

Use the access that fits the moment.

Start with an API-backed model when you want it. If that budget is finished, move your next task or follow-up to an eligible browser-backed subscription.

2connection paths

1coding workflow

KEEP CONTEXT

Stay inside the same repository.

wcagent keeps task-relevant files, instructions, diagnostics, Git state, and durable conversation history in the VS Code workflow.

KEEP TOOLS

Keep editing, testing, and reviewing.

Commands, file changes, browser checks, approvals, and diffs still run through wcagent whichever eligible model connection you select.

0forced editor changes

1continuous coding workflow

100%local command control

What you keep

The model can change. The coding workflow doesn't.

wcagent separates the coding agent from the model connection. Your wcagent plan covers the VS Code workflow; you choose from the eligible model access available to your account.

Spend API budget deliberatelyUse API-backed models when they are worth the metered cost instead of making them your only route to AI coding.

Use browser subscription accessPair your account when a browser connector is available for that provider and account type.

Keep execution where the code livesCommands, edits, redaction, and workspace approvals remain authoritative inside desktop VS Code.

Finish with repository evidenceTests, builds, diffs, and diagnostics decide when the work is done. Model confidence does not.

The important distinction

Another connection, not a limit bypass.

When an API budget is exhausted, wcagent can let you select a separate eligible browser-backed connection. It never makes the exhausted API accept more requests, and the connection you switch to has its own provider limits.

Separate access

You bring the model account

wcagent supplies the agent workflow, not the underlying third-party model access.

Eligible connections

Use access you are allowed to use

Provider, account type, and connection method must permit use with wcagent.

Limits respected

Each connection keeps its limits

If a provider pauses or refuses a request, wcagent reports it. You can select another eligible connection; wcagent cannot override the first one.

Provider terms

No hidden workaround

wcagent does not defeat authentication, CAPTCHAs, safety systems, geographic restrictions, or technical access controls.

The API meter can stop. You don't have to.

Keep the coding session moving.

Install wcagent, pair eligible browser-backed AI access, and keep working in VS Code when an API-only workflow would send you home.

Explore wcagent

Product

See how browser subscriptions and API-backed models power one local coding workflow.

↗

Simple by design

Pricing

One wcagent plan for the agent workflow. Model access stays separate.

↗

Visual Studio Marketplace

Install wcagent

Add the agent to VS Code and connect eligible browser-backed or API model access.

↗

Keep coding, even afteryour API budget runs out.