CLAUDE.md and skill files use inconsistent mxcli invocation paths

[oskar5331]

Summary

mxcli init generates a CLAUDE.md that instructs AI agents to always use ./mxcli
(local path), while the skill files in .ai-context/skills/ use bare mxcli (assumes PATH).
This creates conflicting guidance in the same project.

Specific inconsistency

CLAUDE.md (generated, project-level):

The mxcli tool is located in the root folder of this project, not in the system PATH.
Always use the local path: ./mxcli -p ELDYcare.mpr
Do NOT use mxcli directly - it will fail with "command not found".

.ai-context/skills/run-app.md and other skill files (upstream templates):

mxcli docker run -p app.mpr --wait
mxcli docker build -p app.mpr

These assume mxcli is on PATH.

There is also a broken line in run-app.md:

mxcli is local — always use mxcli, not mxcli

(the ./ prefix was stripped, making it nonsensical)

Impact

• AI agents reading both sources get contradictory instructions
• The VSCode MDL extension (mendix.vscode-mdl) uses "mdl.mxcliPath": "mxcli" (bare name), so it requires mxcli to be on PATH — but CLAUDE.md discourages that
• Users who follow CLAUDE.md strictly end up with a broken VSCode MDL language server

Suggested fix

Either:

1. Recommended: Ship a post-init step (mxcli setup mxcli --global or similar) that installs the binary to ~/.local/bin, and update CLAUDE.md to reflect that mxcli is available on PATH — consistent with the skill files and the VSCode extension
2. Update skill files to use ./mxcli to match the CLAUDE.md guidance (less ideal, breaks the VSCode extension assumption)

Environment

• mxcli v0.7.0
• VSCode extension: mendix.vscode-mdl-0.6.0
• Devcontainer / Linux amd64

[github-actions]

Issue Triage

Summary:
The issue reports that mxcli init creates a CLAUDE.md advising users to invoke mxcli via ./mxcli, while the bundled skill files and VSCode extension expect mxcli on the PATH, leading to contradictory guidance.

Checklist for bug report completeness

Required info	Present?	Notes
mxcli version	✅	v0.7.0 given
Mendix version	❌	Not mentioned
Scenario (what the user was trying to do)	⚠️	Implied (using mxcli init and skill files) but not explicitly stated
Expected output	❌	Not described
Experienced output (error/wrong result)	❌	Only described as contradictory guidance; no specific error message
AI bug report (mxcli diag --bundle or session log)	❌	Not provided

Request for additional information
To help us reproduce and fix the inconsistency, could you please add:

1. The Mendix version of the project you’re working with (e.g., 10.6, 9.24).
2. A clear description of what you were trying to accomplish (e.g., running mxcli init then using the skill files).
3. What you expected to happen versus what actually happened (any error messages or incorrect behavior).
4. If possible, the output of mxcli diag --bundle (or at least the relevant session log).

Thanks for bringing this to our attention—once we have those details we’ll be able to address the conflict quickly!

---

Automated triage via OpenRouter — workflow source