/autoplan dispatches reviewers again
gstack 1.91.34.0: /autoplan works again on current Claude Code
0 reviewers allowedeach one denied with "retry"
every reviewer allowedin the foreground and with claude --bg
On current Claude Code, /autoplan refused every reviewer it dispatched and said retry. Now every reviewer goes through, in the foreground and in the background. A run already underway may see one more denial.
Long sessions are accepted
A session journal of any size is accepted
only a single record over 32 MiB counts as too large
Long sessions work again. The guard used to refuse any session journal over 32 MiB; now any size is accepted. A resumed session over a hundred mebibytes reached phase one in about seventy seconds.
The pre-push scan stops flagging known emails
The pre-push scan stops flagging your own email
git config user.emailno longer reportedemails in the historyno longer reportedHIGH secretsstill block the pushThe pre-push scan stops warning about your own email and addresses already in the repo's history. High severity secrets still block the push, and an address only another remote knows still reports.
One flagged file no longer stops the sync
One flagged file no longer stops the artifacts sync
nothing pushesno notice; one machine went 18 days without a push
that file waitsthe rest pushes, and every skill start says so
One flagged file used to stop the artifacts sync without telling you. One contributor's machine went 18 days without a push. Now that file waits, the rest pushes, and every skill start tells you.
New: gstack-doctor
gstack-doctor shows what's ready before you start a skill
New: gstack-doctor. One row each for your install, Bun, hooks, Codex, the artifacts sync, Claude Code and your largest session journal. It spends nothing unless you ask for a live check.
/ship opens the PR early with Greptile
In repos that use Greptile, /ship opens the PR early
In repos that use Greptile, /ship opens a draft pull request once its tests pass. Greptile reviews while ship runs its own checks, and its comments land in the same pass. Public repos get asked first.
Three smaller changes
Three smaller changes you may notice
Outside reviews that list findings without a severity tag now show unverified, never clean. Browser skills offer a tab you're already signed in to. And context restore stops handing you an older checkpoint.
Re-render older skills before October 21
Skills rendered before this release need re-rendering by October 21
todaythey source the Codex probe and print one deprecation line2026-10-21sourcing stops working in a release on or after this date/gstack-upgradere-renders themCHANGELOG.mdWhat this means for you, 1.91.34.0Skills rendered before this release still source the Codex probe and print a deprecation line. That stops working in a release on or after October 21st; upgrading re-renders them. The change log has the rest.
