# FAQs Source: https://docs.specstory.com/faqs Frequently asked questions about SpecStory's features, getting in touch and future plans. SpecStory is tested to work with: * Cursor: every version after `v0.43.5` * Copilot: every version after `v1.300.0` Nope. Today SpecStory is [free as in beer 🍺](https://opensource.stackexchange.com/questions/620/what-is-the-difference-between-free-as-in-beer-and-free-as-in-speech). Enjoy! Sharing is caring! We'd absolutely love if you could: * Tell your friends about SpecStory. * Introduce us to a colleague at work. * [Leave a review](https://marketplace.visualstudio.com/items?itemName=SpecStory.specstory-vscode\&ssr=false#review-details) on the VS Code Marketplace * Talk about us on [Cursor Reddit](https://www.reddit.com/r/cursor/), [Cursor Forums](https://forum.cursor.com/), [GitHub Copilot Reddit](https://www.reddit.com/r/GithubCopilot/), X.com, BlueSky and LinkedIn. * Follow us on [LinkedIn](https://www.linkedin.com/company/specstory), [X.com](https://www.x.com/specstoryai) and [BlueSky](https://bsky.app/profile/specstory.com). Star us on [GitHub](https://github.com/specstoryai/getspecstory). We get this question a lot! Each [AI Code IDE](https://specstory.com/editor-tracker) stores chats in differing formats and locations. All are [subject to change](https://forum.cursor.com/t/questions-about-state-vscdb/47299/2) at anytime. We're currently focused on making the best possible extension for GitHub Copilot & Cursor. We would like to make SpecStory available for Windsurf. Tell them your interested in making your chats available on this [issue](https://github.com/Exafunction/codeium/issues/127)! Curious about the hype around the different AI code editors? Us too. That's why we created the [AI Editor Tracker](https://specstory.com/editor-tracker) to follow the sentiment. In a nutshell, SpecStory allows you to save and share your AI conversation history. For Cursor, it reads your local chat history directly from a `sqlite3` database. This is located in different paths depending on your operating system: * Windows: `%APPDATA%\Cursor\User\globalStorage\state.vscdb` * MacOS: `~/Library/Application Support/Cursor/User/globalStorage/state.vscdb` * Linux: `~/.config/Cursor/User/globalStorage/state.vscdb` For GitHub Copilot, it reads your local chat history directly from chat jsons: * Windows: `%APPDATA%\Code\User\workspaceStorage\{hash}\chatSessions` * MacOS: `~/Library/Application Support/Code/User/workspaceStorage/{hash}/chatSessions` * Linux: `~/.config/Code/User/workspaceStorage/{hash}/chatSessions` For more detail about each SpecStory feature check out [our feature page](/features). For insight into what data we collect and access to deliver SpecStory look at [our data privacy page](/privacy). Don't be shy: we'd absolutely love to hear from you and promise to be extra responsive! 1. Drop us a line at [support@specstory.com](mailto:support@specstory.com). 2. Join our [Slack community](https://join.slack.com/t/specstory/shared_invite/zt-2vq0274ck-MYS39rgOpDSmgfE1IeK9gg) and ping us directly 3. File an [issue on github](https://github.com/specstoryai/getspecstory/issues). The extension is still in active development with rapid iterations. We've talked about this internally but have not made a decision. We do strive to be as open as possible in terms of [how it works](/features), what [data is accessed and stored](/privacy) and [what our policy is](https://specstory.com/privacy). Not today. We do not conduct write operations on the `state.vscdb` or the [Shadow Workspace](https://www.cursor.com/blog/shadow-workspace) Cursor maintains. We do not modify the `workspaceStorage` directory Copilot maintains. You can `@` reference (in Cursor) or `#` reference (Copilot) these files to provide context to your AI though! # Features Source: https://docs.specstory.com/features Everything you can do with SpecStory ## Auto-Save Your AI Conversations SpecStory automatically saves AI chat history in your project's `.specstory` folder. Each conversation is saved as a separate markdown file, ensuring you never lose valuable AI interactions. * **Auto-save is enabled by default** but can be disabled via the setting `specstory.autoSave`. * Works seamlessly in the background. * Preserves your entire conversation history. * Compatible with standard workspaces (WSL support coming soon). ## Manual Save and Export Need more control over your saved conversations? Use the command palette (Cmd/Ctrl+Shift+P) and run `SpecStory: Save AI Chat History` to: * Select specific conversations to save. * Combine multiple conversations into a single markdown file. ## Share and Editorialize Your AI Conversations Share your AI chat history instantly using the command palette with `SpecStory: Share AI Chat History`. Key sharing features: * Get a unique, shareable URL instantly. * Share anonymously - no signup required. * Select specific conversations to include. * Add markdown and edit markdown blocks, images and embed videos into to your shares. * Add a GitHub URL to "link" your work together. * Edit or remove shared content later (cookie-based authentication). ## Automatically Derive Rules for AI In SpecStory [v0.7.0](https://marketplace.visualstudio.com/items/SpecStory.specstory-vscode/changelog) and later you can turn on an feature via the setting `specstory.derivedRules`. To use this feature you must: * Have Auto-save enabled. * Create an account and sign-in to the Specstory extension. This feature is currently free. Each generation makes a call to an LLM and we require authentication to its prevent abuse. Key Features * Automatically create a `derived-rules.mdc` to `.cursor/rules` or `copilot-instructions.md` to `.github/`. * Back-ups your previous versions to the `.specstory/ai_rules_backups` directory. * Automatically adds backups to your `.gitignore`. * Allows for custom file headers to be modified to customize rule generation through settings. The system prompt currently in use is: ``` You are an expert software engineer responsible for maintaining a "living" and "evolving" AI coding assistant rules file. This file defines all project rules, coding standards, workflow guidelines, references, documentation structures, and best practices. Each time you receive new user–AI interactions, you must merge any relevant new guidelines, clarifications, or decisions into the file which is stored in the root of the project and is obeyed by the AI coding assistant. Rules for Updating: 1. Retain the structure of the AI coding assistant rules file, which uses the following top-level sections: 2. Read the new user–AI interactions carefully. Identify any instructions, new rules, clarifications, or best practices that arise. Incorporate them into the correct sections. If a new rule conflicts with an existing one, note the conflict and either: - Resolve it by clarifying the final, decided rule, - OR highlight that further user confirmation is needed. 3. Do not remove or discard existing content unless there is a clear directive to do so, but if a new rule supersedes or modifies old content, replace or annotate the old content accordingly. Don't let the rule file grow too much. 4. Maintain consistent markdown format, with ## headings for the top-level structure. 5. If version updates or references to version changes arise record them under the relevant section(s). For example, if it impacts the "TECH STACK" or "PROJECT DOCUMENTATION & CONTEXT SYSTEM", note it there. 6. If any mention of new coding tools or libraries arises, add them under the correct section (e.g., "TECH STACK") but do not remove previous entries. 7. If new debugging or workflow rules appear in the saved chat as a result of a user request to the AI, insert them into the correct sections (e.g., "DEBUGGING" or "WORKFLOW & RELEASE RULES"). 8. Look for signals that the user's intent is to make something a permanent rule. This includes words like "don't","must", "should", "always", "never", "all the time", "every time", "every time you see this", etc. 9. Don't make ANY adjustments to the AI coding assistant rules file unless you are absolutely sure that the user's intent is rule like in nature. Err on the side of making too few adjustments, not too many. It's perfectly fine to leave the file as it is. 10. After merging all relevant updates, output the entire updated AI coding assistant rules file as a single cohesive markdown document. Do not include extraneous commentary or placeholders, just the final updated file content. --- TASK: Please merge the new interactions into the AI coding assistant rules file as specified, and return the complete updated file content in markdown format. Ensure all headings remain in order, conflicts are addressed, and the file remains consistent and comprehensive. OUTPUT FORMAT: You must return the updated AI coding assistant rules file as a single cohesive markdown document. Do not include extraneous commentary. You must return the response inside a tag. Example: Content of the updated AI coding assistant rules file The MOST IMPORTANT THING is that you must return the response inside a tag. ``` # Install the extension Source: https://docs.specstory.com/introduction Save, search and share your AI chat history with SpecStory. ## Multiplatform support is now here The SpecStory Extension as of `v0.11.0` [(changelog)](https://marketplace.visualstudio.com/items/SpecStory.specstory-vscode/changelog) supports both [Cursor](https://www.cursor.com/) and [GitHub Copilot](https://github.com/features/copilot). SpecStory saves, organizes, and makes all your AI chats searchable in structured Markdown. Never lose a great solution, easily share interactions, and use conversation history to refine Copilot and Cursor with custom instructions and project rules. ## 🍦 Installation Options We recommend you install directly from the Extension Marketplace in your preferred editor. 1. Open VSCode with GitHub Copilot installed and activated. 2. Search for **SpecStory** in the Extensions Marketplace (Ctrl/CMD-Shift-X). 3. Click **Install**. Consult our [Changelog](https://marketplace.visualstudio.com/items/SpecStory.specstory-vscode/changelog) to make sure you're on the latest version. 4. Once installed, SpecStory automatically saves your Copilot chats to the `.specstory` folder in your project.. 1. Open Cursor. 2. Search for **SpecStory** in the Extensions Marketplace (Ctrl/CMD-Shift-X). 3. Click **Install**. Consult our [Changelog](https://marketplace.visualstudio.com/items/SpecStory.specstory-vscode/changelog) to make sure you're on the latest version. 4. Once installed, SpecStory automatically saves your Cursor chats to the `.specstory` folder in your project. As a Cursor user, if you try to install from the [Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=SpecStory.specstory-vscode) website banner you might find yourself in a state where VSCode has SpecStory installed but Cursor doesn't. [It makes for a bad time](https://github.com/specstoryai/getspecstory/issues/8). No one wants that. The SpecStory extension's VSIX works seamlessly with both GitHub Copilot and Cursor. You'll need to install it separately in each environment. 1. Make sure you're on the latest version of [GitHub Copilot](https://github.blog/changelog/label/copilot/) or [Cursor](https://www.cursor.com/changelog) . 2. Download our extension: [specstory-vscode-latest.vsix](https://static.specstory.com/vscode-extension/releases/specstory-vscode-latest.vsix) 3. From either editor, pop open the Command Palette (Ctrl/CMD-Shift-P) and choose `Extensions: Install from VSIX…`. 4. To verify the installation, open the Command Palette again (Ctrl/CMD-Shift-P) and type `SpecStory`. You should see the available commands show up. ## 🌎 Why this will rock your world Think of [SpecStory](https://specstory.com) as your AI conversation time machine. * ⚑ Auto-save your conversations into digestible Markdown format (readable by both humans AND machines). * 🌐 Make your [vibe-coding](https://x.com/karpathy/status/1886192184808149383) adventures shareable via URLs at share.specstory.com. * πŸ§ͺ Auto-magically derive Copilot [custom instructions](https://code.visualstudio.com/docs/copilot/copilot-customization) and Cursor [project rules](https://docs.cursor.com/context/rules-for-ai#project-rules-recommended) to improve agent-first coding performance. 🧠 Your AI companion is about to get significantly less forgetful, and you won't have to lift a finger - let's go! # Data Privacy Source: https://docs.specstory.com/privacy Transparency into what we collect and access to deliver SpecStory ## Services we use to collect data We use [PostHog](https://posthog.com/) to collect product analytics. When you install the SpecStory Extension tracking is turned on by default. You may turn it off in settings via: `specstory.helpUsImprove`. * We log events including: when the extension is activated, when an auto-save occurs, when a manual save occurs, when a share occurs, when a custom rule is derived and when errors occur. * We use this telemetry to calculate total installs, active user counts and to understand other patterns like user retention. We also use [PostHog](https://posthog.com/) to collect web analytics, both on Specstory.com and share.specstory.com. * We use log events to understand time on site, improve usability in our share experience and monitor our own traffic and traffic to shares. * If you turn off `specstory.helpUsImprove` in the Extension settings it will not apply to the web analytics we collect. In SpecStory `v0.7.0` and later for the *optional* and Derived Rules feature, we use: * [Clerk.com](https://clerk.com/): for authentication and user management. * [Helicone.com](https://www.helicone.ai/): for LLM observability. ## What data is accessed and collected by feature ### Auto-saves and manual saves Usage of these features *never* transmits your prompts or code in assistant responses to SpecStory. Each of these features read from your local chat history stored in a `sqlite3 state.vscdb` or `chat.jsons` in different folders depending on your OS on your machine. * Windows: `%APPDATA%\Cursor\User\globalStorage\state.vscdb` * MacOS: `~/Library/Application Support/Cursor/User/globalStorage/state.vscdb` * Linux: `~/.config/Cursor/User/globalStorage/state.vscdb` * Windows: `%APPDATA%\Code\User\workspaceStorage\{hash}\chatSessions` * MacOS: `~/Library/Application Support/Code/User/workspaceStorage/{hash}/chatSessions` * Linux: `~/.config/Code/User/workspaceStorage/{hash}/chatSessions` These saves are then stored in your project's `.specstory` folder. ### Shares Usage of this features transmits prompts and code in assistant responses to SpecStory. This feature allows you to publish your local chat history to share.specstory.com. We store shares in [Cloudflare R2 Object Storage](https://www.cloudflare.com/developer-platform/products/r2/). * Shared content is anonymous in the sense that we do not require authentication to share. But it is *public*. * We generate a non-guessable UUID for every share at the time of creation. * When you share your history, the request includes a `device_id hash` from your machine. This allows us to allow you to uniquely edit it without being authenticated. * As an editor, you can delete sensitive information in the share. You may also request full deletion of the object by e-mailing support the URL of the share. ### Derived Rules Usage of this features transmits prompts, code in assistant responses, markdown header information you supply and your project's metadata to SpecStory. This feature allows you to save time and improve code generation quality. * When you authenticate into the Extension and turn on the feature, as you prompt we send your prompt history, prior derived rules, file headers and project directory metadata to an LLM. * We log these requests via Helicone by user to track cost, response quality, error rates and prevent abuse. * We conduct aggregate analysis on the requests made by users of this feature to improve it. # Quickstart Source: https://docs.specstory.com/quickstart Give your AI assistant a persistent memory. Best upgrade since coffee β˜• ## πŸͺ„ Your work saves itself, no cloud required! When you install SpecStory it begins its work in the background, **automatically saving πŸ—„οΈ** your AI chat history for your active project in `./specstory/history`. You can toggle this on and off in our [settings](/settings). ![Autosave your history](https://share.specstory.com/extension/autosave_your_history.gif) ## 🎯 Cherry pick your save worthy moments If you want to combine selected conversations into a single file, you can do that too. Just open the command palette (Cmd/Ctrl+Shift+P) and run `SpecStory: Save AI Chat History`. ![Never lose your chat history](https://share.specstory.com/extension/never_lose_your_composer_history_2.gif) * **πŸ“ Presto!** Run this command and watch your AI conversations transform into a beautiful markdown file right before your eyes! * **πŸ‘€ No waiting around** - it pops open instantly in your editor. (We love instant gratification!) * **πŸ’Ύ Like what you see?** Hit that Save button and your AI wisdom is safely tucked into your project files. * **🌳 Feeling git-ty?** Commit it to your repo just like any other file - because your AI conversations deserve version control too! ## 🌟 Share your history with a story! Share your chat history with others by opening the command pallette and running `SpecStory: Share AI Chat History`. ![share your chat history](https://share.specstory.com/extension/share_your_history_2.gif) * **🌎 Ready to share your AI coding adventures with the world?** One command sends your chat history sailing into the cloud, returning a magical URL just for you! * **🎭 No signup required** - your shares are anonymous. (But hey, keep those secret API keys and passwords to yourself, okay?) * **πŸ”— Pro tip:** Bookmark that special URL like it's your favorite cat gif - you'll want it later! * **✏️ As the creator, you can add a description to your share, paste images, and curate which chats to include.** * **πŸ“ Mark it down:** You can add tons of details to your share by adding sections of markdown-formatted text in between any parts of the conversation. * **πŸ—‘οΈ Having second thoughts?** Need to make something disappear? Drop us a line at [support@specstory.com](mailto:support@specstory.com) **with a link to the share** and we'll take care of it faster than you can say "delete my search history." ## πŸ§ͺ Auto-magically derive Rules for AI