Problem
PR #833 was merged while the web provider still masks the managed backend Node-version hint. The package still advertises Node >=22.19, but the managed web backend requires Node 24+.
Current merged path:
src/platforms/web/agent-browser-tool.ts correctly reports Web automation requires Node 24+; current Node is ... when the backend is unavailable on Node 22.
src/platforms/web/agent-browser-provider.ts:204-211 calls mapManagedAgentBrowserError(error), then wraps TOOL_MISSING with the generic Run agent-device web setup hint.
- The shipped route
agent-device --platform web open ... therefore tells Node 22 users to run setup, then setup fails with the Node 24+ requirement.
Expected
The provider/runtime path should preserve the specific unavailable reason from appError.details.hint, especially the Node 24+ requirement, instead of replacing it with generic setup guidance.
Suggested validation
Add provider or runtime coverage for the Node <24 missing-backend case so the CLI/daemon path keeps the actionable hint. A tool-only test is not enough because the provider wrapper currently masks the hint.
Related: #833 review comments called this out before merge.
Problem
PR #833 was merged while the web provider still masks the managed backend Node-version hint. The package still advertises Node
>=22.19, but the managed web backend requires Node 24+.Current merged path:
src/platforms/web/agent-browser-tool.tscorrectly reportsWeb automation requires Node 24+; current Node is ...when the backend is unavailable on Node 22.src/platforms/web/agent-browser-provider.ts:204-211callsmapManagedAgentBrowserError(error), then wrapsTOOL_MISSINGwith the genericRun agent-device web setuphint.agent-device --platform web open ...therefore tells Node 22 users to run setup, then setup fails with the Node 24+ requirement.Expected
The provider/runtime path should preserve the specific unavailable reason from
appError.details.hint, especially the Node 24+ requirement, instead of replacing it with generic setup guidance.Suggested validation
Add provider or runtime coverage for the Node <24 missing-backend case so the CLI/daemon path keeps the actionable hint. A tool-only test is not enough because the provider wrapper currently masks the hint.
Related: #833 review comments called this out before merge.