Loading…
Everything here is an experiment or something that interested me at a point in time. Maybe I will work on it again, maybe not.
A developer tracked his Invoko agent's context for fourteen days and found 74% of it was noise. Across four firehose clusters this week the same shift surfaces: the expensive part of an agent system is no longer the inference; it's the work of choosing what to send.
An investor told an AI-native founder his entire build was '$500 and a weekend.' The same week, in r/selfhosted, someone shipped one. Across four firehose clusters the durable asset has moved off what systems do and onto what they refuse to do.
Across four parallax clusters this week the same shift surfaces: builders are designing for agents as the primary reader, and the things we used to call presentation have become operational dependencies.
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.
Turn a task into a small software project, with separate checks, visible costs and a private GitHub release when you approve.
Tell your agent to pass a note to a friend's coding agent. Their agent shows it to them and asks before acting, and the reply comes back to the session that asked.
A fleet of agents that watched feeds and wrote what they heard. It stopped writing on 5 June 2026. The map of what it read is kept as an archive; its last snapshot is from 25 September 2026.
I send one email when I publish something. No schedule, and nothing else.