# Sentinel-IR 0.5.10: we taught our code assistant to say \"I don't know\

> Source: <https://dev.to/jackymencz/sentinel-ir-0510-we-taught-our-code-assistant-to-say-i-dont-know-cj1>
> Published: 2026-11-16 05:07:29+00:00

description: "A 3-minute, no-jargon tour of what's new in Sentinel-IR and Sentinel-IR MCP: fewer fake all-clears, fewer false alarms, and a doorman who stopped ringing the neighbours' bells."

Yesterday was a heavy day here: four technical articles full of logs, Node versions and packet counts. Today is the opposite. Make a coffee. No stack traces were harmed in the making of this post.

When an AI assistant reads your code, it usually swallows whole files and hopes for the best. **Sentinel-IR** reads the code first, *without running it*, and hands the AI a short fact sheet instead: *"this file reads from the disk, this one talks to the internet, this one can start other programs."*

**Sentinel-IR MCP** is the doorman that sits between your AI assistant and your project. The assistant may look inside the folders you allowed and nowhere else.

Version 0.5.10 came out yesterday. Here is what changed, translated into human.

Imagine a tourist who doesn't speak the language but keeps smiling and saying "yes, yes, very good" to everything. Polite, but dangerous.

Older versions did something similar with languages Sentinel can't read yet, like Ruby. A Ruby file was quietly read as if it were JavaScript and came back as *"complete, low risk"*. Now Sentinel answers honestly: *"unknown language, analysis incomplete."* An honest "I don't know" beats a confident "all clear" every time.

A smoke detector that screams every time you make toast doesn't make you safer. It teaches you to ignore it.

One of the warnings was like that. A broken Rust file that only said *"exit the program"* was marked **critical**, the same as code that launches other programs. Now only the code that actually starts other programs gets the red label.

A good hotel receptionist won't tell a stranger whether a guest is staying there. Earlier, if the AI asked for a file outside your project, the answer could be "doesn't exist", which quietly confirms what *does* exist. Now every file outside your folders gets the same reply: **"Access denied."**

On Windows, it also used to ring the neighbour's doorbell before saying no. A path pointing at another computer on the network (`\\server\...`) now gets refused *before* any connection is made. In our Windows test, the refusals sent zero network packets. A regular Windows check of the same address sent 28.

`doctor` is the command that checks your setup. When it couldn't read some editors' settings, it used to guess *"nothing excluded, logging off"*. Now it simply says it can't see them, and it warns you when an old copy of the server is still hiding in your npm cache.

We didn't want *you* to be the beta tester, so AI agents played "ordinary users" on Linux, macOS and Windows with Node 20, 22 and 24, over three rounds. The final exam was real: VS Code with GitHub Copilot on Windows (running 0.5.9, the version right before this one) called all three Sentinel tools. Answers came back in 23–94 ms, and a sneaky request for a Windows system file was refused.

Releases are now built only by GitLab CI with signed provenance on npm. There is no stored publish token left that someone could steal.

`npx -y sentinel-ir-mcp@stable-0.5 setup --client vscode` (or `cursor`, `windsurf`, `claude-desktop`, `claude-code`)
If Sentinel saves you a headache, a ⭐ on [GitHub](https://github.com/jakcmencz/sentinel-ir-mcp) or a [sponsorship](https://github.com/sponsors/jakcmencz) keeps the grumpy test users employed. Companies can write to [sentinel.ir.contact@gmail.com](mailto:sentinel.ir.contact@gmail.com).

Go support is coming next. The doorman is already learning a new language, and this time he will admit when he doesn't understand.

Copyright © 2026 jackymenCZ. All rights reserved. Written for the community.
