VS Code · Live

Version control for VS Code AI chats and commits

The VibeHub extension auto-captures every commit you make in VS Code — message, full diff, and stats — and imports Copilot, Cursor, or Windsurf chat transcripts as VibeHub sessions. One extension works unchanged in VS Code, Cursor, Windsurf, and other VS Code forks.

Set it up

Install from the marketplace

code --install-extension vibehub.vibehub-vscode        # VS Code
cursor --install-extension vibehub.vibehub-vscode      # Cursor
windsurf --install-extension vibehub.vibehub-vscode    # Windsurf

Build from source

cd integrations/vscode
npx -y @vscode/vsce package          # produces vibehub-vscode-0.2.0.vsix
code --install-extension vibehub-vscode-0.2.0.vsix

What gets captured

  • Every commit you make, with its message, full diff, and stats
  • A VibeHub project created (idempotently) from the workspace folder name on first capture
  • Pasted or clipboard Copilot, Cursor, and Windsurf chats, imported as VibeHub sessions

How it works

Run VibeHub: Set API Token from the command palette and paste a token from Settings → API tokens; VibeHub: Test Connection confirms it works.

The token lives in the editor’s secret storage, not in synced settings.

With vibehub.autoCaptureCommits on (the default), commits are pushed as they happen; VibeHub: Capture Last Commit pushes HEAD immediately.

VibeHub: Capture Chat Transcript turns a pasted or copied chat into a VibeHub session.

VS Code 1.102+ can also reach VibeHub from Copilot agent mode via MCP: copy mcp.template.json to .vscode/mcp.json (or use MCP: Add Server) and replace the token.

VS Code + VibeHub FAQ

Does the VS Code extension work in Cursor and Windsurf?
Yes. The same extension works unchanged in VS Code, Cursor, Windsurf, and other VS Code forks. For automatic conversation capture in Cursor or Windsurf, pair it with the VibeHub MCP server — MCP captures the chats, the extension captures the commits, and VibeHub links them.
Which VibeHub project do my commits go to?
By default, a project named after the workspace folder. Override it with the vibehub.projectName setting.
Where is my API token stored?
In the editor’s secret storage, not in synced settings.

Other integrations

Version the whole vibe.

The vb CLI, public vibes, and GitHub mirroring are free forever.