DevOps / SRE / Platform · 28.08.2026, 18:48 UTC
LM Studio built a judge for AI commands. Then the judge started agreeing with the defendant.
| Schweregrad | info |
|---|---|
| Kategorie | DevOps / SRE / Platform |
| Quelle | The New Stack ↗ |
| Veröffentlicht | 28.08.2026 UTC |
Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.
A command as ordinary as git diff can become a problem for an AI coding agent once a variable gets involved.
Take git diff $base. If $base contains a commit hash, the command behaves as expected. But if it resolves to --output=/some/file, Git can write the result to the filesystem. LM Studio built Auto Review to catch cases like this before Bionic runs the command, turning to another language model only when it can’t determine whether it’s safe.
In a blog post published Thursday, LM Studio said this first layer cleared as many as 82% of Bionic’s commands without another model call, although the author described the figure as anecdotal rather than a benchmark.
Bionic does this by turning shell commands into abstract syntax trees (ASTs), following variables and nested commands to see what they could affect. LM Studio has built 11,651 test cases to catch the many ways that analysis can go wrong.
A command as ordinary as git diff can become a problem for an AI coding agent once a variable gets involved.
Parsing structure, not strings
Searching for dangerous strings only gets you so far because shell commands can change depending on the variables, redirects and other commands inside them.
Bionic’s Shell Judge gets around that by looking at the structure of the command instead. It uses the mvdan/sh parser for Bash, Zsh and SH, while PowerShell uses its own AST support. The Judge then works out what LM Studio calls the command’s “capabilities,” essentially what the command could read or change.
It can also follow a value from one command to the next. If an agent uses git …