~ ❯ ls blog
Notes from the workshop.
Release notes, design decisions and how we run a fleet of agents. Subscribe with RSS.
Close the window. Keep the agents.
Why wrkstrms runs your panes in a background server, what that buys you (detach, attach from anywhere, restore after a crash), and what happens when you close the terminal.
Getting around a dozen agents
The finder, search across every pane, and keys you don't have to memorize. How to move through wrkstrms when there's a lot going on.
Which agent needs you?
How wrkstrms knows what every agent is doing, and how it gets you to the one that's waiting, without checking every terminal.
One memory for every agent
Why wrkstrms keeps what your agents learn in one local store they all share, and how it reaches Claude Code, Codex and the rest.