Skip to content
SpecKit Companion

Install where you work

Pick the place you work. Each one has its own Install page, which takes you from nothing to a first spec.

You can use more than one. They all read the same spec files in your project, so a spec started in one shows up in the others.

Every path has the same shape: Spec Kit itself, then the Companion extension for Spec Kit, which is optional but recommended, then the one thing your tool needs.

What each piece is

Section titled “What each piece is”
Piece What it does Where it installs Do you need it?
Spec Kit CLI (specify) Sets a project up with the /speckit commands, and installs extensions Your machine, as a uv tool. specify init writes a .specify folder and the commands into the project Required on every path
Companion extension for Spec Kit Records each run, adds the Companion pipeline and Auto, and brings living specs The project, under .specify/extensions/companion, plus commands for your assistant Optional, recommended on every path
VS Code extension The sidebar, the spec viewer, review comments and the Overview Your editor Required for VS Code only
Copilot board A board of every spec beside the chat, with a button for the next step The project, under .github/extensions/speckit-companion, or your user folder, under ~/.copilot/extensions/speckit-companion Required for the Copilot app only
Claude Code mod A line above the prompt and a pane with the steps and tasks Claude Code, as a plugin for your user Required for Claude Code only

Update later

Section titled “Update later”
Piece How to update it
Spec Kit CLI Run the uv tool install command again. --force replaces the build you have.
Companion extension for Spec Kit Run its specify extension add command again. The URL always serves the newest build, and --force refreshes in place.
VS Code extension Your editor updates it like any other extension.
Copilot board Copy the folder again and commit it. A project copy then shows Update available under Repository trust, and new sessions lose the board until you accept again.
Claude Code mod Run claude plugin update speckit-companion@speckit-companion, then /reload-plugins in an open session.

To silence the VS Code extension’s install prompts, set speckit.companion.installPrompt to false.

If something did not work

Section titled “If something did not work”
What you see What to do
No such command 'extension' You have the stock PyPI build. Install the GitHub build of the CLI, then add the extension again.
Stuck on an old build of the Companion extension Run specify extension remove companion, then add it again.
No /speckit.companion.* commands Run specify extension list from the repo root, not your home directory. Then reload the window, or start a new session, so your assistant re-reads its commands.
VS Code: no Living Specs view The install went somewhere other than this workspace. Run it again from this project’s root.
Copilot app: the board does not open Accept the repository content, then start a new session. If the agent opens an empty speckit-companion.md in the editor, you are in a session from before you accepted.
Copilot app: the board is missing from a project copy Commit the copy and get it onto your default branch. Each session starts from that branch.
Copilot app: the buttons send stock commands though Companion is installed Commit the files the Companion install added. A session cannot see uncommitted commands.
Claude Code: nothing shows Run /reload-plugins. Then widen the terminal, or run /speckit-tracker to open the pane in a narrow one.
Section titled “Related”