Hermes Atlas
Multi-agent & orchestration

Agent Batch

raaaas/hermes-agent-batch

Overnight parallel coding agents on GitHub Actions, planned by Hermes, delivered as one PR per task

In short

Agent Batch is a GitHub Actions system where Hermes Agent plans a list of coding tasks and several agents work through them in parallel overnight. Each task gets its own throwaway VM, its own branch and its own coding agent, and the result arrives as a pull request.

What Agent Batch does

Agent Batch uses GitHub Actions as its whole backend. A prepare job turns a task list into a matrix, and each matrix job checks out the repository on a fresh GitHub-hosted runner, creates a branch such as agent-0N-xxx, runs one coding agent, commits and opens a pull request. Ten tasks therefore become ten jobs, ten VMs, ten branches and ten PRs that run at the same time without touching each other's work. Two workflows ship: agent-batch.yml for nightly or on-demand batches, and agent-issues.yml, which turns an opened issue into a branch, a PR and a comment.

The agent runner is pluggable through the AGENT_BATCH_RUNNER setting. The table lists cline, opencode, kilo, claude-code, codex and dsh, with qoder pending headless CI authentication. Some runners have a free path, such as Cline Credits or opencode free models, while others take your own API key. Hermes desktop acts as the operator console through a plugin in the plugin/ folder: tasks go in, Hermes splits them into phases, dispatches phase N and tracks the resulting PRs.

Key features

  • One isolated GitHub-hosted VM, branch and pull request per task
  • Matrix fan-out so many tasks run in parallel, with logs and retry per job
  • Pluggable coding-agent runners selected with AGENT_BATCH_RUNNER
  • Issue agent workflow that turns an opened issue into a branch, PR and comment
  • Hermes desktop plugin for phasing tasks, dispatching them and tracking PRs

When to use it

  • Queueing a list of small features or refactors before bed and reviewing PRs in the morning
  • Letting an agent handle each GitHub issue in its own sandbox
  • Running agents on free public-repository Actions minutes with free-model runners

Who it is for: Developers who want to fan a task list out to several coding agents on GitHub Actions and review the results as pull requests.

How it fits with Hermes Agent

Hermes Agent plays the orchestrator role through a desktop plugin, while GitHub Actions and the chosen runner agent do the coding work.

Requirements: A GitHub repository using GitHub Actions; your own provider keys for runners without a free path

Note: Only some runners have a free path; claude-code, codex and dsh need your own API keys, and kilo's default models need a Kilo account.

FAQ

What is Agent Batch?

Agent Batch is a GitHub Actions setup that runs many coding agents in parallel, each in its own sandbox VM and branch, and delivers each result as a pull request. Hermes Agent orchestrates the task list through a desktop plugin.

Does Agent Batch work with Hermes Agent?

Yes. The repository includes a Hermes desktop plugin that phases tasks, dispatches each phase to GitHub Actions and tracks the resulting PRs.

Is Agent Batch free and open source?

The repository has no license file, so default copyright applies and you should check with the author before reuse. The README says public repositories get free GitHub Actions minutes and some runners have free model paths.

Similar multi-agent for Hermes Agent

All multi-agent

Related guides: Build agent teams with the Hermes kanban board · Run multiple Hermes agents with profiles · Connect Hermes agents on several machines with Hermes Desktop