Guard against NUL bytes in terminal/lifecycle code
Cluster 77988. Data as of
Nothing open on GitHub. Fix merged in #80258 on 6 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #80258. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These members address crashes or errors caused by embedded NUL bytes appearing in command tokens, affecting lifecycle guard and terminal script scanning paths. Fixes are applied to prevent unhandled exceptions in both areas.
Open issues0
Open PRs0
Fixes on record
-
#80258 fix(cron): make the lifecycle guard total — sanitize at ingestion, not per-syscall
files:
cron/lifecycle_guard.py,cron/scheduler.py,tests/cron/test_cron_no_agent.py,tests/hermes_cli/test_gateway_restart_loop.py,tools/terminal_tool.py
2 PRs closed without merging
From the close comments: superseded by another PR 2
Closed issues · 1
- Closed#77988lifecycle_guard: unhandled ValueError ("embedded null byte") crashes every terminal-tool call once a NUL byte appears in a command token
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #80258
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 6 Aug 2026