oneagentgraph
Compose agents into a graph over oneharness and onejudge, and merge their outputs into one NDJSON event stream.
One config file and one CLI call: the graph names an oneharness config per role
and side, and oneagentgraph prepares each member's launch, supervises liveness,
and emits every turn, tool call, fallback, and settle as an event you can pipe
into anything.
Install
To install a revision that has not been released yet, build it from the repository:
Prebuilt archives for Linux (x86-64, arm64), macOS (Intel, Apple silicon), and
Windows (x86-64) are attached to every release, with sha256 checksums.
onejudge is a library dependency, linked into this binary — there is
nothing to install for it. run, smoke, and health drive the oneharness
CLI, so that has to be on PATH; validate, history, persona, trigger,
reset-timer, and cancel need nothing at all.
ONEAGENTGRAPH_ONEHARNESS_BIN names a pinned install instead.
What it does
A graph is YAML — members, the oneharness config each side uses, personas, schedules, and dependencies:
version: 1
name: node-scope
members:
worker:
kind: onejudge
base_config: ./onejudge.base.yaml
agent:
judge:
mode: bypass
run streams one envelope per line. Exit 0 means every member settled, 1
that one failed or died, 2 that the config is invalid.
oneagentgraph owns no harness, model, or fallback logic. oneharness keeps owning identity chains, fallback, model pins, and quota classification; onejudge keeps owning the two-party conversation. This composes them.
Develop
Licence
MIT. See LICENSE.