miqdadbadjuber/anti-slop v3.2.22

v3.2.22: name all seven plugin doors

on GitHub

The installer could only see four of the seven plugin doors, so a plugin copy it could not see was never named. A Kimi Code, Cline, or Oh My Pi install keeps its own copy of antislop, and --update cannot reach it. The fixed paths only covered Claude Code, Antigravity, Codex, and Cursor, so everyone else finished an update believing that was all of it.

Three doors the probe could not see

The installer now probes all seven, reading the location each vendor actually uses:

• Kimi Code: $KIMI_CODE_HOME/plugins/managed/, defaulting to ~/.kimi-code/plugins/managed/
• Cline: ~/.cline/plugins/_installed/, where each install sits under its source and a hash
• Oh My Pi: ~/.omp/plugins/cache/plugins/, with $XDG_DATA_HOME/omp searched as well

The notice after an install now prints the right update command for each door it finds, so a plugin copy is updated through the agent that owns it rather than silently left behind.

A miss still stays silent by design. A door that moves its files stops being named instead of failing the install, which is why the probe reads only and never throws.

What is verified, and what is not

The four existing probes were re-checked against real installs on this machine: Claude Code, Codex, and Antigravity are all detected, and the first two report a version. Cursor is a documented path that had no install to read.

The three new probes follow each vendor's own layout and are tested against it, not against a live Kimi Code, Cline, or Oh My Pi install. That distinction is deliberate: a wrong path costs a missing line in a notice, never a broken install.

The Cline removal step in the guide also changed. Cline's documentation page lists only cline plugin install, but the CLI ships cline plugin uninstall as well, so the guide now gives that command and keeps the folder deletion as the fallback for an older CLI.

Also in this release:

• CI runs on macOS as well as Linux and Windows, so a report from a Mac can be split into what the installer got wrong and what the agent's own configuration explains.
• A smoke check asserts all seven doors are probed, so a door dropped from the list fails a test instead of disappearing quietly.
• Every version-bearing file moved to 3.2.22 together, which includes the install sample in the guide and the contributors image in the README.

Updating is unchanged:

npx antislop-ai --update

A plugin keeps its own copy, so update it through the agent that installed it. Skills load when a session starts, so start a new one afterwards. Full detail is in the ROADMAP.