release: Codex Exporter 0.2.0 - #1
Merged
Merged
Conversation
lowestprime
marked this pull request as ready for review
July 18, 2026 20:50
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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
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
Publishes Codex Exporter 0.2.0 as a fidelity-oriented,
automation-first exporter for local Codex session JSONL data, with
optional native dialogs and terminal browsing.
Major changes
tiktokenmetadata with explicit regex fallback.never reconstructed.
and machine-readable JSON.
codex-exportconsole entry point.Windows UTF-8 regression addressed
Windows redirected Python streams can inherit a legacy code page such as
CP1252. The browser uses Unicode typography, and JSON output may contain
arbitrary Unicode session data.
The CLI now reconfigures stdout and stderr to UTF-8 at process startup. The
browser regression deliberately forces
PYTHONIOENCODING=cp1252on every CIplatform and verifies that the browser heading and final JSON result remain
valid UTF-8.
Privacy and fixture policy
exports, and local session identifiers are excluded.
tests/fixtures/.are excluded from the commit.
Distribution hygiene
MANIFEST.inexcludes.pyc,.pyo, and__pycache__content.artifact.
Local validation completed
skipped.
codex-export --versionreportscodex-export 0.2.0.git diff --checkpasses.Review focus
Please pay particular attention to:
Merge and release
Use squash merge.
Tag
v0.2.0only after:mainbranch installs successfully on Windows;