Fix mkcert -install error in pi-for-excel-proxy CLI
Session from pi-for-excel-sessions on Hugging Face by thomasmustier · MIT · condensed by Coders Talk
Click a segment to jump to that moment
27msession
2interventions
GOAL
Fix a broken npx pi-for-excel-proxy install flow that failed with an mkcert 'unknown option -install' error, then ship a corrected published package.
- +0Prompt · +0npx pi-for-excel-proxy fails with 'unknown option -install' error during cert generation
- +2mIntervention · +2mDeveloper rejected generic troubleshooting/workaround suggestions and asked the agent to actually inspect the repo and fix the real bugWhy: I didn't want workaround install instructions, I wanted the actual bug in our code fixed.
- +2mAgent did · +2mAgent searched the repo, found pkg/proxy/cli.mjs and identified the mkcert -install call as the likely broken path in the published npm package
- +3mIntervention · +3mDeveloper told the agent it had full local git/gh access and to just implement the fix, open a PR, and merge itself rather than just describing stepsWhy: I gave it explicit permission and told it to actually do the work end-to-end instead of just describing commands for me to run.
- +3mAgent did · +3mAgent edited pkg/proxy/cli.mjs to add a fallback for mkcert install variants, bumped version, committed, pushed branch fix/proxy-mkcert-install, and opened PR #331
- +12mFail · +12mCodex PR review flagged that the 'mkcert install' fallback (without dash) is not equivalent to 'mkcert -install' — it can be misread as a hostname arg, silently masking real CA trust-store failures
- +12mAgent did · +12mAgent removed the unsafe fallback, added mkcert compatibility probing via -CAROOT and explicit Homebrew path preference, tested with fake mkcert binaries simulating failure modes, replied to the review comment, waited for CI, and merged PR #331
- +25mAgent did · +25mAgent published the fixed package to npm as [email protected] and fixed the dist-tags so 'latest' pointed to the new version instead of the old broken 0.2.0-pre
- +27mOutcome · +27mPR #331 merged fixing the mkcert -install crash; [email protected] published to npm with corrected dist-tags
VERDICT
Next time I'd start by telling the agent to inspect the actual repo and reproduce the bug immediately, instead of letting it spend a few turns suggesting generic workarounds like 'use a different npx version' or 'run npm run dev instead'. The correction that actually mattered was catching that its 'mkcert install' fallback wasn't equivalent to 'mkcert -install' — that review comment stopped a fix that would have silently masked real CA trust-store failures from shipping.