Preserve non-ASCII characters in tool input when extracting conversations#43
Open
hewenpang wants to merge 1 commit into
Open
Conversation
…ersations Add ensure_ascii=False to json.dumps() when serializing tool_use input in extract_claude_logs.py so that CJK and other non-ASCII text (e.g. Chinese metric/dimension names in MCP tool calls) are shown as readable characters instead of \uXXXX escape sequences in exported logs. Co-authored-by: Cursor <cursoragent@cursor.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds
ensure_ascii=Falseto bothjson.dumps()calls that serialize tool use input insrc/extract_claude_logs.py, so that exported conversation logs show non-ASCII characters as readable text instead of Unicode escape sequences.