SpecStory works across multiple tools. Follow the steps to setup SpecStory for your editor or workflow and get started quickly.

Cursor

Install

  1. Open Cursor.
  2. Extensions (Ctrl/Cmd+Shift+X) → search SpecStoryInstall.
  3. Verify via Command Palette (Ctrl/Cmd+Shift+P) → type SpecStory.
Installing from the Visual Studio Marketplace website can leave VS Code installed but not Cursor. Install inside Cursor.

Verify autosave

  1. Chat with Cursor’s AI in a workspace folder.
  2. Check <your-project>/.specstory/history/ for a Markdown file representing your session.
👉 Learn more in Integrations → VS Code + Copilot.

VS Code (Copilot)

Install

  1. Open VS Code with GitHub Copilot enabled.
  2. Extensions (Ctrl/Cmd+Shift+X) → search SpecStoryInstall.
  3. Verify via Command Palette (Ctrl/Cmd+Shift+P): type SpecStory.

Verify autosave

  1. Start a Copilot chat in your workspace.
  2. Check <your-project>/.specstory/history/ for a new Markdown file.
👉 More details in Integrations → VS Code + Copilot.

Claude Code

Install (macOS via Homebrew)

brew tap specstoryai/tap
brew update
brew install specstory
specstory version

Run & verify

# Launch Claude Code via SpecStory (captures the session)
specstory run

# Convert existing Claude Code sessions to Markdown
specstory sync

# Sync a specific session
specstory sync -u <session-uuid>

# Optional: view logs in console
specstory sync --console
Generated files appear in <your-project>/.specstory/history/.
Linux/WSL: download binaries from the GitHub releases page. See Integrations → Claude Code / CLI for platform notes and paths.
👉 Learn more in Integrations → Claude Code.

BearClaude (macOS)

Install

Use & verify

  1. Open a project folder in BearClaude.
  2. Write a spec in the editor, then use the Claude pane.
  3. Check <your-project>/.specstory/history/ for Markdown files of your conversations.
👉 Deep dive in BearClaude and Settings.

Troubleshooting quick checks

  • No files in .specstory/history/: Confirm you are inside a project folder with write permissions.
  • Cursor VS Code not saving: Ensure the extension is installed in the correct editor (Cursor vs VS Code) and restart the editor.
  • CLI not capturing: Run specstory check and confirm Claude Code runs from your shell (e.g., claude --version).
  • Still stuck? See Integrations for storage paths and known issues, or contact support@specstory.com.

Next steps