You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most "Chisle isn't doing anything" reports come down to one of four things. Work
through these before opening a thread - and if none of it explains your case,
reply here with the output from step 1 and we'll dig in.
1. Is it installed, and for which agent?
npx chisle --list
✓ Claude Code
· Pi
✓ Codex CLI
✓ OpenCode
· Cursor (project-scoped)
✓ means detected, · means not found. Chisle only installs for ✓ agents.
If your agent shows ·, that is your answer - Chisle never touched it. Detection
is by binary on PATH or config directory, so an agent installed somewhere
unusual can read as absent. Force it:
npx chisle --only opencode --force
2. Project-scoped agents install per repo, not once
Cursor, Windsurf, Cline, Kiro and Copilot get a rule file inside the current
directory - .cursor/rules/chisle.mdc, .clinerules/chisle.md, and so on.
That is how those agents load rules; there is no global install.
So if you ran npx chisle in ~ and then opened a different project, that
project has no rule file. Run it again inside each repo:
cd~/code/my-project
npx chisle --only cursor
The global agents (Claude Code, Pi, Gemini, Codex, OpenCode, Hermes) install
once and apply everywhere.
3. Know which axis you expected
Chisle has two independent halves, and not every agent gets both:
Output axis - the ruleset that makes the model write less. Every agent gets this.
Input axis - tool-output compression, which shrinks what the model reads. Only some agents.
If you installed for Cursor and expected elided bash output, that is expected
behaviour, not a bug - Cursor gets the ruleset only.
For agents without a toggle the ruleset is always on once installed. There is
no /chisle off there; remove it with npx chisle -u --only <agent>.
4. Is compression actually running?
npx chisle --stats
saved: 88,967 chars (~22,241 tokens)
outputs: 18 compressed, 4,943 chars each on average
Zeros mean the hook has not fired yet. Common reasons:
Nothing was big enough. Outputs at or under ~8,000 chars pass through
untouched by design. Only ~4% of real tool results clear that bar.
CHISLE_COMPRESS=0 is set. That is the global kill switch. Also check CHISLE_DEFAULT_MODE=off.
The tool is excluded on purpose.Read/Edit/Write output is not
compressed by default on any agent. Their exact text feeds later exact-match
edits, and eliding it would make the model edit text it never saw.
On OpenCode this is a hard block. On the other agents it is a default:
setting CHISLE_COMPRESS_TOOLS=Read,... explicitly will re-enable it, and you
almost certainly do not want that - it is the one setting that can make the
model corrupt an edit.
You restarted? Hooks and plugins load at agent startup.
On old versions, "installed" could be a lie
Before 3.4.0, a failed install could report success: if the target CLI was
missing from PATH, npx chisle --only gemini printed installed: gemini,
installed nothing, and still exited 0. It affected the agents installed by
shelling out to their own CLI - Claude Code, Pi and Gemini.
Fixed in 3.4.0. If you are on anything older, upgrade before debugging anything
else:
npx chisle@latest --update
Verify by hand
Agent
Check
Claude Code
In a session: /chisle off, then /chisle. Status badge appears.
Pi
Footer shows [CHISLE]. /chisle off clears it.
OpenCode
~/.config/opencode/AGENTS.md has the fenced block; ~/.config/opencode/plugins/chisle.js exists.
Codex
~/.codex/AGENTS.md has the fenced block.
Hermes
~/.hermes/skills/chisle/SKILL.md exists.
Cursor / Windsurf / Cline / Kiro / Copilot
The rule file exists in the project directory you ran it from.
Preview any install without touching disk:
npx chisle --dry-run
Still stuck? Reply with this
Four things, and the answer is usually immediate:
Output of npx chisle --list
Your agent and its version
OS and node --version (Chisle needs Node ≥ 18)
Which axis you expected - shorter answers, or elided tool output
If the install itself is the problem, add npx chisle --dry-run output too.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Most "Chisle isn't doing anything" reports come down to one of four things. Work
through these before opening a thread - and if none of it explains your case,
reply here with the output from step 1 and we'll dig in.
1. Is it installed, and for which agent?
✓means detected,·means not found. Chisle only installs for✓agents.If your agent shows
·, that is your answer - Chisle never touched it. Detectionis by binary on
PATHor config directory, so an agent installed somewhereunusual can read as absent. Force it:
2. Project-scoped agents install per repo, not once
Cursor, Windsurf, Cline, Kiro and Copilot get a rule file inside the current
directory -
.cursor/rules/chisle.mdc,.clinerules/chisle.md, and so on.That is how those agents load rules; there is no global install.
So if you ran
npx chislein~and then opened a different project, thatproject has no rule file. Run it again inside each repo:
The global agents (Claude Code, Pi, Gemini, Codex, OpenCode, Hermes) install
once and apply everywhere.
3. Know which axis you expected
Chisle has two independent halves, and not every agent gets both:
/chisletoggleIf you installed for Cursor and expected elided
bashoutput, that is expectedbehaviour, not a bug - Cursor gets the ruleset only.
For agents without a toggle the ruleset is always on once installed. There is
no
/chisle offthere; remove it withnpx chisle -u --only <agent>.4. Is compression actually running?
Zeros mean the hook has not fired yet. Common reasons:
untouched by design. Only ~4% of real tool results clear that bar.
CHISLE_COMPRESS=0is set. That is the global kill switch. Also checkCHISLE_DEFAULT_MODE=off.Read/Edit/Writeoutput is notcompressed by default on any agent. Their exact text feeds later exact-match
edits, and eliding it would make the model edit text it never saw.
On OpenCode this is a hard block. On the other agents it is a default:
setting
CHISLE_COMPRESS_TOOLS=Read,...explicitly will re-enable it, and youalmost certainly do not want that - it is the one setting that can make the
model corrupt an edit.
On old versions, "installed" could be a lie
Before 3.4.0, a failed install could report success: if the target CLI was
missing from
PATH,npx chisle --only geminiprintedinstalled: gemini,installed nothing, and still exited 0. It affected the agents installed by
shelling out to their own CLI - Claude Code, Pi and Gemini.
Fixed in 3.4.0. If you are on anything older, upgrade before debugging anything
else:
Verify by hand
/chisle off, then/chisle. Status badge appears.[CHISLE]./chisle offclears it.~/.config/opencode/AGENTS.mdhas the fenced block;~/.config/opencode/plugins/chisle.jsexists.~/.codex/AGENTS.mdhas the fenced block.~/.hermes/skills/chisle/SKILL.mdexists.Preview any install without touching disk:
Still stuck? Reply with this
Four things, and the answer is usually immediate:
npx chisle --listnode --version(Chisle needs Node ≥ 18)If the install itself is the problem, add
npx chisle --dry-runoutput too.All reactions