Documentation

WebCodingAgent quick start

wcagent connects an eligible AI service to repository context, developer-controlled local tools, and verification inside desktop VS Code.

Overview

WebCodingAgent combines a desktop VS Code extension, a SaaS task-coordination service, and provider connections available through wcagent. The extension supplies ranked repository context, local tools, approvals, recovery, and evidence. The service coordinates the task. For eligible web-account integrations, the browser connector exchanges prompts and responses without exporting provider authentication material.

1. Install

Download the wcagent VSIX and browser connector from the downloads page. Install the VSIX in desktop VS Code, then open the wcagent view from the secondary sidebar.

code --install-extension wcagent-agent.vsix

2. Connect your account

Run wcagent: Connect Account and complete the browser device flow. VS Code stores the resulting token in the operating-system secret store.

Connect an AI service

Choose a provider, account type, and connection method you are authorized to use. For an eligible web-account integration, install the wcagent browser connector, run wcagent: Pair Browser Connector, then paste the copied pairing details into the connector. Provider cookies and authentication headers never leave the browser profile.

3. Start a task

Open a repository, select an available eligible AI connection, and tell WebCodingAgent what outcome you want. Choose whether local actions require approval. The system selects a bounded workflow and execution policy, then shows its tool activity as task evidence.

Make the checkout handler idempotent,
add regression tests,
and explain every validation command you run.

The initial context ranks relevant paths from the request, active editor, manifests, repository instructions, language symbols, open files, and diagnostics. While the task runs, you can add direction without discarding verified progress.

4. Resume safely

The extension stores only the active turn identifier in workspace state. After VS Code restarts, it fetches the canonical SaaS turn and reconstructs the presentation from the retained event log. Local mutations and provider submissions use stable identifiers and durable completion journals to avoid accidental replay.

5. Review every boundary

Untrusted workspaces are read-only. With Ask for approval, every command and file mutation opens an approval card in the conversation. Full access grants bounded task-wide approval only for actions still permitted by local policy.

Existing files require a prior SHA-256, paths cannot escape through symlinks, and likely credential files require additional confirmation. Common secret values are redacted before supported tool output leaves VS Code. Repository commands execute locally. Read-only and validation-only environments are enforced independently in both the cloud and extension.

Provider access and usage limits

wcagent does not increase, reset, conceal, or bypass provider usage limits. It does not defeat authentication, CAPTCHAs, safety systems, geographic restrictions, or other technical access controls.

If a provider refuses or limits a request, wcagent reports that result and pauses the connection. It cannot make the provider accept the request. Only use a connection method permitted for your provider and account type.

Privacy

Ranked path metadata, explicitly selected editor text, requested file contents, diagnostics, diffs, command output, approvals, and completion evidence may be sent to the wcagent service and the AI provider you select as needed for the task. Absolute workspace paths are excluded.

For eligible web-account integrations, the browser connector returns model text and bounded runtime metadata but never provider cookies, passwords, or authentication headers. Conversations may remain in the selected provider’s history. Your use remains governed by that provider’s account settings, availability, usage limits, and terms.