coldpass

RealDealCPA-VR/Iron-Jarvis

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/RealDealCPA-VR--Iron-Jarvis.svg).

agentic-aiagentscodingcoding-agentlocal-ailocal-first

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 · ba8e64f31733 · claude-code / 2.1.300 (Claude Code)
Recorded operation: /workspace/.venv/bin/ironjarvis demo

Needs keys or browser
None seen
Setup time
4 min 32 s to install
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 /workspace/.venv/bin/ironjarvis demo

Agent-reported scope: Offline end-to-end demo: `uv run ironjarvis demo` (plan -> act -> write_file tool -> workspace artifact), run from the Python daemon install with no keys and no network. Exit code 0; session status completed, write_file tool ok, artifact demo-report v1 generated.

Run details
run
RealDealCPA-VR--Iron-Jarvis-claude-haiku-5-5-1792211612769262566
date
Oct 17, 2026
time to working
1680.4s
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.007801
Recorded source
https://github.com/RealDealCPA-VR/Iron-Jarvis
Tool transport
mcp-assigned-vm
Test version
readme-3691798994c35a4248db43f18225b5f420ad493d7ca35c5ea2e8f1d0d89e7c20
revision
ba8e64f3173339c7e430ed046a3cf03d388f13f7
Whose fault: not assigned · resolved

Additional warning

Step: cd dashboard && pnpm install (README 'From source' section, dashboard step)

npm registry (registry.npmjs.org) returns transient 500/504 errors for package tarballs, so the dashboard dependency install never completes and the Next.js build cannot run.

Agent-reported additional finding (agent-reported): Retry `cd dashboard && pnpm install --frozen-lockfile` later, or configure a working registry mirror/proxy via pnpm config (registry=...) in the guest. Then run `pnpm build`. Re-running the demo does not depend on this step.

What the agent did

Offline end-to-end demo: `uv run ironjarvis demo` (plan -> act -> write_file tool -> workspace artifact), run from the Python daemon install with no keys and no network. Exit code 0; session status completed, write_file tool ok, artifact demo-report v1 generated.

Read README.md (From source section)
Installed uv 0.13.1 via astral.sh install script
uv sync --extra dev (Python 3.12.3) - succeeded
Installed Node v20.20.2 and npm 10.8.2 via NodeSource setup_20.x and apt nodejs; installed pnpm 9.15.9 globally
cd dashboard && pnpm install - failed ERR_PNPM_FETCH_504 (x1), then ERR_PNPM_FETCH_500 on 3 retries and 1 more after 60s wait
cd dashboard && pnpm build - not run successfully (next: not found because install failed)
uv run ironjarvis --help - succeeded
uv run ironjarvis demo - succeeded, exit 0

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

No product verdict. Run record.

No product verdict. Run record.

No product verdict. Run record.