Flywheel for VS Code

A greatest-hits coding agent, inside VS Code.

Flywheel is a coding agent built for doing real work in your repository. Ask for a change, watch it use tools and edit files, then review the result without leaving VS Code.

• A chat worth using. Markdown streams as it arrives. Tool calls show what ran, live output, errors, diffs, and omitted content you can load on demand. Questions are answered inline.
• Your subscription, not another bill. Sign in with ChatGPT, GitHub Copilot, SuperGrok, or OpenCode Go, or use an API key for Anthropic, OpenAI, Google, OpenRouter, or an OpenAI-compatible endpoint. Connect several accounts and Flywheel can rotate past provider limits.
• Durable workflows. Launch planning, implementation, review, QA, and debugging workflows from the composer. Follow step progress, pause or resume the queue, and reconnect after a window reload without losing the active run.
• Your editor is the context. Attach selections, files, symbols, or Problems. Error and warning lightbulbs can send a focused fix request directly to Flywheel.
• Review before you trust. Open the current session's retained changes in VS Code's native multi-file diff editor. Revert one file or undo the last turn, with drift checks that refuse to overwrite newer work.
• Sessions that stay useful. Create, switch, rename, close, or delete sessions. Older transcript content loads when you need it, and active subagents and workflows remain connected to their own sessions.
• Your stack still fits. Choose models and reasoning effort, manage provider accounts and profiles, inspect subscription usage, and check MCP connection health from VS Code.

Getting started

1. Install the extension and open a folder.
2. Open the Flywheel panel.
3. Select a provider in the setup screen, or run Flywheel: Connect a Provider from the command palette.
4. Ask for a change. Flywheel opens a session on the first message and starts working in the current project.

The platform-specific Marketplace package includes the Flywheel runtime. You do not need to install the CLI separately. Advanced users can select another executable with flywheel.executablePath.

The panel

The toolbar shows only the controls that apply to the current state:

Type / on an otherwise empty composer line to open Flywheel's action panel. It contains session actions, model and usage controls, provider and profile management, available workflows and skills, runtime settings, status, logs, and recovery actions. The available entries come from the installed runtime and current configuration.

Press Enter to send and Shift+Enter for a new line. When the composer is empty, Arrow Up and Arrow Down recall earlier messages from the current session.

Bring in editor context

Use VS Code's native pickers instead of copying paths and diagnostics by hand:

• Flywheel: Add Files to Message inserts selected workspace file references.
• Flywheel: Add Symbol to Message searches workspace symbols and inserts the selected location.
• Flywheel: Add Problems to Message attaches selected errors and warnings.
• Add Selection to Chat is available from the editor context menu.
• Error and warning lightbulbs offer a focused Fix action. A non-empty selection also offers Explain.

Workflows

Run Flywheel: Launch Workflow or select a workflow after typing /. User-invocable workflows ask for a task description and open their own session.

A running workflow shows its current steps, progress, model, effort, duration, and state above the transcript. Pause and resume are available when the workflow supports them. Flywheel: Stop Workflow interrupts the active workflow, and some workflow states accept steering text directly from the composer.

Review and undo changes

When the current session has retained file changes, a Changes button appears beside the composer. It opens VS Code's native multi-file diff editor. Mutation tool rows can also open a diff for one file.

A file revert or last-turn undo first checks that the file still matches the recorded change. If you edited the file afterward, Flywheel refuses the revert instead of discarding your work. If a change has no retained diff, Flywheel reports the omission rather than presenting incomplete review as complete.

Providers, models, and usage

Provider setup follows the method supported by that provider: API key, device code, or browser sign-in. You can connect more than one account, organize accounts into profiles, choose the chat model and effort for a session, assign models to other agent roles, and inspect provider-reported usage and history.

Provider names, models, login methods, and availability come from the bundled runtime and connected accounts. The UI explains when a model is unavailable instead of silently hiding it.

Quick actions

Requirements and remote workspaces

Flywheel requires VS Code 1.96 or later and an open folder. It runs as a workspace extension, so in SSH, WSL, and dev-container sessions the extension and runtime run beside the project on the remote host. The Marketplace selects the package for that host's operating system and CPU architecture.

The extension supports macOS, Linux, Alpine Linux, and Windows on x64 and ARM64. You can override the project root with flywheel.projectRoot when the first workspace folder is not the project Flywheel should own.

Privacy and data

Flywheel does not send product analytics or telemetry to the Flywheel Core Team. Conversations, tool results, file changes, diagnostics, and session state stay on the machine where the extension host runs. In a remote workspace, that is the remote machine.

When you use a model provider, Flywheel sends that provider the prompt and the context needed for the request. When the agent calls a configured MCP server, that server receives the inputs for the call. Those services process data under their own terms and privacy policies.

Provider credentials are stored in Flywheel's account profile and are sent only to the relevant authentication or provider endpoint. Flywheel excludes credentials from model context, logs, and snapshots. The Flywheel Core Team receives no session data unless you choose to include it in a support request.

Support

Report bugs and request features through GitHub Issues. The / action panel also includes Report a problem. Before attaching logs or session details, remove source code, personal information, and credentials that you do not want to share publicly.

License

Flywheel for VS Code is distributed under the MIT License.