Claude Code
claude-code-actionwithallowed_non_write_usersbroke every Bash command on GitHub-hosted runners. If your CI went red after enabling that config, update to 2.1.227.- Max plan users may stop seeing a wrong "enable usage credits for Fable" prompt. Second fix for this gating bug in three weeks (more below).
- Nothing else actionable today. The rest is a
/tuiedge case, slash-command menu polish, and a minor event-loop performance win.
New in 2.1.227
2.1.227 (August 11, 2026)
- Fixed feature flags being evaluated without the user's subscription tier when a session started with an expired login token, which could wrongly prompt Max plan users to enable usage credits for Fable
- Fixed every Bash command failing under
claude-code-actionwithallowed_non_write_userson GitHub-hosted runners - Fixed
/tuibringing back a conversation that had been rewound to before its first message - Improved slash-command menu: blue now marks only the selected row, matched characters are bolded instead of recolored, and emoji or accented names keep their glyphs
- Improved performance: fewer event-loop stalls on file-not-found suggestions and at-mention size checks
Notes
Fable feature-flag gating: second fix in three weeks
2.1.219 fixed a stale cache that baked in a wrong "Requires usage credits" label on the Fable model row. 2.1.227 fixes a different path to the same symptom: when a session starts with an expired login token, the subscription tier is unavailable for feature-flag evaluation, so the flag defaults to gating Fable behind usage credits for Max plan users. Two distinct bugs, same visible result. If you were still seeing the prompt after updating past 2.1.219, this should close it out.