Repository navigation
Chisle 3.5.0 — output styles stop fighting Chisle, and OMP works again #18
Replies: 2 comments
|
Per-agent update commands are now documented, since
Two that catch people out: OpenCode users should update explicitly. That update refreshes the compression plugin, not just the ruleset — it's how you get the CommonJS pin that stops the plugin failing to load under Node. The last five keep their rule file inside the repo. Full table with what each update actually refreshes: INSTALL.md |
|
For Codex, would it be difficult to provide it via a hook mechanism when installed as a plugin? I ask because the idea of adding entries to |
Uh oh!
There was an error while loading. Please reload this page.
npx chisle@latest --updateTwo features and two fixes. If you use Claude Code output styles, the first one matters to you.
Output styles no longer fight Chisle
Claude Code's output styles govern prose structure — a style tells the model to use a table for a comparison. Chisle's prose rules forbid tables the question didn't ask for. Both landed in the same context with no precedence between them, so the result varied turn to turn.
Chisle now reads the active style and steps its prose rules aside on its own. Nothing to configure:
The code rules never yield. Output styles govern prose, not the efficiency ladder, the context diet, or the compressor — those keep running. That was the whole point: the old workaround was turning Chisle off, which threw away everything else too.
Reported by @zaphod72 in #15, who also identified exactly why it was hard to fix automatically: the
SessionStarthook payload carries onlysource, so the active style isn't visible there. It turned out to be visible somewhere else —outputStyleis a documented settings key, and/output-stylepersists it to.claude/settings.local.json. Chisle reads it across Claude Code's own settings precedence.Suppress a rule group by hand
The manual half, from @zaphod72's PR #16:
sections.proseorsections.code, independently. Explicit config always beats detection — setprose: trueand you keep Chisle's prose rules even with a style active.The always-on sections (Persistence, Thinking Is Billed Too, Auto-Clarity, When NOT to be lazy, Boundaries) ship regardless of both keys. Auto-Clarity and When NOT to be lazy are safety rules, not style, and the per-turn reinforcement line emits its Boundaries clause outside the code group so that suppressing code rules can't drop a safety rule.
Claude Code and Pi only. The static-rule agents get flat files baked at build time with no runtime config to read.
Fixed: the Pi extension didn't load under OMP at all
Reported by @pyshivam in #14. OMP ships a subset of Pi's
sessionManager, and Chisle calledctx.sessionManager.buildContextEntries()unguarded insidesession_start— so it threw before finishing load, which is why it failed completely rather than partially:Both readers are now optional. A full Pi
sessionManagertakes exactly the path it did before.If you're on OMP, this release is the one that makes Chisle work there. I don't have OMP installed, so it's fixed against the API shape in the traceback rather than a live session — a reply on #14 either way is useful.
Also fixed
Pi's fallback ruleset silently ignored the
sectionskey whenSKILL.mdwas unreadable.Defaults did not change
With no output style and nothing configured, the emitted ruleset is byte-for-byte identical to 3.4.0. Verified by diffing the real emission, not by inspection.
One deliberate removal: documenting the
sectionskey inside the rulesets themselves cost 202 chars (~9%) in each of the five always-on static rule files — to describe a key those agents can't read — and spent tokens in every Claude Code and Pi session on configuration the model can't act on. That documentation lives in the README instead. Chisle should not be the thing bloating your context.Full changelog: https://github.com/JayPokale/Chisle/blob/main/CHANGELOG.md
Release: https://github.com/JayPokale/Chisle/releases/tag/v3.5.0
Questions go in Q&A. If something regressed for you, an issue with
npx chisle --listoutput is the fastest path to a fix.All reactions