fix: Add UTF-8 encoding for cross-platform file reading in context-monitor #107
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.
Fixes #106
Problem
The context-monitor fails to read transcript files on Windows due to encoding mismatch. The script doesn't specify
encoding, so it defaults to cp949 on Windows, which can't handle UTF-8 content.
Solution
Added explicit UTF-8 encoding to the file open call:
This follows Python best practices and ensures the code works across all platforms.
Testing
Tested on Windows 11 with Python 3.13. The statusline now correctly displays context information instead of "???".
Changes
Image