aislop v0.4.0. Agent Handoff, Smarter Fix, Better Scoring

What is new in v0.4.0? Three things worth opening the changelog for. aislop fix can now hand remaining issues to any of 14 coding agents with one flag. The fix pipeline stopped running fixers when nothing needed fixing, so clean code stays clean. And formatting issues are warnings now, not errors, which means a stray tab no longer drops your score from 100 to 94.

Here is the full picture, with the upgrade command at the bottom.

Hand off to any agent in one flag

When aislop fix resolves what it can automatically, you are usually left with issues that need human (or agent) judgment. Complex refactors. Architectural decisions. Security fixes that need context. v0.4.0 generates a structured prompt with every remaining issue, the affected files, and suggested fixes, then opens your preferred coding agent.

14 agents supported out of the box: Claude Code, Codex CLI, Cursor, Windsurf, Gemini CLI, Amp, VS Code Copilot, Aider, Goose, OpenCode, Warp, Kimi Code, Antigravity, and Deep Agents. If your agent is not in the list, --prompt prints the context so you can paste it anywhere. The prompt carries the scan score, every diagnostic with file path and line number, and a prioritized fix list. The agent has everything it needs without asking follow up questions.

Fix that doesn't touch clean code

In previous versions, aislop fix ran every fixer unconditionally. Even if your code was already clean, Biome would reformat files and produce noisy diffs like "40 insertions, 40 deletions" for what was just re-indentation. v0.4.0 scans first, then only runs fixers for engines that actually found issues. If formatting reports zero issues, the formatter does not run. If linting is clean, the lint fixer is skipped.

• + No phantom diffs. Clean code stays clean after fix.
• + Faster runs. Skips unnecessary tool invocations.
• + Trustworthy output. "0 resolved" means 0 files changed. Always.

The output is cleaner too. When everything passes, the result box shows your score and stops. No more "Next steps: 1. All clear!" If it is clear, we just say nothing.

Formatting issues are warnings, not errors

A tab being two spaces instead of four should not block your PR. But that is exactly what happened. Biome reports formatting issues as error severity and aislop was passing that through. Your score dropped from 100 to 94 because of indentation.

v0.4.0 downgrades all formatting issues to warning. This matches every other format engine in aislop (gofmt, ruff, rubocop, cargo fmt) which already used warning severity. The principle: auto fixable style issues are warnings. Real bugs are errors. Your scores will be more accurate. A project with perfect logic but messy tabs gets 100, not 94.

Everything else

• + Diagnostic deduplication. No more duplicate issue reports from overlapping engines.
• + Unused file removal in aislop fix.
• + Directory existence validation in scan.
• ~ Respect biome.json lineWidth config when scanning and fixing.
• ~ Fallback to npm audit when the pnpm audit endpoint is retired.
• ~ Graceful config loading errors.
• ~ CI upgraded to Node 22/24, pnpm/action-setup v5.

Upgrade

Or if you have it installed already:

Full changelog on GitHub.

Try it on your repo

Run it. You will see the number. Star the AI Slop CLI on GitHub if you want the next release in your feed.