MySpec for VS Code

Work with your MySpec specs without leaving the editor.

• Browse the spec files of a MySpec project as a folder tree, open them read-only (Markdown preview works), and step through their revisions — open any of the last 10, or compare it with the current version or the one before.
• Discuss: see comment threads in the editor gutter, start a thread on the lines you select, reply, resolve or reopen, and edit or delete your own comments.
• Plan: see the project's tasks — yours by default — and change their status, assignee, priority, story points, cycle, dates and labels. Changes are staged locally, like a cart, and sent to MySpec together when you Submit.
• Download a spec file, a revision, an attachment or a whole folder.
• Open in MySpec from anything to continue in the webapp. Changing spec files and everything else happens there.

Install

Search for MySpec in the Extensions view, or run code --install-extension myspec.myspec-vscode. Cursor, Windsurf and VSCodium get it from Open VSX the same way.

Getting started

1. Open the MySpec view in the activity bar.
2. Sign in. If you already signed in with the MySpec MCP server (npx @myspec/mcp-server login) on this machine, you are signed in here too — it is the same sign-in. Otherwise choose Sign in with browser, or Use an API token (avatar menu → API tokens in MySpec).
3. Link a project to the folder you have open. VS Code remembers the link per folder: reopen the folder and its project is there; another folder can link another project.

Things to know

• One sign-in for the MCP server and VS Code. Signing in, switching organization or signing out in VS Code does the same for the MySpec MCP server on this machine, and the other way round. An API token entered in VS Code is kept in VS Code's secret storage and used only by VS Code.
• Read-only API tokens can browse and download; commenting and task edits are turned off.
• Unsubmitted task changes show as ● unsubmitted in the Tasks view, with a count on the view. To change many at once, select several tasks (Shift/Ctrl-click) or a tasks file (all of its tasks), then Set status. Use Submit Task Changes to send them in one go, Review Task Changes to see them, or Discard to drop them. They stay on this machine until you submit (for up to 14 days), per project and per account. A task someone else changed meanwhile is marked needs review and held back: keep your change or undo it.
• Copy prompt for AI agent (right-click tasks or a tasks file) saves the latest spec files those tasks come from under .specs/ in the workspace folder, and copies a prompt with the tasks in full that names those files. Paste it into Copilot, Claude Code, Cursor or any coding agent: it needs no MySpec access. Files in .specs/ are overwritten each time; add the folder to .gitignore if you do not want to commit it.
• Comments are anchored to the text you select, not to a line number, so they follow the passage when the file changes. Select a little more text if MySpec says your selection appears more than once. Old revisions are read-only.
• Freshness. Views refresh when you come back to the window or open them; use Refresh for an immediate reload. The Discussions view also reloads right after you add, reply to, resolve, reopen, edit or delete a comment.
• Remote development (SSH, containers, WSL): the extension runs on your local machine by default, so it uses your local sign-in.

Settings

The MySpec log is in Output → MySpec; tokens are never written to it.