IDB-31
VS Code extension
Run a team of agents from one editor.
Forq turns VS Code into a control panel for Claude Code, the native Claude CLI. Launch, isolate, and resume sessions as editor tabs, each in its own git worktree, all working at once.
Cache license validationwt/license-cachelive
Board drag and dropwt/board-dndlive
Linear sync retrywt/linear-retryin review
Worktree cleanup on donewt/wt-cleanupdone
Resume session from tabwt/resume-tabqueued
Watch a real run.
Create an issue, move it to To Do, and a Claude session spins up in its own worktree to take it. Here’s the whole loop in about a minute.
One agent at a time is the bottleneck.
You ship alone, with five half-built ideas open at once. Working one agent on one branch means everything waits on the thing in front of it. Forq runs them side by side, isolated, so progress happens in parallel.
- 01
Launch
Start a Claude Code session as an editor tab. Open as many as you need and watch them work like panes.
- 02
Isolate
Each session gets its own git worktree, so agents never step on each other’s files or branches.
- 03
Resume
Come back to any session and keep the conversation going from exactly where it left off.
Move a task to To Do. An agent picks it up.
Keep your work as a simple board. The moment an issue lands in To Do, Forq spawns a Claude Code session for it in a fresh worktree, then moves it to In Review when the agent is done and it’s your turn to look.
Backlog 2
IDB-30
Settings: default mode
To Do 1
IDB-28
Cache license validation
In Progress 2
IDB-27agent
Board drag and drop
IDB-25agent
Linear sync retry
In Review 1
IDB-22
Worktree cleanup on done
Done 1
IDB-19
Resume session from tab
Your ideas and issues live on your machine and work offline. Prefer a shared tracker? Connect Linear and sync both ways.
Your tools. Your accounts. Your machine.
Forq is the control panel, not the engine. It drives the native Claude CLI and other software you install and sign in to yourself, so each provider’s account, billing, and terms stay between you and that provider. Forq is not a middleman reselling anyone’s service or using your Claude subscription on your behalf.
- Claude Codecoding agent
Forq launches the native Claude CLI (Claude Code, by Anthropic) and drives it from VS Code. You install it and sign in with your own Anthropic account, so every session runs under your own agreement with Anthropic and any usage costs are yours. Forq runs the CLI locally on your machine and never proxies, stores, or reuses your Claude credentials or subscription. Forq is an independent extension, not affiliated with or endorsed by Anthropic.
- Linearissue syncOptional
Connect Linear to sync your issue board across machines and teammates. It is off by default; when you turn it on, issues move directly between your machine and Linear under your own Linear account and their terms. Leave it off and your board stays entirely on your machine.
- Dodo Paymentscheckout & licensing
Our merchant of record runs checkout and validates your license key. Your card details go to Dodo Payments and their processors, never to us. Activation binds a key to one machine and then keeps working offline.
- Google GeminiAI issue titlesOptional
If you add your own Google Gemini API key, Forq can suggest issue titles. Only the issue description you are titling is sent to Google's Gemini API, under your own key and Google's terms. Leave the key unset and titling stays fully offline.
Forq is an independent VS Code extension. Claude, Anthropic, Linear, Google Gemini, and Visual Studio Code are trademarks of their respective owners, named here only to describe what Forq works with.
Get your license key.
Forq is a paid VS Code extension. Pay once and it’s yours for life: one license activates one machine, validated through Dodo Payments.
Regular price $25$2020% off
- One machine per license
- Optional Linear sync
Do I need Claude Code?
Yes. Forq drives the native Claude CLI (Claude Code) inside VS Code, so you’ll need it installed and signed in with your own Anthropic account.
Is this allowed under Anthropic’s terms?
Forq runs the native Claude CLI locally and only sends it commands, the same way you would in a terminal. You sign in with your own Anthropic account, so your usage stays under your own agreement with Anthropic. Forq never proxies, stores, or reuses your Claude credentials or subscription, and is an independent product, not affiliated with or endorsed by Anthropic.
Does it work offline?
Yes. Ideas and issues are stored locally as plain JSON, so the board runs with no connection. Linear sync is optional.
How many machines can one license run?
One. A license binds to a single machine through Dodo Payments. Need more seats? Buy additional keys.
Is my code sent anywhere?
Not by Forq. Worktrees, issues, and sessions stay on your machine; the only things Forq sends are license checks and any sync you turn on. Claude Code, which you run, sends whatever you give it to Anthropic under your own account, the same as using it in a terminal.