Repository navigation
fix: 0.13 backport, name Node.js under an npm install command (MiMo Code, #36761) - #37357
Conversation
The Agent Harness detail for an absent harness showed its install command bare. For OpenCode that is `npm i -g opencode-ai@1`, and on a host without Node.js it fails with "npm: command not found" while the card never says that npm comes with Node.js. Several other harnesses send an `npm i -g` command too. AgentInstallDetail now adds one muted line under an install command that starts with `npm `: the command needs Node.js and npm on the gateway host, with a link to the Node.js download page. A curl installer or an empty command gets no line. The component backs both Settings > Agent Harness and the first-run agent picker, so both get the line. The new key is translated in every shipped catalog. Closes #36377 Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit 5317def)
UX Review (Opus 5.5) — ✅ PASS (a BLOCK with no Trigger and no Outcome does not block)UX-level review of UX-Verdict: PASS cannot evaluate: missing a screenshot of the Node.js hint line under an Evidence gaps
Notes
[UX-REVIEWED] bb63375 Description read[DESCRIPTION-READ] 0e4fbd14e384a9aff271accd3ab177fa7c426fe9dc55c285ba9ba11bd8770acb That sha256 names everything this verdict read: the PR description, plus the 3 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
Design Review (Opus 5.5) — ✅ PASSDesign-level review of Design-Verdict: PASS Nothing blocks: it is a clean cherry-pick that adds one help line under the existing install command, and it is not a new page, panel, control set or default mode. Notes
[DESIGN-REVIEWED] bb63375 Description read[DESCRIPTION-READ] 43fc54d97abd20d1922f11c81d815dc5668e6431ba6cbd2ac012901619ee8f39 That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
First Principles Review (Opus 5.5) — ✅ PASSPremise-level review of First-Principles-Verdict: PASS Nothing blocks: a one-line help hint, backported unchanged from #36761, for a defect the test cites as #36377. What this change shipsInventory (3 items) — 3 justifiedIntent: a 0.13 user installing an npm-based harness (MiMo Code and others) learns that the command needs Node.js before it fails with "npm: command not found". FIX (backport).
[FIRST-PRINCIPLES-REVIEWED] bb63375 Description read[DESCRIPTION-READ] 71b28fbb4818df2dee90c28c424419e645b03f3197b1a3cbbb1d0273a8f2394e That sha256 names the PR description this verdict read. Recompute it with |
Opus 5.5 Review — ✅ no blocking findingsReviewed Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
GPT 6.1 Review — ✅ no blocking findingsGPT 6.1 completed its review of This comment is updated in place on each push. Review detailsNo findings. False positive or not applicable? A repository writer can comment: |
Problem / Motivation
Goal: Ship the MiMo Code harness fixes that merged on main after the 0.13 cut in 0.13.
release/0.13.0already carries the MiMo Code harness itself (#24732, #36290). Since the cut (a29fcc3c2e6b), one user-facing fix on main touches it: #36761. MiMo Code installs through npm, and the Agent Harness card showed thenpm installcommand without saying it needs Node.js and npm.One commit, made with
git cherry-pick -xontorelease/0.13.0head1fe3510b2fa2. It applied with no conflict.5317defe6456npm ...install command that names Node.js and links its download page, so a MiMo Code (or other npm-installed harness) user knows what to install first. curl installers get no line.Why it matters
A user without Node.js who copies the shown command gets
npm: command not foundand no hint why.Not a goal
What changed (motivation → approach → change)
Cherry-pick only. No hunk was hand-resolved.
Backwards compatibility
Compatible. One added line of help text on the Agent Harness card; no key, path or record removed.
Tests
Test changes come from the pick (
website/src/test/AgentBackendTab.test.tsx).On this head:
tsc -p tsconfig.app.jsonclean,AgentBackendTab.test.tsxpasses,scripts/check-i18n-keys.mjsOK. The pick touches no Python.It also applies cleanly next to the open batch 1 part 2 (#37355): part 2, then this pick, then batch 1 part 3 all cherry-pick with no conflict.
Manual verification
N/A. Unit coverage above; the same change is on main.
Screenshots / video
Why no screenshot: a cherry-pick of #36761, which passed Design and UX review on main with its own evidence.
Related Issues
Backport of #36761.
Sibling sweep
Siblings: none -- the backport touches the same sites #36761 changed on main
Pattern harvest
Not generalizable: backport of an already-reviewed fix (#36761)
Checklist
feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...)Contribution License Agreement
Contributions are accepted under the project's Apache-2.0 license.