# Changelog What shipped, newest first. bugstack is in early access and changes most days. This page lists the changes you would notice, including the bugs we fixed. ## October 2026 1 October ### New hero animation on bugstack.ai One real fix from start to finish, then the 158 problems of our latest benchmark run. ## September 2026 30 September ### Python errors are read properly When a Python app reports an error without a name, bugstack now reads the exception type and the stack frames from the traceback. Python’s own library paths are treated as vendor code, so the fixer starts in your code. 29 September ### The fixer checks its work against the rest of your code Two new checks run before a fix is proposed. Does the change still fit the files that use what it changed? Does it leave any caller on the old behaviour? A fix that fails is retried once, then refused. 29 September ### The fixer sees what changed recently For each file it reads, the fixer now also gets the latest commit as a diff. Many crashes are caused by a change made shortly before. 25 September ### Benchmark: 158 planted problems We ran bugstack against 158 defects planted in our own code. Six of seven kinds of problem reached the right action at least 80% of the time, and 45 of 61 crash fixes held. [See the numbers](/#numbers). 25 September ### Render: each workspace is scanned with its own key A second connected Render workspace is now read with its own credentials, and a revoked key is reported. 24 September ### Monorepos: the right lockfile is regenerated When a package inside a monorepo is upgraded, bugstack regenerates the lockfile next to that package. 23 September ### Fixed: vulnerability advisories were being dropped Advisories returned by the vulnerability database were discarded before they were recorded. They are stored and reported again. 21 September ### You are told when bugstack leaves a problem for you When bugstack declines a problem and it stays open, the owner is notified. Notification subscriptions now respect the event type you chose. 12 September ### Twelve fixes merged on our own repository Between 8 and 12 September bugstack opened twelve crash fixes on its own codebase and we merged them, including the one shown on the homepage. 4 September ### Fixed: scheduled scans run on time again A scheduling bug had stopped repository scans from running on their clock. Vulnerable packages are checked every four hours again. 2 September ### Google Analytics removed from the dashboard The dashboard no longer loads any analytics script. 1 September ### Alerts reach a person, by GitHub issue or Slack A problem that needs a person and cannot be fixed automatically now opens a GitHub issue or posts to Slack. 1 September ### A disconnected repository is no longer scanned Disconnecting a repository stops crash intake and every scheduled scan for it. ## August 2026 31 August ### Upgrade pull requests regenerate every lockfile A dependency upgrade now updates every lockfile in the repository. bugstack also stops opening a second upgrade pull request while the first is still open. 31 August ### Your spend limit is the ceiling The monthly limit you set is the most bugstack will spend on work for you. 23 August ### A missing CI run no longer counts as proof Automatic merging needs checks that actually ran. A pull request with no checks waits for a person. 23 August ### Ten findings from an internal audit closed Including a stricter check on who may release the pause switch, and invitations pinned to the organisation that issued them. ## July 2026 31 July ### First fix completed end to end bugstack fixed a failed deploy of its own dashboard. A person only reviewed and merged. 8 July ### First failed-deploy fixes bugstack opened its first pull requests for failed deploys on Render. ## See it on your repository Every early access team is onboarded personally, and every change arrives as a pull request you control. [Request Early Access](/early-access) Personal onboarding · We set it up with you