🤖 fix: truncate status_set messages at 60 chars instead of failing #487
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
status_settool previously validated message length at 40 characters via Zod schema, causing tool failures when agents provided longer messages. This changes the behavior to gracefully truncate at 60 characters with an ellipsis.Changes:
STATUS_MESSAGE_MAX_LENGTHconstant (60 chars) totoolLimits.ts.max(40)Zod validation from schematruncateMessage()helper that truncates to 59 chars + "…"Behavior:
This eliminates validation errors for long status messages while maintaining a reasonable display limit.
Generated with
cmux