Skip to content
Discussion options

You must be logged in to vote

You’re right that this is quite an edge case - hitting the output limit during the planning phase usually means you’re working with a very large specification.

The issue you’re experiencing is related to output token limits rather than API limits. When an agent like Task Breakdown generates more than ~32K tokens of output, it gets truncated and the work is lost.

The best workaround is to use the step command to give the agent explicit instructions on how to handle large outputs:

codemachine step task-breakdown "Use a write-then-append flow. Same file, fixed chunks of 500 lines. Keep appending chunks until the full tasks file is produced to avoid hitting output limits"

This tells the agent…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@meakelc
Comment options

Answer selected by moazbuilds
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants