GSD Core v1.4.0 just dropped. This release makes GSD more native across agent runtimes, with Claude Code plugin distribution, richer Cursor/Cline/Gemini/Codex/Qwen/CodeBuddy support, a new research cache seam, safer hook/runtime behavior, and smarter CI scope controls. github.com/open-gsd/gsd-core

GSD-Pi v1.2.0 is live. This release is all about smoother, more visible agent workflows: running tool rail sweep, per-phase thinking controls, managed browser automation, TUI mouse support, latency instrumentation, post-unit gates, and a cleaner GSD-Pi Web identity. github.com/open-gsd/gsd-pi/

GSD Core v1.3.0 is live. This release sharpens the workflow engine with milestone-prefixed phase IDs, provider-neutral model policy presets, Vertical Slice mode, per-phase granularity controls & safer work tree handling. github.com/open-gsd/gsd-core…

GSD-Browser v0.1.28 is out. This release makes agent browser workflows more reliable, replayable, and easier to share as evidence. What’s new: Richer recording exports with before/after page state, command context, and focused network slices Replayable bundles with schema, manifest metadata, and state restoration hints Playwright test generation from recordings or exported bundles Safer artifacts with redacted cookies and high-entropy storage values Fixed attached-browser mode so existing CDP pages stay connected Hosted HTTP MCP auth verifier support and clearer MCP token guidance Built for agents that need to prove what happened, replay it, and share clean evidence without leaking sensitive browser state.

Double Release Day $GSD Pi v1.1.1 just dropped This release adds Claude Opus 4.8 support, new /gsd usage context observability commands, a smoother guided install flow, cloud MCP gateway runtime support, leaner prompt/tool surfaces, and a big stability pass across auto-mode, worktrees, packaging, CI, and provider handling. github.com/open-gsd/gsd-pi/

We just shipped $GSD Core v1.20 Large hardening and consolidation release for GSD Core. It adds security and supply-chain checks like markdown-link threat detection, stricter secret-scan governance, npm dependency integrity validation, and reproducible environment checks. It also continues the SDK retirement work by consolidating around @opengsd/gsd-core / gsd-tools, adds cross-provider effort controls and plan-vs-codebase drift protection, and includes many CI, Windows, test-determinism, workflow, and performance fixes. github.com/open-gsd/gsd-core…

$GSD Browser Codex is now a one-command setup. Install the CLI and automatically register the Codex Plugin in a single pass: No manual plugin configuration. No marketplace editing. Just install and start building browser-powered agents in minutes. github.com/open-gsd/gsd-brow…

Open GSD had a call with @AWSreInvent and @riotgames this afternoon. We love seeing how $GSD has helped Riot developers in their day to day workflow. Can't wait to help them even further with some of the changes we're adding. You may ... or may not ... see Us on stage in November in Vegas presenting

GSD-Browser just got a major upgrade. GSD-Browser now includes a full MCP server with 62 tools, resources, and executable prompts built specifically for autonomous agents. This release also includes a long list of fixes discovered through real-world agent testing. github.com/open-gsd/gsd-brow…

GSD-Pi has grown into something incredibly powerful — but with that power comes a LOT of options and configuration. So today, we’re making setup dramatically easier. Introducing the Open GSD Pi Config Generator: pi.opengsd.net We’ve already got templates ready for launch to help you get deployed faster, and you can even submit your own templates for other users to use and improve on. Less time configuring. More time building.

The Rebrand & Why As @ColinSolvely said: “In corp world/speaking… I’d be hard pressed to say anything but GSD and breeze past it.” And honestly, he’s right. While many of us will always know the original meaning behind GSD, we also recognize that building a serious platform means thinking bigger than the inside joke. So moving forward, GSD will officially stand for: Git. Ship. Done. The reality is simple. Using vulgarity in a product name may get attention early on, but it also creates friction with businesses, developers, partnerships, and long-term adoption. This lets us keep the identity, energy, and momentum behind GSD while giving it a stronger foundation and clearer direction moving forward. Same builders. Same mission. Better framing.

Introducing GSD Workbench. GSD Workbench is being built as the central development environment for the GSD ecosystem. A place where builders can create, manage, test, and deploy projects without fighting their tools every step of the way. The focus is speed, visibility, collaboration, and giving developers a cleaner workflow from idea to production. We’re designing Workbench to support real world project management, AI-assisted development, deployment pipelines, team collaboration, and modular tooling that can evolve with the ecosystem over time. This is not another bloated dashboard. This is infrastructure for builders. Development is officially underway.

An update on GSD-Cloud. The previous GSD-Cloud work and infrastructure were solely controlled by Lex, and we no longer have access to that environment or codebase. Because of that, GSD-Cloud is now being rebuilt from the ground up. Instead of trying to patch together what was lost, we’re taking the opportunity to redesign the platform correctly with transparency, scalability, and long-term ownership in mind. This reset is frustrating, but it also creates the chance to build something stronger than what existed before. We’re back to building.

We’re still waiting on @useblacksmith to approve our new account. Our builds are super slow right now on GH. Hopefully we can get the new releases out soon on GSD-Pi.

This is my commitment to the community. Open GSD will be built differently. No false promises. No hidden agendas. No disappearing act when things get hard. What happened hurt a lot of people financially and emotionally. Trust was broken. I can’t erase that. But I can choose how we move forward from here. Open GSD is about rebuilding with transparency, accountability, and community at the center. Not hype. Not smoke. Not ego. I’m committing to: Building in public Communicating honestly — even when the news isn’t good Staying present and accessible to the community Focusing on long-term utility over short-term excitement Creating something bigger than one person This isn’t about pretending the past didn’t happen. It’s about refusing to let failure be the final chapter. Some people will walk away, and I understand that completely. But for those still here — for the builders, believers, and people willing to stand back up after getting knocked down — I’m with you. Open GSD starts now. And this time, we build it together. — @jeremymcs opengsd.net/promise