With unlimited tokens, the constraint becomes compute power: CPU, memory, disk space. Dan Luu’s and Dennis Snell’s work inspired me to move from managing Codex sessions to assigning it a big task and a pool of compute resources to maximize. It burns tokens! I’ve got through ~120 billion tokens since Thursday. Dan is at ~300 billion total. How I’ve started 80 codex sessions My home cluster has a total of ~80 CPU threads, 288 GB of RAM, and 20TB worth of fast SSDs: I’ve started two VMs with 20 CPU threads and 40 GB of ram each, and one smaller VM with . Then I started codex in a tmux session in each. I’ve asked them to: Build a direct PHP -> binary compiler Port Lightning css, libsqlite, pandoc, and other tools to PHP Build a push my changes to the remote site feature for Reprint My prompts could be summarized as: /goal you will supervise a swarm of codex sessions to build projectspec.md. One worker = one tmux window so I can inspect. Have a critic to candidly evaluate your performance…
No comments yet. Log in to reply on the Fediverse. Comments will appear here.