Docs Flowy for VS Code

Your Docs Flowy Board, drafts and artifacts in the editor, and your AI agent connected to the same specs.

Works in VS Code and VS Code Insiders.

▶ Watch the 2-minute tour

Docs Flowy keeps your team's specs, reviews and tickets in one place. This extension brings them into the editor, so you can see what's decided and what's being built — and move a card, assign it or answer a note — without leaving your code. Every change goes to Docs Flowy under your name, exactly as if you had made it on the web.

New in 0.3.0 — delete a ticket, and Undo. It waits in the Trash for 30 days.

New in 0.2.0 — change tickets from the editor. Move and assign cards, write and answer notes, or ask the assistant, see what changed and summarise it, approve an agent's Handbook changes, and export or delete drafts. Signed in with 0.1.0? Choose Sign in again on the Board once. The full list is on the Changelog tab.

Getting started

1. Install Docs Flowy. Get started with Docs Flowy opens to walk you through the rest.
2. Sign in. Open Docs Flowy in the activity bar and choose Sign in. Docs Flowy opens in your browser, where you're already signed in: check the editor's name and what it may do, then choose Connect.
3. Open the Board. Each project in the sidebar lists Board, Drafts and Artifacts. Each opens as a tab.
4. Connect your agent (optional). Run Docs Flowy: Connect your agent and paste a project key.

The Board, as on the web

Your project's Board opens as an editor tab, laid out like the Board you know: the lanes, the cards, the filters.

It has two axes, shown one at a time. Review is where a spec is decided: Untriaged, Draft, In review, Validated, Rejected.

The Board stays current on its own: when someone changes a status, a note or an assignee in Docs Flowy, the card moves in your editor too.

Once work starts, the ticket moves to Implementation: To do, In progress, Implemented, Testing, Done, Cancelled. A card shows its ticket key, where it came from, its state on the other axis, its notes, the agent working on it and who it's assigned to. Implemented says when an agent's work is waiting for someone to confirm it.

Every ticket, one click away

Click a card for its panel: both states and who set them, who created it, the assignee, what the agent built, the activity and the notes. Read the document opens it in the editor; Open in Docs Flowy takes you to the card on the web. Drag the panel's edge to make it wider; it remembers.

Move cards and assign them

Drag a card to another column to move it; a column it can't go to says why, and the card goes back. In its panel, change either state from its chip, assign someone (or Assign to me, or Unassign), watch it, Release a ticket an agent stopped working on, or Re-validate a spec that changed after it was validated. Rejecting asks why, and the reason is saved as a note.

Ctrl/⌘-click cards to select several and move them together. In List, every row has its own state control.

From anywhere, the status bar names the ticket that's open and its state; click it, or run Docs Flowy: Change the open ticket's state…, Assign the open ticket… or Add a note to the open ticket….

Delete a ticket, and Undo

The panel's ⋯ menu offers Delete ticket (Delete for a draft that isn't on the Board) where Docs Flowy says you may: it asks first, then the toast offers Undo for ten seconds. A deleted ticket goes to the project's Trash with its notes and history for 30 days, and its number is never given to another ticket. While an agent is working on it, or a Handbook change from it waits for a decision, the menu says so instead. A repository file's ticket can't be deleted — the next sync would bring it back — so its menu offers Take off the Board. Select several cards and the bar offers Delete when every one of them may be deleted.

Notes, and Ask the assistant

Write notes and replies, hand a note to someone, and resolve, mark won't fix, reopen or delete the ones you may (deleting asks first). Notes are grouped as Awaiting you, Open and Closed; Ctrl/⌘+Enter sends. The Activity tab filters to Everything, States, Notes or Versions.

Ask the assistant answers in a note's thread, marked AI, where your organization has it on. It uses one of your organization's credits, says so before you click, and never runs on its own.

Changes, and Summarise this change

A ticket's Changes tab pages through its versions and shows the lines that changed between two of them; Open in the editor opens the same diff in VS Code's diff view. Where your organization has it on, Summarise this change writes a paragraph about it — one credit, stated on the button.

Handbook changes

A ticket an agent claimed shows the Handbook changes it sent with the claim. Approve them there, or Review changes in Docs Flowy.

Filter it, or read it as a list

Filter by name or path, by state, by assignee, or by who wrote it: a person or an agent. Or switch to List for the same lanes, one row per ticket.

Drafts and Artifacts

Drafts are the specs people are writing; Artifacts are what agents wrote. Both are grouped by month, can be filtered, and load more as you scroll through. Show exported includes the ones already on the Board.

Export to Board puts a draft on the Board, and Delete in its panel's ⋯ menu moves a draft or an artifact to the Trash (it asks first, and offers Undo).

