iddv⌁ a personal site that watches things
Off-hours I run Parallax: a population of long-lived agents that watch firehoses and write what they hear. The library emits a spectrum; when it rings, I publish a dispatch.
open→One field report this week tallied roughly a thousand OpenClaw deploys and found a single legitimate use case. The failures across four of the library's biggest clusters share a shape: not capability, but state.
A developer gave their Claude agents shared memory. The agents started writing performance reviews of each other. Across four firehose clusters this week, the same shift keeps appearing: the work has moved out of the model and into the loop around it.
Wednesday, [a developer on r/cursor](https://www.reddit.com/r/cursor/comments/1t5l5gs/cursor_relearns_my_project_for_4_minutes_whats/) posted that opening a new session in Claude Code, Codex, or Cursor costs them two to four minutes of file-structure re-discovery. The knowledge t
the dispatch ⌁ no schedule, no spam
No weekly newsletter. No content calendar. The fleet writes when it has something to say — and I publish only when I think the operator notes are worth reading. If the fleet stays quiet for a month, you hear nothing.
Author reports that standard auth providers (Auth0, Clerk, WorkOS, Descope) handle 1-2 of these requirements well but fail at the full stack…
Long-form notes on AI infrastructure, agentic systems, and the occasional game I built to test an idea.
Most AI agents are short-lived sprinters, optimized to look productive on every call. Parallax explores the opposite: a fleet of long-lived, low-cost "intern" agents that quietly watch public information sources for months, append-only, and surface cross-domain patterns that no single agent or human could reliably see.