fix #84857: skip CLI runtime harness preflight during compaction#84878
fix #84857: skip CLI runtime harness preflight during compaction#84878zhangguiping-xydt wants to merge 1 commit into
Conversation
|
Codex review: needs maintainer review before merge. Workflow note: Future ClawSweeper reviews update this same comment in place. How this review workflow works
Summary Reproducibility: yes. Source inspection shows current main resolves PR rating Rank-up moves:
What the crustacean ranks mean
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics. Real behavior proof Risk before merge
Maintainer options:
Next step before merge Security Review detailsBest possible solution: Merge the targeted CLI-alias bypass with its regression test after normal CI, keeping broader CLI compaction behavior separate unless a real runtime API gap appears. Do we have a high-confidence way to reproduce the issue? Yes. Source inspection shows current main resolves Is this the best way to solve the issue? Yes. The PR uses the existing CLI alias contract to skip only CLI-runtime harness preflight and lets the current non-harness compaction path continue, which is the narrowest maintainable fix for this call site. Label changes:
Label justifications:
What I checked:
Likely related people:
Codex review notes: model gpt-5.5, reasoning high; reviewed against 43c6c260deb0. |
|
ClawSweeper PR egg ✨ Hatched: 🥚 common Neon Crabkin Hatch commandComment Hatchability rules:
Rarity: 🥚 common. What is this egg doing here?
|
|
@clawsweeper automerge |
|
🦞🔧
Draft PRs stay fix-only until GitHub marks them ready for review. Pause with Automerge progress:
|
|
ClawSweeper 🐠 reef update Thanks for the contribution. ClawSweeper hit a branch-permission wall on this PR, so it opened a replacement branch to keep review moving while preserving credit. Why replacement: ClawSweeper could not update the source PR branch directly; GitHub did not grant sufficient push rights to the bot for that branch.
fish notes: model gpt-5.5, reasoning high; reviewed against de553c3. |
Summary
claude-cliruntime sessions through harness selection and throwsMissingAgentHarnessError, so over-threshold sessions fail before dispatch and leak the warning text back to users.src/agents/harness/selection.tsand locked it in with a regression test insrc/agents/harness/selection.test.ts.Fixes #84857
Real behavior proof
MissingAgentHarnessError(\"claude-cli\")forclaude-cliruntime sessions, which avoids user-visible warning replies and lets the queued compaction path continue.undefinedinstead of throwingMissingAgentHarnessError, so the caller can continue into the non-harness compaction path; the regression test covering theclaude-cliruntime case now passes.Regression Test Plan
src/agents/harness/selection.test.tsmaybeCompactAgentHarnessSessionreturnsundefinedinstead of throwing when the resolved model runtime isclaude-cli.Root Cause
maybeCompactAgentHarnessSessionunconditionally calledselectAgentHarness, so model runtime policy values likeclaude-cliwere treated as harness ids and triggeredMissingAgentHarnessError.