gstack gained 12,654★ this week — plus 3 tools you should know

The Lens

gstack is Garry Tan's Claude Code setup, open sourced by the Y Combinator CEO: 23 specialist slash commands that act like a virtual team (a CEO who rethinks the product, an eng manager who locks architecture, a designer, a reviewer, a QA lead who opens a real browser, a security officer and a release engineer), plus power tools like /office-hours, /review and /ship. All Markdown, MIT licensed. It's built for Claude Code, with experimental ports to Codex, OpenCode, Cursor, Factory, Kiro and Copilot CLI where its safety hooks are advisory rather than enforced. Install clones it into ~/.claude/skills/gstack and runs a setup script that needs Bun, and it keeps state in ~/.gstack too. Browser QA drives the Aside browser on macOS and falls back to its own Chromium. Solo founders and small teams who want an opinionated, ready-made workflow get the most here, free. Larger teams with their own conventions will mostly mine it for ideas. Telemetry stays off unless you opt in. The catch: it moves fast with no tagged releases, so your setup changes under you every time you pull. The optional GBrain setup can ask for a Supabase access token to create a project for you, so read what you're granting. And it's one person's taste, opinionated by design.

The Lens

OpenSpace is a librarian for the skill files your coding agent piles up. Version 2, released in July 2026, dropped the original self-evolving-agent pitch for something concrete: find the right skill, track whether it worked, share the ones that did, retire the ones that did not. All MIT licensed, including the community library at open-space.cloud. Running it means Python 3.12 or newer, a pip install, and wiring an MCP server into Claude Code, Codex, OpenClaw, or nanobot. Skills and execution stay local, and the cloud is optional. The dashboard is a second install needing Node 20. You bring your own model key, so the running cost is tokens. Solo developers with a dozen skill files do not need this, and a curated pack like slavingia/skills is a smaller commitment. It pays off once a team shares hundreds of skills and nobody can say which still work. The catch: this comes out of an academic lab, and its Terminal-Bench 2.1 result, 65.2% cold to 78.7% warm, was run on its own harness. Self-evolving skills mean an agent rewriting its own instructions, and the restrictive policy that limits it to repairs is not the default. The shared library is still thin.

The Lens

Lightpanda is a headless browser written from scratch in Zig, not another Chromium wrapper. Your Puppeteer or Playwright scripts connect to it over CDP just as they'd connect to headless Chrome. On the project's own 100-page benchmark it used about 16x less memory and finished about 9x faster. It's AGPL-3.0 and free to self-host. Running it is a single binary or one docker run exposing a CDP server on port 9222. Version 1.0 shipped in October; it now speaks WebDriver BiDi, runs as an MCP server for AI agents, and has an agent mode that saves a session as a replayable script. Linux and macOS only; Windows goes through WSL. Lightpanda Cloud is the paid side: Explorer is free with 10 browser hours a month, Builder is $19/month for 300 hours and 30 concurrent sessions, then $0.08 per extra hour. Bring your own proxy on both. Solo: self-host or Explorer. Small teams: Builder, or Browserless and Browserbase if you need real Chrome. At scale, self-hosting is where the memory savings pay off. The catch: it isn't Chrome. PNG and PDF dumps are text-only renderings, so visual testing is out, and JavaScript-heavy sites can still break. Telemetry is on by default.

The Lens

This Claude Code skill turns any repository into a beautiful, interactive single-page HTML course. Point it at a codebase, and it generates a structured learning experience that walks through the architecture, key files, and how everything connects. Built specifically for non-technical 'vibe coders' who learn by doing and want to understand what they built (or what someone else built). The output is a single HTML file you can share, host, or open locally. No language specified in the repo. It's a Claude Code skill file, not a traditional software project. The catch: the quality depends entirely on Claude's understanding of the codebase. Complex, poorly-documented codebases will produce courses with gaps. And 'single-page HTML' means everything is in one file. Great for sharing, awkward for very large codebases. This is a skill, not a product. It runs inside Claude Code only.