Changelog, page 2

November 9, 2026 · v0.1.67

MCP checks fail on any new finding: The MCP check tool now fails a check on any new finding unless you set failOn, as the slopcop CLI does, so the same change gets the same answer from either.
Inconclusive checks say why: Each inconclusive check in a check answer now carries the analyzer’s reason codes. The MCP check tool lists them in its text and says plainly that inconclusive checks never block a clean result and need no fix or retry.
Clearer MCP connector errors: When the SlopCop MCP server turns a request away, it now says what to fix: an invalid or revoked token points you to making a new agent token, an unsupported protocol version lists the versions it speaks, and a tool argument of the wrong type names the field.
Check a pushed commit over MCP: The MCP check tool takes headCommit, a pushed commit that holds your change, instead of a diff, so an agent checks a large change without retyping it. It works for GitHub and GitLab repositories. Without a base commit, SlopCop checks the commit against where it branched from your default branch.
Fewer incomplete checks: A check no longer comes back incomplete because a default policy for a language your change doesn’t contain could not run, so a change in one language can come back clean. A policy you name yourself still makes the check incomplete when it cannot run.
Incomplete checks say why: An unreliable check in a check answer now carries its cause, such as the diagnostic codes or the analyzer stopping early. When one cause left many checks incomplete, the answer reports it once in runFailures with how many checks it affected.

November 6, 2026 · v0.1.66

Updates without interruptions: SlopCop stays available while an update rolls out, and a check that is waiting for its result gets an answer instead of being cut off.

November 6, 2026 · v0.1.65

Analyzer update: Checks run Bifrost 0.15.1 with public rules 0.9.1 and rule packs 0.9.0.
All languages: a finding that covers a whole declaration, such as a class, now keeps its id when the declaration’s body changes. These ids change once with this update, so an ignore recorded for one of them needs recording again.
Go: calls through standard library interfaces, such as closing a network connection, now resolve, so more rules reach a result.
Java, Kotlin, C# and Rust: more precise call and type resolution; some findings may change.
JavaScript and TypeScript: fewer misspelled-identifier findings, reported only when the corrected spelling appears in the same file.

November 5, 2026 · v0.1.64

Connecting GitHub adds your repositories: Connecting GitHub to a workspace now adds every repository the connection can reach, with pull request checks on, and a repository you grant the SlopCop app later joins the workspace by itself. You no longer add them one at a time.
Checks don’t enroll repositories on their own: A check adds a repository to your workspace only when you explicitly confirm it, as slopcop enable does. A check of a repository the workspace hasn’t added now stops before analysis instead of adding it, so an agent or CI job can’t change which repositories your workspace checks by itself.
Repositories page stays lined up: On the Repositories page, each repository’s figures and actions now sit under their own column headings at every width, and a repository’s summary line stays under its name.
Connect Cursor or any MCP client from Agent setup: Over MCP on Agent setup now lists each agent on its own: Claude Code, Codex, Cursor, Lovable, Bolt, and Anything else. Pick one, make an agent token, and copy the connection in the form that agent takes it: a command, a config file entry for Cursor, the URL and token for an app builder’s Connectors form, or the URL and Authorization header for any other remote MCP client.
Pull request checks say how to ignore: A pull request check’s summary now says which workspace ran it and lists each new finding’s id, and each annotation carries the slopcop ignore command for its finding. An ignore applies only in the workspace that ran the check, so the command names it.

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. Repositories reached through a connected GitHub workspace start with checks on; Workspace settings lists every repository with its own toggle and can turn checks on for all of them at once. 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.