imagine if they banned all models and we all went back to writing code by hand and the last 6 months were just a fever dream…imagine

modernizing egghead, removing 13 years of cruft, final killing rails for good, fixing all the perf issues, failed experiments, broken dreams lol 🥚 beta.egghead.io/

~Once a month I take an afternoon to completely revisit my Codex setup in light of new features and/or an improved model What I landed on yesterday is really exciting. I feel like I'm actually getting >50% out of Codex what is possible Working on a blog, but it includes: - a home thread that manages a todo list that is always open - a home thread that manages other threads - heartbeats on almost all of them Still WIP, but the vision is to simplify everything: show what matters to uniquely me (because an agent can't do it), show me what my agents are up to, and convert my provided goals/tasks/intentions to the right threads who are responsible for those workstreams In essence, this "home thread" has become my context manager (context: most my work is not coding)

Feeling pretty good about things

The Legend of Zelda: Ocarina of Time will be reborn on Nintendo Switch 2 in 2026. #NintendoDirect

📣 Open call to agent builders: Let's read agent skills from `.agents/skills`, so people don't have to manage separate folders per agent. Today we pulled the trigger for Codex to read `.agents/skills`. Goal is to deprecate `.codex/skills`. Pls like/tag/RT for momentum.

I went HAM on git worktrees when I learned they were a thing like 6 months ago but slowly drifted back to single branch flows. It's just way easier to manage and far less repeat/conflicting work. But how do you make sure multiple agents don't collide? The flow is simple: You need proper planning. Measure twice cut once has never been more true. After the plan is created, I prompt the model if it's 100% clear on what to do, and if not to surface non obvious questions edge cases we haven't yet covered. Now with a SOLID plan, I turn it into a directed graph of tasks where they know the clear order of operations. The task graph is then fed into a swarm of tmux sessions running [insert your favorite harness here] by a top level agent, lets call it the "ring leader" The agent sessions collaborate via file reservations and their own agent mail messaging system. This ensures no edits are conflicting and duplicate work is not done. The top level ring leader agent just sits there on a cron, checking in to the sessions every ~5 minutes to nudge them to pickup unblocked tasks from the graph if there are any until all the work is done. Then when its all done, I prompt for a summary of work completed and a QA plan for me or other agent to verify. This is like the "ralph loop" but on galactic steroids. It gets work done would have taken several weeks a year ago to get done in a ~2 hour session. If this all sounds too hard to manage, I thought so too. But then I stumbled across what @doodlestein was doing thru one of @johnlindquist's AI workshops. Then Jeffrey released his skills jeffreys-skills.md and holy cow everything I just mentioned above unlocked.