Conversation
Marks dev as the development state after shipping 0.12.0, per the -dev rule. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Every /describe and /review on an installed Windows build died with PermissionError under C:\Program Files. The cause is a bad file in the package, not a permissions setting. litellm points TIKTOKEN_CACHE_DIR at its own tokenizers/ directory and ships encoding files there to be offline-capable, but the files it ships fail the expected_hash pinned by the tiktoken it depends on -- all three of them. tiktoken therefore treats the cache as invalid on every run and re-downloads into site-packages, which is writable while building and read-only once installed. It is not model specific: every path that counts tokens goes through it. scripts/tiktoken-cache.py prime repairs the bundled bytes at assemble time, so the cache is a hit and nothing is written at runtime. verify asserts it, and runs after slimming so a slim rule that deletes the cache is caught too. The assertion compares hashes rather than just loading the encoding, because loading proves nothing here: a stale file loads fine on a machine that can re-download it. That is exactly how 0.12.0 shipped -- assembled clean, smoke tested clean, then failed on the first run of every install. Expected hashes are read from the installed tiktoken rather than copied here, so they cannot drift from it on the next upgrade. Documents the general rule in AGENTS.md and the runtime design doc: the install directory is read-only, a dev machine never shows this because vendor/ is writable, so a dependency that writes under its own package must be pre-populated at assemble time and asserted. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Patch release for the read-only install failure (#232): version, changelog section in both locales with their compare links, lockfile synced. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
fix(pragent): bake the tiktoken encodings so a read-only install works (0.12.1)
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.
Patch release for 0.12.1 — fixes the read-only install failure (#232) that makes the released 0.12.0 Windows build unusable.
Pre-release checklist
apps/desktop/package.jsonset to0.12.1, lockfile synced## [0.12.1] - 2026-09-10in both locales, each with a[0.12.1]: …/compare/v0.12.0...v0.12.1link referencelint/typecheck/test/buildpass.What changed
One fix (#233): the tiktoken encoding files bundled with the review engine were out of date, so tiktoken re-downloaded them into the installation directory on every run — which has no write permission under
C:\Program Files. They are now baked in correctly at assemble time, and a smoke-test assertion prevents shipping them stale again.Verified against a genuinely read-only directory in both directions: the fix loads, and restoring the stale file reproduces the reported error.
Post-release (mandatory, right after tagging)
masterintodev— verifygit log dev..masteris emptydevto the next-devTag must be
v0.12.1to match package.json.🤖 Generated with Claude Code