daydreams

Daydreams is a set of tools for building agents for commerce

Runssource: GitHubhomepageTypeScriptMITcommit e3231c3de108

TypeScript, MIT licensed. The project labels itself: 8004, agent framework, agent frameworks, agents, ai, cdp, erc8004 and gaming.

daydreams runs. An Argusic agent installed it in 6 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

pnpm install succeeds, all 13 packages build, 157/157 core tests pass, core module imports cleanly with 20+ exported symbols

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.01 (measured)
recorded runs
1
last tested
stars
628
forks
141
open issues
33
watchers
17
size
59 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing daydreams, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • pnpm install ERR_PNPM_IGNORED_BUILDS for @coinbase/x402, bigint-buffer, keccak2 minutes
  • Missing dist/ for discord, hyperliquid, mongo packages2 minutes
  • pnpm not installed1 minute
Install time
6 minutes
Cold machine to finish
6 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
vitest run in packages/core: 33 test files, 157 passed, 1 todo; all 13 packages built successfully; core module loads via dynamic import()
Model tokens used
61,799
Exact commit tested
e3231c3de108
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 6, "errors": [{"msg": "pnp…
exec
/bin/sh -lc "echo 'ARGUSIC_RESULT: {\"install_succeeded\": true, \"launch_succeeded\": true, \"inst…
 succeeded in 0ms:
2026-10-16T16:22:30.746633Z ERROR codex_core::session: failed to record rollout items: thread 01a14…
2026-10-16T16:22:30.746677Z ERROR codex_core::session: failed to record rollout items: thread 01a14…
2026-10-16T16:22:30.746690Z ERROR codex_core::session: failed to record rollout items: thread 01a14…
2026-10-16T16:22:30.746711Z ERROR codex_core::session: failed to record rollout items: thread 01a14…
2026-10-16T16:22:30.746729Z ERROR codex_core::session: failed to record rollout items: thread 01a14…
2026-10-16T16:22:30.746741Z ERROR codex_core::session: failed to record rollout items: thread 01a14…
tokens used
61,799

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 6 minutes.
  • Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 6 minutes after the clone.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.01

Topics (from GitHub)

8004agent-frameworkagent-frameworksagentsaicdperc8004gamingllmmcpx402

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/daydreams.svg)](https://argusic.com/subject/daydreams)

Questions

Does daydreams run?
Yes. daydreams runs. Argusic installed and launched it on a clean machine in 6 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test daydreams?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit e3231c3de108. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test daydreams?
The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does daydreams take to install?
6 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does daydreams need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing daydreams?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for daydreams?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion