feat: include operation context in mistake_limit_reached error message #10878
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.
Summary
This PR attempts to address Issue #10855 by including operation context in the
mistake_limit_reachederror message. When users see "Roo is having trouble..." they now also get context about what operation was being attempted.Changes
mistake_limit_operation_contextwith value "While attempting: {{operation}}"getLastAttemptedOperationContext()helper method that extracts the last tool use fromassistantMessageContentand formats a human-readable operation description (e.g., "write_to_file for 'path/to/file'")Example
Before:
After:
Testing
Feedback and guidance are welcome!
Important
Adds operation context to
mistake_limit_reachederror messages inTask.tsfor better user understanding.mistake_limit_reachederror message inTask.ts.getLastAttemptedOperationContext()to extract and format operation context.mistake_limit_operation_contextkey tocommon.jsonfor error message context.This description was created by
for 558eced. You can customize this summary. It will automatically update as commits are pushed.