Docs / IDE extension

Developer docs

ForkMesh for VS Code / Codeium

Brings ForkMesh's issue tracker into the editor and lets you hand any issue to Claude Code or Codex with one click. Works in VS Code and the VS Code–based IDEs (Windsurf, Cursor, Codeium, VSCodium) via the standard extension API.

What it does

Requirements

Settings

SettingDefaultMeaning
forkmesh.claudeCommandclaude "$(cat {promptFile})"Command to start Claude Code. {promptFile} → generated prompt file, {issueNumber} → issue number.
forkmesh.codexCommandcodex "$(cat {promptFile})"Command to start Codex.
forkmesh.issuesPath(auto)Absolute path to an issues/ dir; empty = auto-detect <workspace>/issues.
forkmesh.showClosedIssuesfalseAlso list closed issues.

The default commands use $(cat …) (a POSIX shell). On Windows, set a PowerShell-friendly command, e.g. claude (Get-Content {promptFile} -Raw).

Desktop-app handshake

While running, the extension maintains a heartbeat file and watches for task requests under ~/.forkmesh/ide/ — see ide-extension-protocol.md. The ForkMesh desktop app uses these to detect the extension and to launch issues in the IDE. No network sockets are involved.

Develop / build

cd ide_extension
npm install
npm run compile          # or: npm run watch
# Press F5 in VS Code to launch an Extension Development Host.
npm run package          # produces forkmesh-<version>.vsix (needs @vscode/vsce)

Install the packaged build with:

code --install-extension forkmesh-0.1.1.vsix
# Windsurf / Cursor / VSCodium expose the same CLI under their own name.