gstack 1.101.0.0 keeps a token-capped /ship going in Claude Code

1 day ago

gstack 1.101.0.0: a token-capped /ship now hands off to a fresh Claude Code agent that actually loads /ship, and a driven /ship stops itself at 100 minutes. iOS pull requests get a review sized to their risk, security findings stay out of PR bodies, and /ship on Codex gets past its coverage audit.

Ask about this presentation

Chapters

  1. 0:00Token-capped /ship hands off
  2. 0:15Stops at 100 minutes
  3. 0:28Reuses CI’s passing run
  4. 0:41Fewer owner stops
  5. 0:55One PUSH line
  6. 1:0602 Reviews
  7. 1:09Swift sorted by risk
  8. 1:23Private data gets every reviewer
  9. 1:35Security findings stay private
  10. 1:48Secrets check
  11. 2:0103 Skills
  12. 2:05No bug rule
  13. 2:17/ship on Codex
  14. 2:28/autoplan’s second model
  15. 2:45Prefixes, monorepos, office hours
  16. 2:59Changelog
Show transcript
  1. A token-capped /ship hands its last steps to a fresh Claude Code agent. That agent got no prompt, and given one, it still loaded the skill in zero of sixty runs. Now the prompt arrives and opens with the typed command.

    Slide text
    gstack logo

    gstack 1.101.0.0 keeps a token-capped /ship going in Claude Code

    /ship hands its last steps to a fresh Claude Code agent
    Input must be provided either through stdin or as a prompt argument
    /ship loaded in 0 of 60 sessions
    → /ship --continue <brief>
    #4448 · gstack-evals#366
    /ship Reviews Skills
    garrytan/gstack · CHANGELOG.md · 1.101.0.0
  2. Conductor agents running /ship made over a hundred calls where the driver makes about ten, and ten of twelve ran past 100 minutes. Now /ship stops itself there and saves its place.

    Slide text

    A driven /ship now stops itself at 100 minutes and saves where it was

    Conductors, with the limits written as prose
    121 to 308 calls · 10 of 12 past 100 minutes
    gstack-ship-phase run, one command per phase
    9 to 12 calls
    Past 100 minutes: STOP, and stop.json keeps the head, review passes and next act
    /ship Reviews Skills
    garrytan/gstack · CHANGELOG.md · 1.101.0.0
  3. If merging the base changes no file, /ship counts CI's earlier passing run. A suite with no passing CI run now stops and names the CI command, instead of running for an hour on your machine.

    Slide text

    /ship reuses CI’s passing test run when a base merge changed no file

    merge main → same file tree as the tested commit
    → CI’s passing run counts, named in the output
    $ gstack-ship-preflight --tests-only
    SHIP_LANE_NOT_CARRIED + the CI command to run
    GST-3019
    /ship Reviews Skills
    garrytan/gstack · CHANGELOG.md · 1.101.0.0
  4. After a main merge, one regenerated hash in 94 files stopped /ship for an owner, and so did a reviewer's prose that only confirmed code. Neither stops it now. Prose naming a real blocker still blocks.

    Slide text

    Base-merge text and a reviewer’s confirmation prose no longer stop /ship

    Base merge: one regenerated preamble id in 94 files read as a behavior change
    Reviewer prose: “a High or Critical challenge…” read as a Critical finding under NO FINDINGS
    Still blocks: “no Critical issues except the token leak in log.ts:3”
    /ship Reviews Skills
    garrytan/gstack · CHANGELOG.md · 1.101.0.0
  5. The push step now always ends with one line: pushed, already pushed, or failed with a reason. The old push lines are gone, so update anything that matched them.

    Slide text

    /ship’s push step now ends with one line that says whether it pushed

    PUSH: pushed remote=origin ref=<branch> head=<full sha>
    PUSH: already_pushed remote=origin ref=<branch> head=<full sha>
    PUSH: failed reason=PUSH_REJECTED
    PUSH: pushed <short sha> to origin/<branch>
    PUSH: ALREADY_PUSHED <short sha>
    GST-3053 · docs/unattended.md#push-line
    /ship Reviews Skills
    garrytan/gstack · CHANGELOG.md · 1.101.0.0
  6. Next, iOS reviews and security findings.

    Slide text
    02

    Reviews that fit iOS, and security findings kept private

    /ship Reviews Skills
  7. A 55-line SwiftUI copy change used to get five reviewers and a coverage audit, because Swift had no rule. Now Swift sorts by risk, and networking code still gets the full review.

    Slide text

    An all-Swift pull request no longer gets the full review panel by default

    55-line SwiftUI copy change
    SCOPE_ERROR=unmatched → five readers + a coverage audit
    Swift, storyboards, asset catalogs → UI and app code
    Info.plist, entitlements → permissions
    Package.swift, project.pbxproj → config
    GST-3041
    /ship Reviews Skills
    garrytan/gstack · CHANGELOG.md · 1.101.0.0
  8. Swift code that asks for the microphone or location, or reads HealthKit or contacts, gets every reviewer. Plain SwiftUI views and settings stay on the light review.

    Slide text

    Swift code that touches private user data still goes to the full panel

    Permissions: microphone, speech, HealthKit, calendars, location, camera, photos
    User data: HealthKit, EventKit or contacts reads, file writes and deletes on the device
    Stays light: plain SwiftUI views, UserDefaults settings, file reads
    GST-3052
    /ship Reviews Skills
    garrytan/gstack · CHANGELOG.md · 1.101.0.0
  9. A security finding you ruled a note used to put its file, line and reason in the PR body, pointing straight at the exposure on a public repo. Now the body gets an opaque reference.

    Slide text

    A security finding’s file, line and reason stay out of your PR body

    Ruled note: <file>:<line> <reason>
    Ruled note: <opaque id> security finding, details recorded privately
    Covers security, auth, secret and red-team findings. Details stay in gstack-approvals list.
    /ship Reviews Skills
    garrytan/gstack · CHANGELOG.md · 1.101.0.0
  10. Spaced TypeScript generics, Python settings arguments and dotted field paths no longer stop a push. And the secrets check now catches a secret glued together with plus signs, or tucked in a comment.

    Slide text

    The secrets check stops flagging three kinds of ordinary code

    TypeScript: types with spaced generic arguments
    Python: aws_secret_access_key=settings.S3_SECRET_KEY,
    Field paths: "form.section.fieldName"
    Now caught: a secret built with + from short pieces, or written in a comment
    #4289
    /ship Reviews Skills
    garrytan/gstack · CHANGELOG.md · 1.101.0.0
  11. Then the skills, on Claude Code and Codex.

    Slide text
    03

    The router, Codex and /autoplan

    /ship Reviews Skills
  12. On 26 real bugs, the rule to check the cause once and write a failing test first gave no clear gain. So bug reports no longer load the gstack router.

    Slide text

    gstack no longer gives bug reports a special rule

    26 real gbrain bugs that plain Opus 5.5 had failed once
    gstack with the bug rule: 3 fixed
    plain Opus 5.5: 2 fixed
    +3.8 points · 95% interval −11.5 to +19.2
    The router’s description drops debugging. Planning, review, /verify, /qa and /ship are unchanged.
    /ship Reviews Skills
    garrytan/gstack · CHANGELOG.md · 1.101.0.0
  13. On Codex, /ship asked for Claude Code's agent tool and stopped at the coverage audit. Codex skills now use Codex's own spawn agent, once its multi-agent feature is on.

    Slide text

    /ship on Codex now gets past its test coverage audit

    Agent tool · subagent_type · run_in_background
    → stopped at the coverage audit (#4476)
    spawn_agent → wait_agent
    Needs Codex’s multi_agent feature on. The plan reviews’ timed fallback reviewer reports unavailable on Codex.
    /ship Reviews Skills
    garrytan/gstack · CHANGELOG.md · 1.101.0.0
  14. /autoplan marked finished second-model reviews unavailable, so sessions paid to run them again or dropped them. Unattended runs now do the review you turned on, and revise accepts what the first pass accepted.

    Slide text

    /autoplan stops calling a finished second-model review unavailable

    Judged by its own format: an INPUT: line and a gstack-findings fence (GST-3051)
    Unattended runs: with codex_reviews: enabled, the review runs in the foreground, up to 9 minutes
    revise: accepts a plan the first next accepted, without editing your file
    /ship Reviews Skills
    garrytan/gstack · CHANGELOG.md · 1.101.0.0
  15. With gbrain, prefixed skill names no longer reset after an update. /ship finds tests in monorepo apps that use their own import alias. And office hours quotes you when it recommends a mode.

    Slide text

    Prefixed skill names survive updates, and monorepo apps get their tests found

    skill_prefix=true: stays /gstack-retro and /gstack-review after an update with gbrain (#4413)
    Monorepo apps: /ship’s pre-gate reads @/ aliases from the nearest tsconfig.json (#4462)
    /office-hours: recommends a mode by quoting your own words
    /ship Reviews Skills
    garrytan/gstack · CHANGELOG.md · 1.101.0.0
  16. If you run /ship with a token cap in Claude Code, I would say upgrade, once anything matching the old push lines is updated. The new handoff was tried on two Claude Code versions. The gstack changelog has the rest.

    Slide text
    gstack logo

    Run a token-capped /ship in Claude Code? Upgrade.

    gstack CHANGELOG.md · 1.101.0.0
    The push line format: docs/unattended.md#push-line
    /ship Reviews Skills
    garrytan/gstack · CHANGELOG.md · 1.101.0.0

What happened in AI today, in your inbox

One short email each evening. Read it and you’re caught up.

Built with ❤️ in New York