Fix background compound command rewrite breaking syntax
Cluster 98222. Data as of
Nothing open on GitHub. Fix merged in #101662 on 2 Sep 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 #101662. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #101662. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address a bug where rewriting compound background commands (e.g., { ... } &) corrupts shell syntax when a statement follows the ampersand. The fix targets the _rewrite_compound_background function to preserve parseable output in such cases.
Open issues0
Open PRs0
Fixes on record
-
#101662 fix(terminal): keep a statement after a backgrounded compound valid — remote kernel spawn (salvage #42278)
files:
tests/tools/test_terminal_compound_background.py,tools/terminal_tool.py
2 PRs closed without merging
From the close comments: duplicate 1 · superseded by another PR 1
Closed issues · 1
- Closed#98222[Bug]: execute_code remote kernel spawn always fails on Docker/SSH/Modal — _rewrite_compound_background corrupts commands with a statement after &
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
- #101662
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 2 Sep 2026