Migrate back to GSD-1??

[stoersignal]

is there a way to roll back somehow? Ifor the last 5 weeks i am working on one big project and it was progressing pretty well. since i started with gsd-2 everything is breaking apart. since i have my claude max subscription i never reached the limit. for the last 2 days i hit the limit each and every cycle. my plugin already has 2 working lfos and for a retrigger function and a waveform display i wanted to add it takes 6 hours(???) and then aborted auto mode because of a missing summary......... it would be really great if there would be the option......

[turtlemath]

agree totally. I migrated to gsd 2 for a few projects and it totally fucked all of them up. I need to go back.

[jeremymcs]

Hey @stoersignal and @turtlemath — really sorry to hear GSD-2 hasn't been the experience you were hoping for after migrating from GSD-1.

To answer the rollback question directly: there's no official downgrade path from GSD-2 back to GSD-1, so we'd really like to understand what's going wrong and get it sorted for you.

First — make sure you're on the latest version. Run gsd --version to check and /gsd update to upgrade. We've been shipping improvements rapidly and there's a good chance your issue has already been addressed.

If you're still seeing problems after updating, could you share a bit more detail on what you're experiencing?

• What's going wrong specifically — worse output quality, unexpected behavior, something else?
• Is it consistent or does it happen in certain situations?
• If you're hitting any errors, run /gsd forensics and paste the output — it'll give us a much clearer picture of what's happening under the hood.

The more detail you can share, the faster we can help.

[thewebartisan7]

@jeremymcs As I understand auto mode is optional, and we can do everything like before step by step, am I right?
I am going to migrate from version 1 and I will let you know if I found any issue mentioned here.

[turtlemath]

@jeremymcs Appreciate the response. I was on the latest version when this happened. I was actually checking back almost every hour hoping to see progress or updates from GSD2.

Here are some of the patterns/problems I specifically encountered while using GSD2 over multiple projects. At least these are the ones that were so frustrating I remember them haha.

• Auto-mode runs through migrate/audit/fix/validate/complete sequences silently, then stops. No summary, no next steps, nothing. I had to paste full session logs into a separate Claude window just to understand what it had done. one time auto-mode got stuck in a loop and I had walked away from my computer for a phone call. It was just looping and looping haha. I got back to my computer and found it had wracked up 17 dollars in tokens and was still just running in circles. I had to terminate that session to get it to stop.
• Marks phases "complete" that aren't. It auto-completed phases with human-dependent steps (manual review, external input, handoff). State files said "complete" but deliverables were missing or wrong. Once the tool's own status tracking is unreliable, the whole planning system is pointless.
• Destructive actions without checking. Re-ran a full pipeline step to fix one record, overwriting hours of manual review work. The fix was a one-line CSV edit. Then told me "your data is intact" without verifying -- I caught the error by checking row counts myself.
• Copied files from a worktree to main without checking logic divergence. The worktree version had different filtering that dumped hundreds of incorrect records into output files. Told me the files were "ready." Again, I caught it manually.
• State tracking drifts from reality. After auto-mode, the roadmap showed completed phases as "Planned" or "Not started." State file said "status: unknown."
• No recovery path. /gsd pause said auto-mode wasn't on because sessions had already finished. No session summary, no audit trail, no next steps.

Core issue for me is that GSD1 is more collaborative. I could see what was happening, interrupt, ask questions. GSD2 felt like it was almost treating me like something to run around lol. yes, it would be cool if GSD1's processes could go faster, but it feels hard to give GSD2 so much control and trust it's being thorough.

[stoersignal]

that sums it up pretty well

[benjaminalgreen]

Agree with most of turtle's points. I struggled with GSD-2 due to my lack of control and visibility in the system. The automation and progression systems are really cool, but for the complexity of projects I work on I need to have a much stronger hand in the decision-making process.

[trek-e]

GSD-2 has gone through significant stability improvements since the rough patch you described. If you're still having issues, the latest version (v2.76.x) has most of the stuck-loop, stuck-state, and provider reliability fixes from the past few months. Happy to help debug if you hit a specific error — the /gsd forensics output tells us a lot.