Skip to content
#0558
AgentCronContainers

Every customer's repo gets a night-shift engineer

Your product promises each customer a dependency bump every night, tested, as a pull request. Two hundred customers, two hundred repos.

Each customer has a container with their repo cloned through the agent's GitHub auth. A cron entry per container fires at 2am and POSTs /api/v1/agent/headless/runs with workflow: "deps-bump": an ephemeral session that updates the lockfile, runs the tests, and on green calls POST /api/v1/agent/github/commit and POST /api/v1/agent/github/pr. The run returns a job_id; you never wait on it.

At 8am one script reads GET /api/v1/agent/jobs/{id}/result for all two hundred. One hundred sixty opened PRs, thirty-one had nothing to do, nine failed tests and filed a todo instead.

Two hundred idle containers cost the server, not two hundred line items. The customer wakes up to a pull request and never sees the engineer who wrote it.

The customer wakes up to a pull request and never sees the engineer who wrote it.