Delegation · Automation · Computer use
Dante is the delegation, automation, and computer-use agent on the Hermes harness. It splits a job across isolated subagents, checks their work, and reports only what it confirmed.
Install — one line
curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash
What Dante is
Dante is the delegation, automation, and computer-use agent on Hermes, the self-improving agent harness built by Nous Research. It is terminal-native and runs wherever you put it — a $5 VPS, a GPU cluster, or serverless infrastructure that costs almost nothing when idle. You can talk to it from Telegram while it works on a cloud VM.
Dante is the protagonist; Hermes is the engine. It is built to complement Rook, who handles heavy parallel codegen — Dante owns the decomposition, the dispatch, and the verification. It doesn't grind out the work alone. It splits it, runs it across isolated subagents, and confirms the result before it hands anything back.
What it does
Dante dispatches coding work instead of grinding it out itself. It spawns focused subagents — up to three at once — each with its own isolated context and terminal, handed everything it needs up front. It always checks their output before reporting. A summary is a claim; the proof is the trace.
Dante owns the always-on orchestration layer. It schedules autonomous jobs, fires actions on events, captures reusable procedures as skills, and persists durable facts across sessions — so the next run starts ahead of where the last one ended.
Dante drives GUI automation through the computer-use backend. The default cua-driver targets macOS; this host is Linux, so Dante confirms a working backend before it promises a GUI action. The caveat is stated, not hidden — that's the point.
The loop
Every delegated job runs the same four steps. The last one is the one most agents skip.
Dante breaks the job down and dispatches it with delegate_task, up to three subagents at once.
Each subagent gets its own context and terminal, with all the facts it needs handed over up front.
Dante checks every subagent's output against the goal before it accepts the result.
Only confirmed work comes back. A summary is a claim; the trace is the proof.
Honesty, designed
Disabled toolsets render red and stay visible — never hidden behind a capability it doesn't have. A real capability said plainly beats an invented one every time.
The default cua-driver targets macOS. On a Linux host, Dante confirms a working backend before it promises a GUI action — it won't claim a capability it can't yet run.
Several toolsets are disabled on this profile. They show up red, not hidden. Dante reports what it actually has, not what would look good on a feature grid.
Dante decomposes, dispatches, and verifies. Hands-on parallel codegen across many files is Rook's job, not Dante's. Knowing the boundary is part of the work.
Get started
One line installs the harness. From there, Dante delegates, automates, and verifies — on whatever machine you point it at.
Install — one line
curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash