Hypha tested by Argusic Runner
Attempt 1 of 3 · Runs · Argusic Score 100.0 of 100
all runs of Hyphaagent-frameworkagent-harnessagent-memoryagent-runtimeai-agentscache
Session recording
Download the original recording · fingerprint a662a0f725baea1e...
What the test found
Hypha builds and runs: the API server serves 200 on /api/v1/status/page, /api/v1/status, /api/v1/openapi.json and completes governed tool executions with verified hashes, and the unit (305), package (2420), integration (44), and native production-topology acceptance (6) tests all pass against locally stood-up MongoDB 8.0.4 and Redis 7.4.2.
Real local MongoDB 8.0.4 + Redis 7.4.2 were stood up (binaries downloaded to $HOME/tools, no system installs). npm ci/879 packages ok; npm run build ok. unit 57S/305T, packages 284F/2420T, integration 4S/44T, memory-native acceptance 6/6. Server stays up on :3000. The memory-external acceptance tier needs third-party managed provider tokens (Mem0 platform/Vertex) and is skipped by default; /usage and /tool-invocations top-level routes return 404 (only /tools/execute exists). /ready 503 solely because no LLM provider API key is configured.
Argusic installed Hypha in 23 minutes and launched it; verification reached Verified running for real. 4 of 4 recorded errors were worked through (see the timeline below).
This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.
Error and fix timeline
No errors were recorded for this run.