SlopCop

Changelog

What changed in SlopCop’s checks, the slopcop CLI and the web app, newest first. It is also published as JSON at /changelog.json.

November 4, 2026 · v0.1.63

Check pull requests on GitHub
Turn on Check pull requests in a GitHub repository’s settings, and each push to a pull request gets a SlopCop check with every new finding annotated on its line. Make it a required check to keep a pull request with new findings from merging.
Connect an agent over MCP from Agent setup
Agent setup now has an Over MCP section: pick Claude Code, Codex, or Lovable or Bolt, make an agent token, and copy the connection with the token already in it.
Wait for a check by its id
Every check answer now carries a checkId. While a check runs, the slopcop CLI and the MCP check tool wait for it by that id instead of sending the whole change again.
Erase your account on request
You can ask us to erase your account through Talk to us or by email. We delete your sign-in details, name and email address, your personal workspace with its checks and findings, and remove you from team workspaces, which keep their data. The product analytics recorded about you are deleted too.
Check changes deleted after use
The changes a check sends, unpushed code included, are now deleted within two hours of starting the check, once it has finished. The check’s answer and findings stay.
Old checks deleted after 400 days
A check, with its answer and findings, is now deleted 400 days after it ran, a little longer than the year your dashboard shows. Records of the emails we send go after 90 days, and of messages you send us after 30.
SlopCop over MCP
Coding agents that can’t run the slopcop CLI can call the check and ignore tools from SlopCop’s remote MCP server, signed in with an API token. An agent that can’t produce a diff, such as one without git, can send the changed files’ contents instead.
MCP checks without a commit
Agents without git can leave the base commit out of an MCP check. SlopCop checks the change against the head of the repository’s default branch and says which commit it used; if the change doesn’t apply there, it asks you to push or sync the project and try again.
Agent tokens in workspace settings
Make a named token in a workspace’s settings for an agent that can’t run slopcop login, such as an app builder calling SlopCop over MCP. It checks as you in that workspace only; the list shows who made each one and when it was last used, and revoking one stops it at once.
Say when a check adds a repository
A check’s answer now says when it added the repository to your workspace, so you know which workspace it joined.
Clearer incomplete checks
When a rule can’t run on a change, the check names why instead of reporting an unclassified failure. It still never reports clean.
Changelog by release
The changelog lists each release with its version, says where an analyzer update changes findings, pages through older releases and is published as JSON at /changelog.json.
Replies reach our support team
Reply to a workspace invitation or an account security notice and it reaches our support team. The privacy policy now gives our support address for privacy questions and erasure requests.

November 3, 2026 · v0.1.62

Open a day’s findings
Select a day in Findings by day on the Dashboard to open that day’s findings.
Documentation from the app
The docs site is linked from the workspace sidebar and the site footer.

November 2, 2026 · v0.1.61

Severity on Dashboard and Checks
The Dashboard and Checks pages show the severity of the findings you kept.
Link a device in one click
The approval link slopcop login opens carries its code, so there is nothing to type.
Faster checks
Your repository’s own rules now run in the same analyzer process as the built-in rules, instead of in processes of their own.
Analyzer update
Checks run Bifrost 0.15.0 with public rules 0.9.0 and rule packs 0.8.0.
  • C#: new quality rules for lock statements, self-assignment, nested and misleadingly indented if statements, and passwords in configuration files.
  • C#: new security rules for XML documents that resolve external URLs and signed XML that trusts an embedded key.
  • C#: corrected rules for recursive Equals calls, rethrown exceptions, garbage-collector calls and useless if statements, so their findings may change.

October 30, 2026 · v0.1.58

Dashboard by repository
The Dashboard shows the week’s figures, filters by repository and breaks figures down in a by-repository table.
Repository overview
Each repository has an overview page with its checks and when it was last checked, and the Repositories list shows each one’s figures. The sidebar sorts repositories by their last check.
More ways to install
The Agent setup page offers the shell installer and uv.
Scan reports retired
Checks replace the scan-era report pages, PDF reports, GitHub issue filing and new-finding emails, which have been removed.
Analyzer update
Checks run Bifrost 0.14.3 with public rules 0.7.0 and rule packs 0.7.0.
  • Built-in rules that the previous analyzer skipped without saying so run again, so checks may report findings they missed before.
  • More built-in rules reach a definite result instead of an inconclusive one.

October 29, 2026 · v0.1.55

Know when to update the CLI
The slopcop CLI hears about the newest release, and a release older than the minimum the service supports is told how to update instead of running.
Choose a check’s workspace
A check can name the workspace it belongs to.
Findings by model
The Checks page shows findings by the model that wrote the change, and the share of checks with a finding. Its rules table sorts, searches and pages.
Dashboard from the site
When you’re signed in, the site header and the landing page link straight to your Dashboard.
Community support
Get help from the SlopCop community on Discord, linked across the app.
Security hardening
We hardened repository checkout, webhook handling and the storage of connection tokens.

October 28, 2026 · v0.1.52

Workspace Home
A workspace opens on Home, with a contribution graph of the findings you didn’t ignore.
Repositories join through checks
A repository joins a workspace with its first slopcop check, and Repositories names any connection you need to reconnect.
Agent and model on each check
A check records the coding agent and model that made the change.
Your rules add to the built-ins
A check runs your repository’s rule files on top of the built-in rules, never instead of them.
Inconclusive never blocks clean
An inconclusive rule, one the analyzer couldn’t fully prove either way, no longer stops a clean result. Rules that time out or fail still make the check incomplete.
Archive a team workspace
A team workspace’s owner can archive it and restore it later.
SlopCop in Claude Code and Codex
A public docs page explains how SlopCop fits into Claude Code and Codex.

October 27, 2026 · v0.1.47

Checks, not scans
SlopCop is now built around checks: a Checks page lists every check your agents ran, and repository scans are gone from the app.
Ignore a finding
Your coding agent can ignore a false positive with slopcop ignore, and later checks leave that finding out.
GitLab in the CLI
Sign in to the CLI with GitLab and check gitlab.com projects.

October 26, 2026 · v0.1.46

Check only what changed
A check analyzes only the files a change writes and reports findings on the lines it added or touched.
Passkey sign-in
Sign-in no longer leads with a passkey your browser refuses without asking.

Set it up with us.

Leave your email and we’ll arrange a call about running SlopCop in your team’s coding agents and CI, or anything else you’d like to know.

We’ll use your email to respond.