GitHub Copilot Support at last!
Four months ago, SpecStory flipped the lights on with one lovable child. Our Cursor extension. We promised ourselves we wouldn't rush into more kids. Then came your inbox-flooding chants: COPILOT, COPILOT, COPILOT.
Fine. You win. We're now officially a two-editor household, and GitHub Copilot (agent mode and all) just barged in, suitcase overflowing with autocomplete wizardry.
👉 Get SpecStory on the Visual Studio Code Marketplace.
Before anyone panics for Cursor’s feelings, here's the new family deal: Cursor remains our meticulous firstborn. The kid who turns in homework early, neatly color-coded.
Copilot? Well their new sibling whispers entire functions before you've even named the file. We get to play proud parent, autosave always rolling, preserving every AI interaction and late-night "why did Claude 3.7 refactor everything again?" rant while you craft your project's origin story.
Why did we break our "one kid" rule? Three reasons, wrapped neatly into a giant "duh":
-
You asked. Repeatedly. Loudly. Usually in ALL CAPS.
-
Agent mode slaps. Copilot's
1.300.0release graduated into something closer to a junior dev with a surprising grasp of project lore—exactly the kind of partner our intent-preserving engine thrives on. -
Context compounds. Two smart editors double the narrative depth. And turns out people like to use all of the them.
So open up Visual Studio Code, activate GitHub Copilot, search for SpecStory in the Extensions Marketplace (Ctrl/CMD-Shift-X) and smash Install. Hop freely between editors, compare their suggestions, and never again wonder, "What was past-me thinking?"
Cursor, Copilot, SpecStory. Two brilliant editors, one canonical memory capture mechanism. We can't wait to hear what you ship!