Vibe Bug Tracker

Visual bug reports — screenshot, DOM context, console, network — in your editor sidebar, wired straight into your AI coding agent over MCP.

Website · Docs · Report an issue

When a tester files a bug through Vibe Bug Tracker, it arrives with a screenshot, the CSS selector of the element they clicked, the browser and viewport it happened in, and the console and network activity around the moment it broke. This extension puts those reports in your VS Code sidebar — Assigned, In Progress, Completed — so triage stops being a round trip through a web dashboard.

The part that saves real time is MCP. One click creates a scoped token, links the workspace to the right project, and writes the MCP config your IDE expects. After a reload, your coding agent can read issues, screenshots, and comments directly.

Features

Issues where you already are

Assigned, In Progress, and Completed views populate from your Vibe Bug Tracker board. Open any issue for a detail webview with the screenshot, the CSS selector, browser metadata, and the full comment thread — then move it through statuses, comment, or copy it as Markdown without switching windows.

Bundled MCP server, one-click setup

The MCP bridge ships inside the extension. No separate ZIP, no npm install, no global binary drifting out of sync with the extension version.

Connect MCP does the whole setup in one action:

Detects your IDE — VS Code, Cursor, Windsurf, or Antigravity
Creates an MCP token and stores it in the OS keychain via SecretStorage
Links the workspace to the matching project
Writes .vscode/mcp.json and/or .cursor/mcp.json in that IDE's format
Adds the secret-bearing config paths to .gitignore

Work Issue with Agent

Right-click any assigned issue → Work Issue with Agent. Your IDE's chat opens with /vibe-bug-work ISSUE-123 already typed. The agent pulls the full report over MCP — including the screenshot — and starts on the fix with context that a pasted stack trace never carries. If chat isn't available, the prompt lands on your clipboard instead.

Automatic workspace-to-project mapping

The extension reads your git remote and branch and matches them to the right project. Ten repos checked out on one machine means ten sidebars each showing the correct board — no manual switching, though Switch Project is there when you need it.

Vibly Studio

A project-memory layer that analyzes your codebase into modules and features, then drives agent work at that altitude instead of issue-by-issue: analyze the project, work a feature, work a module, build an approved plan, check status. Optional — the issue views work fine standalone.

Getting started

Install this extension.
Open the repository the bugs are filed against.
Sign in from the Login view in the Vibe Bug Tracker sidebar.
When prompted, click Connect MCP — or open MCP Setup → Connect MCP.
Reload the window when asked.

That's it. Assigned issues appear in the sidebar and your agent can read the board.

Commands

Every command is under the Vibe Bug Tracker category in the Command Palette.

Command	What it does
`Login` / `Logout`	Authenticate against your Vibe Bug Tracker account
`Refresh`	Re-fetch issues for the current project
`Switch Project`	Point the sidebar at a different project
`View`	Open the issue detail webview
`In Progress` / `Complete`	Move an issue's status
`Comment`	Add a comment without leaving the editor
`Copy`	Copy the issue as Markdown
`Work Issue with Agent`	Open IDE chat with `/vibe-bug-work <ID>`
`Connect MCP`	One-click MCP setup for the detected IDE
`Create MCP token`	Issue a token manually
`Generate MCP config` / `Copy stdio config`	Write or copy MCP config by hand
`Link workspace to project`	Override the git-based project mapping
`Initialize or Repair Project Memory`	Fix a broken `.vibebug` memory directory
`Vibly: Analyze Project`	Build the module/feature map for your codebase
`Vibly: Work Feature` / `Work Module`	Run agent work scoped to a feature or module
`Vibly: Build Approved Project`	Execute an approved build plan
`Vibly: Project Status`	Show current Vibly progress

Requirements

VS Code 1.90 or newer (or Cursor, Windsurf, Antigravity on an equivalent base)
A Vibe Bug Tracker account — sign up at vibebugtracker.com
Node.js on your PATH, for the bundled MCP bridge
Git, for automatic workspace-to-project mapping

The extension is free. The service behind it requires an account; see vibebugtracker.com for plans.

The rest of the toolkit

The IDE extension is the developer end. Bugs get filed from:

Chrome extension — click any element on a page to capture a screenshot, the DOM context, console errors, and network activity, plus read-only AI investigation and unattended Auto QA sweeps
Flutter SDK — the same capture flow inside Flutter apps, with region-scoped widget capture

Privacy

Your credentials are stored in the OS keychain through VS Code's SecretStorage — never in workspace files. Issue data moves between this extension and your own Vibe Bug Tracker project at https://vibebugtracker.com, and nowhere else. The MCP bridge runs locally on your machine. Generated MCP config files are added to .gitignore because they carry tokens.

Support

Bugs and feature requests: GitHub Issues
Docs: vibebugtracker.com/docs

_{Built by K-Dynex}

Vibe Bug Tracker

k-dynex.vibe-bug-tracker

Vibe Bug Tracker

Features

Issues where you already are

Bundled MCP server, one-click setup

Work Issue with Agent

Automatic workspace-to-project mapping

Vibly Studio

Getting started

Commands

Requirements

The rest of the toolkit

Privacy

Support