01 — SpecStory: Product, Business, Reception

Research conducted: 2026-07-03. Evidence tiers (A/B/C/D) per the brief. Mechanism internals live in 02 — SpecStory CLI internals; this chapter covers what SpecStory is as a product and business.

What SpecStory is

SpecStory is the best-known "session capture" product: it auto-saves AI coding-assistant conversations to local markdown under .specstory/history/ in the project, then layers search, sharing, cloud sync, and skill-mining on top. Tagline: "Intent is the new source code" (README); site headline "Turn your AI development conversations into searchable, shareable knowledge" (specstory.com). Company thesis: the prompt/response history — the intent — is a durable asset worth versioning alongside code.

Product surface (as of 2026-07-03)

Adjacent: SpecFlow (open methodology site, 141★), intent-releases ("system of record for human decisions"), and unreleased git-provenance research inside the CLI repo (covered in 02).

The open/closed split (load-bearing fact)

The capture engine for terminal agents is fully open source — the entire specstory-cli Go tree, including every provider parser, ships under Apache-2.0 in getspecstory. The IDE extensions are closed: the repo's own installation table marks the Cursor and VS Code Copilot extensions "Source: Closed"; the GitHub repo hosts only their issues and releases. On open-sourcing the extension, the FAQ says "we have not made a decision" (docs.specstory.com/faqs). Practical consequence: the CLI's extraction machinery is directly reusable prior art (license-compatible with jackin❯'s Apache-2.0), while the editor-side extraction (Cursor state.vscdb, Copilot chatSessions JSON) is only documented via FAQ statements and community reverse engineering (tier B/C).

Pricing and business model

Everything capture-side is free as of 2026-07-03: extension ("free as in beer" — FAQ), CLI (open source), Cloud (free, single-user). Monetization has visibly moved to Stoa ($5/hour, no seats, $50 free credit — pricing). Company: SpecStory, Inc., Boston, founded 2024; founders Jake Levirne (CEO, ex-DigitalOcean/Docker), Sean Johnson (CTO), Greg Ceccarelli (CPO, ex-GitHub/Pluralsight); seed investors NP-Hard Ventures, Mango Capital, Tola Capital, amount undisclosed (specstory.com/company, Specter monitor; tier B/C).

Read for jackin❯: the capture layer itself has been commoditized to $0 by its own vendor — value accrues in what sits on top (search, resume, skills-mining, team surfaces). That matches the Déjà Vu framing of capture as infrastructure, not product.

Reception

• Traction signals (2026-07-03): 1,268★ / 78 forks on getspecstory; 22.4k marketplace installs; badge endpoints exist for installs/active-users/sessions-saved but publish no public totals (tier B).
• Positive: Cursor forum launch thread called it a "godsend" (forum thread); recurring HN endorsement pattern — commit .specstory/history to the repo so AI conversations ride along in PRs (HN 44976568); their "Why Git is no 'good' for AI-generated code" essay reached 35 points (HN 43557698).
• No breakout moment: no large Show HN; effectively no Reddit footprint found (tier D — absence).

Complaint themes (GitHub issues, tier B)

These are the field-tested failure modes any capture feature must design against — the fragility mechanics are analyzed in 02:

1. Editor updates break closed-source extraction. Pinned issue #53: "Cursor 0.49.x introduced breaking changes" — official advice was to downgrade Cursor. #186: Cursor 2.5.26 added new message types → 110+ errors/sec. #138: a Copilot update broke saving.
2. Polling costs CPU. Battery/CPU drain from DB polling (#28, #47, #208, #220); specstory run claude busy-waiting 20–50% CPU while idle (open #207).
3. Silent incompleteness. Lost chats (#164), partial saves (#82, #112, #174), duplicate files with differing completeness (#196).
4. Privacy defaults. PostHog telemetry on by default (#100); derived-rules calls logged via Helicone (privacy doc); open #224: histories are not gitignored by default, so transcripts (and any secrets inside) can land in public repos — getspecstory's own committed history demonstrates the pattern.
5. Known capture gaps: Cursor Cmd-K inline edits (#27), Cursor Agents Window (#212), images (#64); Windsurf declared impossible — "encrypted protobufs… locked that data away and thrown away the key" (maintainer, #26).

What jackin❯ should take from the product story

• Local-first markdown in the repo is the adoption hook; cloud is optional and single-user even after ~1.5 years.
• The open CLI + closed extension split maps exactly to extraction difficulty: file-store parsing is commodity, editor-DB scraping is a maintenance treadmill they keep private.
• SpecStory's newest moves (cross-agent resume, session portability, Lore skill-mining) all monetize the archive, validating Déjà Vu's premise that the normalized cross-agent store is the strategic asset.