You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
describe constant and show constants print a stored default value, which can be a credential #1524
describe constant and show constants print the stored default value, which can be a credential. In agent-driven sessions this lands the secret in the transcript. Security-flavoured. Existing mitigation: mxcli constant set (v0.25) keeps secrets out of the model. #801 (closed) is unrelated.
Summary:
The describe constant and show constants commands expose constant default values (including possible secrets) in the CLI output, which could be captured in agent‑driven session transcripts.
Checklist (bug report)
Required info
Present?
Details
mxcli version
✅
v0.26.0 (tested)
Mendix version
✅
11.15.0
Scenario (what was done)
✅
Ran mxcli -p app.mpr -c "describe constant M.ApiPassword" and show constants in M
Expected output
✅
Secrets should be masked; a --reveal flag to show them
Experienced output
✅
Literal default value is printed (no masking)
AI bug report (session log or mxcli diag --bundle)
❌
Not provided
Missing information:
To help us investigate, could you please provide the session log or the output of mxcli diag --bundle for the commands you ran? This will give us the exact context needed to reproduce and fix the issue.
Activity
github-actions commentedon Oct 16, 2026
Issue Triage
Summary:
The
describe constantandshow constantscommands expose constant default values (including possible secrets) in the CLI output, which could be captured in agent‑driven session transcripts.Checklist (bug report)
mxcli -p app.mpr -c "describe constant M.ApiPassword"andshow constants in M--revealflag to show themmxcli diag --bundle)Missing information:
To help us investigate, could you please provide the session log or the output of
mxcli diag --bundlefor the commands you ran? This will give us the exact context needed to reproduce and fix the issue.Thank you for reporting this!
Automated triage via OpenRouter — workflow source