coldpass

WilliamSmithEdward/xlide_vscode

GitHub ↗ · How this check works

Per-setup public labels: Linux / Haiku: Works

Static status badge · SVG · read-only JSON. Embed with ![Coldpass status](https://coldpass.dev/badge/WilliamSmithEdward--xlide_vscode.svg).

agentic-aiagentic-codingai-toolsexcelvbavba-excel

Works

Only older checks are saved; no current product test.

Answers apply to each recorded setup, revision and operation. Earlier observations remain in Run details.

Tested on Linux
PlatformHaikuLuna
Linuxyes

Linux / Haiku 5.5: yes · Oct 17, 2026 · a585d753df19 · claude-code / 2.1.300 (Claude Code)
Recorded operation: npm run compile

Needs keys or browser
None seen
Setup time
5 min 20 s to install, 15 s to first use
Issue
none found in recorded check

Safety: no observations were recorded for the selected revision. Functional results do not establish a safety result.

Repair history and test corrections
Run details

Haiku 5.5

Native agent · Checked operation passed

Checked operation npm run compile

Agent-reported scope: Developer setup from README 'For Developers And Contributors': npm install, then npm run compile (type-check plus esbuild bundle of the VS Code extension). Both succeeded and produced out/extension.js and out/web/extension.js.

Run details
run
WilliamSmithEdward--xlide_vscode-claude-haiku-5-5-1792233888895456918
date
Oct 17, 2026
time to working
377.5s
product hosting / execution
Local command in the guest
recorded operation scope
product operation
model
claude-haiku-5-5
agent / version
claude-code / 2.1.300 (Claude Code)
platform
linux
reported cost
$0.007225
Recorded source
https://github.com/WilliamSmithEdward/xlide_vscode
Tool transport
mcp-assigned-vm
Test version
readme-520bfd15730ba11f12f732859d1d8be557b2f38c2b58468f19f590c551dabe62
revision
a585d753df19e6df4ee0032d53aa8c4b620c2578
Whose fault: not assigned · resolved

Agent-reported additional finding (agent-reported): Node 18 is older than the lockfile engines (vite 8 and vitest 4 want Node >=20.19 or >=22.12). The build works anyway; installing Node 20.19+ or 22 would remove the EBADENGINE warnings. The transient registry 500 is resolved by retrying npm install.

What the agent did

Developer setup from README 'For Developers And Contributors': npm install, then npm run compile (type-check plus esbuild bundle of the VS Code extension). Both succeeded and produced out/extension.js and out/web/extension.js.

apt-get install -y nodejs npm (Node v18.19.1, npm 9.2.0)
npm install (first attempt: registry 500 on tunnel-0.0.6.tgz; second attempt: exit 0, 402 packages)
npm run compile (exit 0)

run JSON · checker evidence · agent report + check · transcript excerpt · error excerpt

No product verdict. Run record.