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.

▲

keepamovin 6 hours ago | parent | next [-]

There's a sense in which you're right that it could be cloned easily by a provider. But that's also an advantage in that we work acorss providers, they're not going to create a service that interacts with each other. So it's more of a fit for someone outside the AI providers to do it, but we'll see.

▲

freedomben 3 hours ago | parent | prev | next [-]

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

What do you use for this?

	▲	reactordev 3 hours ago \| parent [-]
		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.

▲

risyachka 4 hours ago | parent | prev [-]

>> Why email instead of SMS with a web endpoint

Pretty sure this was vibe-coded in a few days based on a discussion that was on HN a few days back and few people mentioned it would be nice to code on the go via email.