gstack

mirror of https://github.com/garrytan/gstack.git synced 2026-09-09 14:38:59 +02:00

Files

T

Garry TanandClaude Fable 5 a5b6522afe fix(browse): stop --force-restart kills the live daemon directly instead of booting a fresh one

`browse stop --force-restart` on a live-but-busy daemon fell through the
stop short-circuit into ensureServer(), whose force-restart path kills the
daemon and then STARTS A FRESH ONE (daemon + Chromium, multi-second churn)
just so sendCommand('stop') can shut it down again — the #2254 churn in
force clothing. gstack-upgrade's Step 4.8 sends users down exactly this
path when a stale daemon is busy after an upgrade.

The stop short-circuit now handles it: live pid + --force-restart → kill
the daemon (tree-kill on Windows, TERM→KILL on POSIX), reap the orphaned
Chromium + clear profile locks, remove the state file, exit 0 — no server
is ever started. Pinned in stop-dead-daemon.test.ts: a wedged live "daemon"
is killed, the state file stays gone (a booted daemon would have rewritten
it), and no Starting/Restarting output appears.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-08-16 14:13:15 -07:00

bin

feat: multi-agent support — gstack works on Codex, Gemini CLI, and Cursor (v0.9.0) (#226 )

2026-03-19 18:20:50 -07:00

scripts

fix(build): convert MSYS paths for Bun in the Windows server-bundle build (#2452 )

2026-08-16 10:59:36 -07:00

src

fix(browse): stop --force-restart kills the live daemon directly instead of booting a fresh one

2026-08-16 14:13:15 -07:00

test

fix(browse): stop --force-restart kills the live daemon directly instead of booting a fresh one