zlacker

>>keepam+(OP)
This is such low hanging fruit. Coding agents can be orchestrated. Controlled, rerun, and tested. Are we just coming up with ways to not be at our desks working? Why not scale out agents on a cluster to do more work? Why email instead of SMS with a web endpoint? I can access each agent of mine via a dashboard from anywhere in the world.

Not trying to poo poo, just saying all it takes is Claude Code to introduce this and you’re done.

>>reacto+QA
> I can access each agent of mine via a dashboard from anywhere in the world.

What do you use for this?

>>freedo+5q1
I use a central server behind a vpn and oauth that gives me access to my "farm". A product I wrote to manage fleets of docker containers that's now being used to manage fleets of docker containers running a tty wrapper I also wrote to send everything over. The backend to this is go+htmx+websockets. The tty wrapper runs OpenCode / Claude / Codex / etc when it starts up and is given access to a repo via volume mount. From there, the "agent" either gets instructions from the websocket or it pulls tasks from Linear. Think ECS but each service instance is an agent.

I can login, create a task, look at task results, approve PR's, deny PR's, retask an agent, or take one over for my own exploratory endeavors.

>>reacto+Ru1
This sounds very cool like what’s stopping you from releasing this as a product? What’s your thinking on that?