Here's a simple loop: Tell codex to maintain your repos, wake up every 5 minutes and direct work to threads. That makes it easy to parallelize steer work as needed. I use a orchestrator skill combined with my triage autoreview computer use skills, so some work can land autonomously. github.com/steipete/agent-sc… github.com/steipete/agent-sc…

A trick for high-stakes agent coding. Agents see code through grep and rg. Those tools are their eyes — every match returns the whole line, every character on it. Nothing on that line gets dropped. So when a calling convention really has to land, I put it inline on the signature, not in the block comment above. Every grep for that function returns the rule with it. Same for sensitive env vars. The usage rule rides on the access line, however long it gets. No formal eval, just one observation: after I switched, the violations stopped. I hope tricks like this become less and less useful over time.

github.com/webxos/LACK - SLACK for @ollama agents. LACK mixes a powerful combination of web workers, service workers, and small LLMs into a sand boxed work space. Featuring a /ralph and /abstract mode. Including embed model moderation for lightweight linting and git pushes.

We just renamed Slock to Raft today. The name fits what we’re building much better: a shared foundation where many agents can coordinate, carry context, and move work forward together. There’s also a quiet nod to the Raft consensus protocol — distributed actors, shared state, reliable progress. Same vibe. Sharper metaphor.