-
Notifications
You must be signed in to change notification settings - Fork 1.1k
fix(claude): map TodoWrite updates to plan events #1387
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
samjandris
wants to merge
4
commits into
pingdotgg:main
Choose a base branch
from
samjandris:claude-plan-steps
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+165
−33
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
0ce647d
Map Claude TodoWrite updates to plan events
samjandris bdc5a4b
Handle lowercase TodoWrite plan updates
samjandris 606fbe6
Match Claude todo-write tools by name substring
samjandris 38e14ce
Stop classifying Claude todo tools as plan items
samjandris File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TodoWrite tools misclassified as file_change in lifecycle events
Medium Severity
The new code emits
turn.plan.updatedfor todowrite tools, butclassifyToolItemTypestill classifies "todowrite" as"file_change"because the name contains "write" (matching at line 422). This means theitem.startedanditem.completedlifecycle events reportitemType: "file_change"andtitle: "File change"for what is actually a plan/todo tool. A check for"todowrite"returning"plan"needs to be added toclassifyToolItemTypebefore the"write"check so the full item lifecycle is consistent with the new plan event.Additional Locations (1)
apps/server/src/provider/Layers/ClaudeAdapter.ts#L398-L441There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This review is valid. TodoWrite already emits
turn.plan.updated, but its lifecycle events are still classified asfile_change. So, the work log currently shows both afile_changetool event and a separatePlan updatedevent for the same action.I can fix that if desired, though it slightly widens the scope because it affects lifecycle classification and not just event emission. If so, should TodoWrite still appear as its own tool event, or should we only show
Plan updated?