Bilg for VS CodeBilg is a shared context layer for teams that build with AI agents: documents, epics and decisions in one place, readable and writable by both people and their agents. This extension brings that context into VS Code — the project your workspace belongs to, its epics and tasks, the decisions behind them, and the open questions nobody has answered yet.
What you getYour project, in the sidebar. Bind a workspace folder to a Bilg project once, and its epics,
tasks, decisions, open questions and documents show up in the activity bar. Every record carries
its stable key ( Board. Open the project board in an editor tab, move work across stages, and drill into an epic without leaving the editor. Each epic's detail view includes an activity timeline, so you can see who changed what and when. Projects that opt into the optional Acceptance stage show it here too, matching the web board — the Build column for "ready" reads "Ready for deployment". Once an epic is marked deployed it's locked: editing stays with a new epic, though closing a leftover open task or resolving an open question is still allowed. Tasks you can actually work. Six statuses — open, in progress, in review, blocked, done, cancelled — plus type, priority, labels and a blocked reason, all editable straight from a task's buffer. Cycle a task's status, assign it to a teammate, and leave comments — all from the tree or the command palette. Task board. A drag-and-drop board across your tasks' statuses, grouped by epic or assignee when you want that view, right next to the epic board. Filter by epic, assignee, priority, type, label or a blocked-only toggle, with a live count of what's active; lanes with no card in progress start collapsed and remember how you left them. Search and ask. Semantic search across your Markdown, PDF and DOCX documents. "Find related documents" pulls up what's relevant to the file you're looking at. Handoffs. Addressed markdown deliveries between teammates and their agents, with a context link, replies and a resolve state. Unread handoffs show up as a badge on the Bilg view. Notifications. Assignments, comments, epic status changes and project invites, with an unread badge in the status bar. Project agent rules. See the markdown policy blocks your project loads into every agent's context, so you know what your agent has been told. Setup
Your API key is stored in VS Code's secret storage, not in settings or in your repo. Commands
Agents can do this tooThe same project is available to any MCP client — Claude Code, Claude Desktop, Cursor. The extension and your agent read and write the same records over the same API, so a decision your agent logs in the terminal is the decision you see in the sidebar. Some things stay human-only by design: only a person signed in on the web can mark an epic
Requirements
SupportQuestions or problems: app.bilgai.com |