I got tired of babysitting my coding agents, so I built TOK

Wait 5 sec.

The problem: I run a few Claude Code and Codex sessions at once, and somewhere along the way I became their babysitter. More terminals than eyes, all of them watched in case one asks a question, fails, or wanders off in the wrong direction. And when a terminal closed, finding the right conversation again meant an archaeological dig through /resume. What I built: TOK, a personal task tool where the agents work inside the task, so I can get on with something else (or, admittedly, make tea). Each task gets its own workspace, with the terminals it needs. One list shows every agent: live, quiet, or waiting on you. When one needs you, your Mac tells you which task. After a restart, Resume reopens each terminal with its own conversation. Even the question it was waiting on is still there. It's not just an agent sitter, though. It's also where my work lives: Claude files what it makes (notes, links, files) on the task it was for, my day gets planned around the hours I actually have, and mail and tickets turn into suggested tasks I confirm. All of it stays in a folder on my Mac. The video shows it in just over a minute: three ways of babysitting, then an evening on the couch while Tok keeps watch. It's a waitlist for now, with invites in waves. The link is in the first comment! Blunt feedback welcome. Does the video make it clear what Tok does? And how do you keep an eye on your agents today: tabs, tmux, or pure willpower?   submitted by   /u/KR4K3N1S [link]   [comments]