Package and executable identity drift
Headroom CLI MCP server headroom package
An MCP host cannot launch Headroom even though the command works in a shell or the package appears installed.
Agent Quick Fix
The local repository can expose the failure, but the decisive repair depends on the current host, package, runtime, or API contract.
Product: Headroom
Current-contract area: Headroom CLI MCP server headroom package
Likely root cause: An MCP host cannot launch Headroom even though the command works in a shell or the package appears installed.
Repair direction: Use the source trail below to align the local install, host, API, or runtime configuration with the current external contract.
Validation Status
Codex searched organically in the validation run. No no-web counterfactual is attached to this page yet.
Symptom
An MCP host cannot launch Headroom even though the command works in a shell or the package appears installed.
Why This Happens
The local repository can expose the failure, but the decisive repair depends on the current host, package, runtime, or API contract.
Verification
Use the source trail below to align the local install, host, API, or runtime configuration with the current external contract.
Common Wrong Fixes
- Changing local code without checking the current external contract.
- Retrying the same install, build, or API call with no version/source change.
- Applying a broad unsafe bypass when a narrow compatibility fix is available.
Codex Search Keywords
These are the search terms observed in a neutral Codex validation run for this failure shape.
Headroom CLI MCP server headroom package
headroom-ai package MCP command headroom
uv tool headroom MCP command absolute path
Source Trail
GitHub source file/reference: