gstack’s /cso eval cells run the real scanners again

1 day ago

gstack 1.91.68.0 to 1.91.69.0 (2026-10-08 to 2026-10-10): paid /cso eval cells run the real scanners again, get five minutes to write their report, keep their spend when they fail, and stop tripping on their own files. https://github.com/garrytan/gstack/blob/main/CHANGELOG.md#191690---2026-10-10 https://github.com/garrytan/gstack/blob/main/CHANGELOG.md#191680---2026-10-08 https://github.com/garrytan/gstack/commits/main

Ask

Ask about this presentation

Answers are generated from this presentation.

Chapters

  1. 0:00Real scanners
  2. 0:14Time to finish
  3. 0:27Spend kept
  4. 0:42Fixes
Show transcript

Real scanners

gstack logo

gstack’s /cso eval cells run the real scanners again

Comprehensive cell, beforestatic-only review
Launcher outside the sandboxreal scanners
Real scannersTime to finishSpend keptFixes
garrytan/gstack · CHANGELOG.md 1.91.68.0

Paid /cso eval cells were quietly falling back to a static-only review, because the scanner launcher couldn't reach Docker inside Claude Code's sandbox. The launcher now runs outside it, and every other command stays sandboxed.

Time to finish

The agent gets five more minutes to write its report

Beforekilled at budget
Nowbudget + 300 s
Evidence after the deadline is still refused, so the measured budget is unchanged.
Real scannersTime to finishSpend keptFixes
garrytan/gstack · CHANGELOG.md 1.91.69.0

Agents were killed at the exact budget, just before they could write their report. Now they get five extra minutes to finish it. Evidence after the deadline is still refused, so the measured budget doesn't change.

Spend kept

A failed cell still records what it spent

Failed receipt keeps tokens · estimated cost · turns · duration
Covers a failed post-run check and a timeout
A failed receipt never counts as succeeded.
Real scannersTime to finishSpend keptFixes
garrytan/gstack · CHANGELOG.md 1.91.68.0 · 1.91.69.0

A cell that failed used to leave no receipt, so its spend showed up as zero. Now it writes a failed receipt with its tokens, estimated cost and turns. That holds for a failed check and for a timeout, and it never counts as a success.

Fixes

Three false failures are gone

No stray empty .mcp.json left in the sealed source
Helper run names no longer flagged as secrets
Every failure names its check and the offending path
CHANGELOG.md · What this means for youfull details
Real scannersTime to finishSpend keptFixes
garrytan/gstack · CHANGELOG.md 1.91.68.0 · 1.91.69.0

Claude no longer leaves an empty config file in the sealed source. The helper's own run names stop reading as phone numbers or wallet addresses. And every failure names the check that broke. Details are in the changelog.