claude-code - 💡(How to fix) Fix [Bug] Claude Opus 4.7 repeatedly violates explicit prompt instructions and operational filters in Claude Code sessions [3 comments, 3 participants]

[{"error":"Error: LSP server plugin:mdbase-lsp:markdown failed to start: Executable not found in $PATH: "mdbase-lsp"\n at start (/$bunfs/root/src/entrypoints/cli.js:3164:22360)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-27T03:58:02.703Z"},{"error":"Error: Executable not found in $PATH: "mdbase-lsp"\n at spawn (unknown)\n at spawn (node:child_process:667:35)\n at spawn (node:child_process:14:39)\n at start (/$bunfs/root/src/entrypoints/cli.js:3164:20896)\n at Y (/$bunfs/root/src/entrypoints/cli.js:3164:24879)\n at z (/$bunfs/root/src/entrypoints/cli.js:3164:30119)\n at j (/$bunfs/root/src/entrypoints/cli.js:3164:30504)\n at f (/$bunfs/root/src/entrypoints/cli.js:3164:31063)\n at call (/$bunfs/root/src/entrypoints/cli.js:4850:1388)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-27T03:58:02.703Z"},{"error":"Error: Failed to start LSP server for file /Users/nerym/Dev/forestal-mt-store/docs/blueprint/03-seo-jsonld-and-production.md: Executable not found in $PATH: "mdbase-lsp"\n at z (/$bunfs/root/src/entrypoints/cli.js:3164:30145)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-27T03:58:02.703Z"},{"error":"Error: Executable not found in $PATH: "mdbase-lsp"\n at spawn (unknown)\n at spawn (node:child_process:667:35)\n at spawn (node:child_process:14:39)\n at start (/$bunfs/root/src/entrypoints/cli.js:3164:20896)\n at Y (/$bunfs/root/src/entrypoints/cli.js:3164:24879)\n at z (/$bunfs/root/src/entrypoints/cli.js:3164:30119)\n at j (/$bunfs/root/src/entrypoints/cli.js:3164:30504)\n at f (/$bunfs/root/src/entrypoints/cli.js:3164:31063)\n at call (/$bunfs/root/src/entrypoints/cli.js:4850:1388)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-27T03:58:02.703Z"},{"error":"Error: LSP server plugin:mdbase-lsp:markdown failed to start: Executable not found in $PATH: "mdbase-lsp"\n at start (/$bunfs/root/src/entrypoints/cli.js:3164:22360)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-27T03:58:07.276Z"},{"error":"Error: Executable not found in $PATH: "mdbase-lsp"\n at spawn (unknown)\n at spawn (node:child_process:667:35)\n at spawn (node:child_process:14:39)\n at start (/$bunfs/root/src/entrypoints/cli.js:3164:20896)\n at Y (/$bunfs/root/src/entrypoints/cli.js:3164:24879)\n at z (/$bunfs/root/src/entrypoints/cli.js:3164:30119)\n at j (/$bunfs/root/src/entrypoints/cli.js:3164:30504)\n at f (/$bunfs/root/src/entrypoints/cli.js:3164:31063)\n at call (/$bunfs/root/src/entrypoints/cli.js:4850:1388)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-27T03:58:07.276Z"},{"error":"Error: Failed to start LSP server for file /Users/nerym/Dev/forestal-mt-store/docs/blueprint/03-seo-jsonld-and-production.md: Executable not found in $PATH: "mdbase-lsp"\n at z (/$bunfs/root/src/entrypoints/cli.js:3164:30145)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-27T03:58:07.276Z"},{"error":"Error: Executable not found in $PATH: "mdbase-lsp"\n at spawn (unknown)\n at spawn (node:child_process:667:35)\n at spawn (node:child_process:1…

TL;DR

The most likely fix is to ensure the mdbase-lsp executable is properly installed and included in the system's PATH.

Guidance

1. Verify mdbase-lsp installation: Check if mdbase-lsp is installed and its version is compatible with the current setup.
2. Check PATH environment variable: Ensure the directory containing mdbase-lsp is included in the system's PATH environment variable.
3. Review error logs: Analyze the provided error logs to identify any patterns or additional clues that might point to the root cause of the issue.

Example

No specific code snippet can be provided without more context, but checking the PATH variable can be done using the command echo $PATH in the terminal.

Notes

The issue seems to be related to a missing executable (mdbase-lsp) in the system's PATH. Without more information about the installation process or the environment, it's challenging to provide a more detailed solution.

Recommendation

Apply a workaround by manually adding the directory containing mdbase-lsp to the PATH variable, if it exists, to test if this resolves the issue.