Skip to content

Ask the planner to shorten a long plan below the limit - #20

Merged
noah-meierlabs merged 1 commit into
mainfrom
fix/planner-shorten
Nov 14, 2026
Merged

noah-meierlabs merged 1 commit into
mainfrom
fix/planner-shorten

Conversation

@noah-meierlabs

Copy link
Copy Markdown
Contributor

A plan over MAX_PLAN (1500 chars) was sent back to the planner once with only the error, and the second answer could still be slightly too long, so the proposal failed without a plan (gs2 proposal #35, 1558 chars). The correction now asks for at most 90% of the limit (1350) and says what to drop (explanations, commands the agent finds itself), and the planner gets two corrections instead of one. Test added; fmt, clippy and cargo test pass.

🤖 Generated with Claude Code

A plan over MAX_PLAN was sent back once with only the error, and the
second answer could still be a few characters too long, so the proposal
failed without a plan (gs2 #35, 1558 characters). The correction now
asks for 90% of the limit and says what to drop, and the planner gets
two corrections instead of one before it fails.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@noah-meierlabs
noah-meierlabs merged commit 5e24077 into main Nov 14, 2026
1 check passed
@noah-meierlabs
noah-meierlabs deleted the fix/planner-shorten branch November 14, 2026 15:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant