StayAwakeBot (saw)Catch supply-chain worms before they run. The saw scanner in VS Code, Cursor, Antigravity, Devin Desktop and VSCodium: a verdict for every folder you open, before you trust it.
Supply-chain worms hide where a developer never looks: an editor task that runs when a folder opens, an obfuscated loader in an installed package, a poisoned lockfile, a git hook that runs on checkout. saw hunts them, and this extension runs saw for you. It scans each folder, shows the verdict where you work, and, when you ask, cleans the folder up. FeaturesA verdict for every folderEach workspace folder is scanned when the window opens, and again when something that can run code
changes: a saved file, a checkout or pull, or a change under
Read what each verdict means in saw's documentation. Safe before you trust a folderScanning only reads files, so it runs in Restricted Mode. When saw confirms malware in a folder you have not trusted yet, the extension warns you before you trust it. ChatThe saw sidebar opens on Chat. Each open folder is a card: the verdict, what saw found, and buttons for what you can do. A scan only reads the folder. Fix the checkout removes what saw confirmed and puts the clean-up on a new local branch. It does not rewrite past commits, and it does not push. Amending history is named separately: that act rewrites the commits that still carry the malicious code and force-updates the branches they are on, and the checkout fix does not do it. When a fix is waiting, the card says whether the question is part of the checkout fix or of amending history. The same buttons are used in Decide. This view is part of the extension, so it looks the same in every editor built on VS Code. After saw holds an update, or after several quiet checks, a card under the folders asks for a rating. Share feedback opens it any time. Reports you can readOpen Report opens a folder's scan as a document in an editor tab: the verdict, what to do, and every finding with its remedy and evidence. Fix, Audit and the hook commands open their own reports, which update live as saw works. Reports are kept in the extension's own storage, never in your project. Fix an infected folderFix… runs
When it's done, the folder is scanned again. With a saw that names the clean-up branch, Open Changes shows the whole clean-up as one diff. When saw can ask during a fix, the Decide view offers the choice and a diff opens beside it. Keep is the focused action. Closing the diff does not answer. Stopping the fix does not answer.
Audit this machinesaw: Audit This Machine runs Scan-on-clone hooksThe saw view shows whether saw's scan-on-clone hooks are in place, so every clone, pull and branch switch is scanned. It installs or repairs them in one click. Updates wait for a checkWhen the installed saw can check an incoming update, a pull, fetch, checkout, merge, rebase, or a GitHub command that lands files waits before it changes an open folder. If that saw includes its git and gh stand-in, the editor places it in front of those commands. The editor's integrated terminal is covered, and so is the Git view, except on Windows. Clean and residue are applied. While the check runs, the status bar, the saw view, and Chat say saw is checking the update, and the step saw names when it names one. The folder is unchanged until the check finishes. Suspicious, infected, and a check that could not finish leave the folder as it was, and the saw view says the update was held. The open folder is scanned again after the check finishes. A git command this window did not run can still change the folder first. When saw can say whether it let that tree in, Chat says the change was not held only when saw did not. A check that runs outside this window shows the same checking, applied, or held. When saw can put a folder back, a commit it did not let in is put back by saw and your unsaved work stays. A change to the files on a commit saw already let in is not put back. An agent that asks saw about a folder hears the same checking, held, or not-held state, and is told to wait while a check is running. When you have asked saw to cover your terminals, the editor's terminal uses that and does not
check the same command again. The Git view still checks. A terminal saw does not cover keeps
saw's scan-on-clone check. Turn the editor's check off with Guards for AI agents
Getting started
Requirements
How saw is installedThe extension uses the
Both come from PyPI as ready-built packages only, so no build script runs. No administrator rights
are needed, and nothing is written into the system Python. The status bar shows
If the install fails, one notification says why and what to run, with Retry, Copy Diagnostics and Show Log. To install saw yourself instead, see saw's first scan tutorial. CommandsAll commands are in the Command Palette under saw:.
Settings
These are read from your user settings only. A folder's own Remote windowsThe extension runs on the machine where the files are. A local window is this computer, on Windows, macOS, or Linux. In Remote - SSH, WSL, or a dev container, it finds or installs saw on that remote, scans the remote's files, and Fix… and the hooks act on the remote's git. Audit This Machine audits that machine (the server, the WSL distribution, or the container), not the computer in front of you. Privacy and safety
Read how saw decides what to trust in its trust model and why it fails closed. Troubleshooting
Learn more
Feedback and contributingsaw: Share feedback is on the saw view title and in the Command Palette. Rate opens the review page for the editor you are using. Star opens this repository. Report a problem asks whether it is about the editor or about what saw found, then opens that tracker with the extension version, the saw version, the editor name, and the verdict word filled in. Nothing from the folder is included. Request a feature opens an extension issue the same way. Not now hides the card until the next version, and only after saw has held another update or checked a folder quietly again. A rating or a star means Chat stops asking on its own.
License |


