@debugai/mcp 2.4.0 → 2.4.1

package/README.md

@@ -133,6 +133,8 @@ call report_outcome so the project's error memory stays accurate.
 
 You do not need this package. The [DebugAI extension](https://marketplace.visualstudio.com/items?itemName=debugai.debugai) registers the MCP server automatically (VS Code 1.101+) and adds one-click fix apply, proactive scan, and codebase indexing on top. It is on [Open VSX](https://open-vsx.org/extension/debugai/debugai) too, for Cursor, Windsurf, and VSCodium.
 
+The two servers are the same protocol surface and are kept in step by a test that reads both copies as text, because a comment saying "keep these in sync" has failed here before. From extension 2.8.1 the bundled server also does local source resolution, which this package has had since 2.2.0. Until then, an agent on the bundled server that pasted a traceback into a workspace nobody had indexed still got "Insufficient context for specific fix" at 20% confidence, which is the exact answer this feature exists to remove.
+
 ## Manual setup
 
 `setup` covers this, and `install --client=<id>` covers the case where a client is installed somewhere unusual. If you would still rather edit the file yourself, the entry is the same everywhere:
@@ -197,6 +199,7 @@ Then run `npx -y @debugai/mcp login` once to store your key. If you would rather
 - Simple errors route to a fast model. Ugly cross-file ones route to a stronger one on paid tiers. The `Model:` badge in each response tells you which one answered.
 - Analyses run on DebugAI's servers. The error text, any snippet you pass, and — since 2.2 — the project source files the stack trace names are sent there, and Claude (Anthropic) does the analysis. The response lists every file that was read. Scope and limits are spelled out under [`debug_error`](#it-reads-the-source-the-trace-names-22). Privacy policy: [debugai.io/privacy](https://debugai.io/privacy?src=npm).
 - Errors are remembered per project so a repeat hit starts from a fix that was already confirmed. The project identity is a hash of your repo root path; the path itself is never sent.
+- The VS Code extension reads the project's `requirements.txt`, `pyproject.toml` and `package.json` and the interpreter the editor has selected, which is what lets it tell "not installed" apart from "installed under a different interpreter". This server sends none of that, so on a missing-module error you get the general answer and the check to run, not a verdict. You have a shell and it does not, so the honest division is that you run the check. Reporting those facts back through this server is planned.
 
 ## Troubleshooting
 
@@ -211,9 +214,36 @@ Run `npx -y @debugai/mcp doctor` first. It checks your Node version, whether a k
 
 **Note on updates**: the analysis runs on DebugAI's servers, so improvements to
 error parsing, retrieval and root-cause quality reach you without upgrading this
-package. Recent server-side work: pytest, unittest, jest, vitest and mocha output
-now yields real file paths, so a failing test gets cross-file context instead of
-none. Client releases are only for things that change on your machine.
+package. Client releases are only for things that change on your machine.
+
+Recent server-side work, all of it live for agents already:
+
+- `ModuleNotFoundError` no longer opens with an install command. A read of every
+  one we had answered found five of eight rejected by the agent that received
+  them, for three different causes needing three different fixes: the package
+  was installed under another interpreter, the name was a local file, or the
+  import line was malformed. Rank 1 is now the check that tells those apart.
+- A Python `SyntaxError` is no longer diagnosed as a JavaScript one, and the
+  framework is read from the error text rather than from what the repository
+  contains.
+- Operating-system errors (`Access is denied.`, `No space left on device`) are
+  recognised as errors. Thirty were probed and twenty-eight had been refused.
+- Credentials in the text you send are replaced before anything is stored or
+  reaches a model.
+- pytest, unittest, jest, vitest and mocha output yields real file paths, so a
+  failing test gets cross-file context instead of none.
+
+**2.4.0**: `report_outcome` gains `unused`. An agent that solved the problem its
+own way had to report `failed`, which marks a fix as tried and beaten when
+nothing of ours was ever run. Both tool surfaces, the npm server and the one
+bundled in the VS Code extension, now take the same fields.
+
+**2.3.0**: agents get the same four memory states the editor panel does.
+`debug_error` had two branches, and a fix that had been tried and kept failing
+read identically to one nobody had tried. To an agent those are the same
+sentence, so the natural next move is to propose the fix that already did not
+work. The four states now match the panel: confirmed and verified, confirmed,
+unproven, and anti-pattern.
 
 **2.2.0**: two things that were advertised but not delivered.
 

package/dist/tools/reportOutcome.js

@@ -58,8 +58,8 @@ export function registerReportOutcome(server, config) {
                 .describe('"worked" = you applied a DebugAI fix and the error stopped. ' +
                 '"failed" = you applied one and it did not help (or made things worse). ' +
                 '"unused" = you did not apply any of them and resolved it another way. ' +
-                'Use "unused" rather than "failed" when nothing of ours was actually run — ' +
-                'they are different facts and reporting the wrong one buries a fix nobody tried.'),
+                'Use "unused" rather than "failed" when nothing of ours was actually run. ' +
+                'They are different facts and reporting the wrong one buries a fix nobody tried.'),
             fixRank: z
                 .number()
                 .int()
@@ -77,7 +77,7 @@ export function registerReportOutcome(server, config) {
                 .max(4000)
                 .optional()
                 .describe('What actually resolved the error, when it was not the fix DebugAI suggested. ' +
-                'Free text. Say what the real cause turned out to be and what you changed — ' +
+                'Free text. Say what the real cause turned out to be and what you changed, ' +
                 'especially if the cause was in a different layer than the answer addressed ' +
                 '(the shell, the runtime version, the environment, a missing package).'),
             toolFeedback: z

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@debugai/mcp",
-  "version": "2.4.0",
+  "version": "2.4.1",
   "mcpName": "io.github.1shizaan/debugai-mcp",
   "description": "DebugAI MCP server. One command sets it up in Claude Desktop, Claude Code, Cursor, Zed, Windsurf, Cline or any MCP client: browser sign-in, no key pasting, no config editing.",
   "license": "MIT",