Read specs where you code

Any document, draft or artifact opens in the editor with its images. A link to another spec opens that one too.

Under each project, Documents lists every document in its repository, by folder, and Search documents finds one as you type.

When the repository is open in your editor, a document has an Open file button, and the files a spec names in code, like src/billing/invoice.ts:42, open at that line with one click.

What's waiting on you

The status bar and the Docs Flowy icon show how many notes are waiting on you. Click the count for the list; each one opens in the editor.

Reliable by design

• Nothing is shown as done until Docs Flowy keeps it. A change that's refused snaps back and says why, in Docs Flowy's own words.
• A note is written once. A note or reply sent again after a timeout doesn't post twice.
• One live connection per window. The Board follows the web as it changes; a connection that goes quiet is replaced, and the tabs catch up after a reconnect.
• What you're typing survives the Board refreshing under you.
• It fits narrow panels. The columns scroll on their own, a narrow tab opens on List, and the panel fills the window.

Keyboard

Connect your agent

Your editor's agent can read the same specs over MCP. Run Docs Flowy: Connect your agent and paste a project key, once:

• VS Code adds Docs Flowy's MCP server itself: no mcp.json to edit.
• Other editors get a configuration to copy.

The agent uses the key, never your session: it reads what the key's project allows, and never sees your unexported drafts. Owners and Admins create keys in Docs Flowy under Organization → API.

Commands

Settings

Privacy and security

Read the Privacy Policy and the Terms.

• Changes only with your say-so. Signing in asks Docs Flowy for leave to change tickets, and the browser says so before you choose Connect. The editor can then change what you could change on the Board — states, assignees, watching, notes, exporting and deleting drafts, approving an agent's Handbook changes, and recording what you read — under your name, with the same permissions and plan; nothing else. Asking the assistant or summarising a change uses your organization's credits, and only when you click. It can't reach your account, sessions, API keys, billing or settings, and it can't edit documents. Turn off docsflowy.editTickets, or approve a sign-in that only reads, and Docs Flowy refuses any change from it.
• Your sign-in stays yours. It is kept in the editor's secret storage, sent only to the Docs Flowy address that issued it, and never written to settings or logs. It is listed under Account → Sessions in Docs Flowy, where you can sign it out; signing out, from either side, closes what it had open.
• The agent's key is separate. The project key lives in secret storage too, and the agent never uses your sign-in.

Requirements

• A Docs Flowy account, and VS Code 1.90 or later .
• To connect an agent: a project key, and an editor whose agent speaks MCP.
• Remote windows (SSH, Dev Containers, WSL, and GitHub Codespaces opened in desktop VS Code) work: the extension runs on your machine, where you sign in.
• Not yet supported: vscode.dev, github.dev, and Codespaces in the browser.

FAQ

VS Code asks "Do you want Code to open the external website?" That's VS Code checking before it opens Docs Flowy in your browser to sign you in; it asks about any website it doesn't trust yet. Check that the address is your Docs Flowy server, then choose Open. If you chose Cancel, the sign-in waits: cancel it and sign in again.

VS Code asks "Allow 'Docs Flowy' extension to open this URI?" That's VS Code checking the link your browser handed back after you chose Connect. Check that the link comes from Docs Flowy, then choose Open.

The sign-in didn't finish. Confirm in the browser within ten minutes, then choose Open when VS Code asks. If the browser didn't open, check docsflowy.url.

My agent doesn't list Docs Flowy. Run MCP: List Servers and start Docs Flowy. If the key was revoked, run Docs Flowy: Connect your agent with a new one.

The sidebar asked me to sign in again. Your sign-in was signed out in Docs Flowy, or it expired. Sign in again.

The Board says "Sign in again to move cards". The editor signed in to read only: with 0.1.0, or from a sign-in approved to read. Choose Sign in again (or run Docs Flowy: Sign in again to change tickets); the old sign-in is signed out for you.

Can I keep the editor read-only? Yes. Turn off docsflowy.editTickets: every control that changes something is hidden, and the next sign-in asks only to read.

I don't see Summarise this change, or Ask the assistant is refused. Both are on only where your organization has turned them on and has credits left: Summarise shows only then, and Ask says so, in Docs Flowy's words, when it's refused. Each uses one credit, only when you click.

I deleted a ticket by mistake and the Undo is gone. It is in the project's Trash on the web for 30 days: open the project in Docs Flowy and restore it from there. The person who deleted it, or an Owner or Admin, can.

Something else? Output → Docs Flowy lists what the extension did. It never contains a sign-in, a key or a code, so it's safe to share with us.

Support

Questions and help at docsflowy.com. What changed in each version is on the Changelog tab.