Which agents work with it?

Any agent that reads skills from a directory. Claude Code, Codex and Gemini CLI read it natively; Cursor and VS Code connect over MCP.

The voice runs on your own machine, so there is nothing to meter. The first run downloads it, about 340 MB.

Yes. The skill is MIT-licensed and the authoring format is public.

Create

gstack now fixes a bug you have already diagnosed without opening /investigate

59 minutes ago

@gstack Subscribe

gstack 1.91.202.0 to 1.91.203.0 (2026-10-25): when you name a bug's cause, gstack checks it once and fixes it without opening /investigate; an unknown cause gets one bounded look first. Team-mode auto-update now waits for live gstack sessions instead of moving the checkout under them. Release notes: https://github.com/garrytan/gstack/blob/main/CHANGELOG.md#1912030---2026-10-25 https://github.com/garrytan/gstack/blob/main/CHANGELOG.md#1912020---2026-10-25 Commits: https://github.com/garrytan/gstack/commits/main

Ask about this presentation

Show transcript

Diagnosed

gstack now fixes a bug you have already diagnosed without opening /investigate

every bug report → /investigate

named cause→1 read-only check→fix→focused test

DiagnosedUnknownTeamVerdict

garrytan/gstack · CHANGELOG.md · 1.91.203.0

gstack no longer sends every bug report straight to investigate. When you name the cause and a narrow fix, it checks the evidence once, read-only, then fixes it and runs the focused test.

Unknown

When the cause is unknown, one short look before any edit

The triage pass finds the root causefix it

Still unclear, or the check contradicts you/investigate first

A failing test or stack trace no longer counts as proof of its cause.

DiagnosedUnknownTeamVerdict

garrytan/gstack · CHANGELOG.md · 1.91.203.0

When the cause is unknown, gstack takes one bounded look and fixes only if that finds the root cause. Anything unclear goes to investigate before any edit. A failing test is no longer proof of its cause.

Team

Team-mode auto-update waits for live gstack sessions

UPDATING · checkout moved mid-workflow

SKIP leased pid=<pid>/<age>

A dead or stale lease never blocks. The next session start tries again.

DiagnosedUnknownTeamVerdict

garrytan/gstack · CHANGELOG.md · 1.91.202.0

On a shared team install, the session-start auto-update could move the checkout while another session was mid-workflow. Now it sees that session's lease and skips. A dead lease never blocks, and the next session start updates.

Verdict

If your team shares one gstack install, I would upgrade now

CHANGELOG.mdgarrytan/gstack · 1.91.202.0 to 1.91.203.0

DiagnosedUnknownTeamVerdict

garrytan/gstack · CHANGELOG.md · 1.91.202.0

If your team shares one gstack install, I would upgrade now, because auto-update stops moving the checkout under a running workflow. The changelog has the full detail.