Project · public repository

Agent Harnesses

Four installable coordination systems for coding agents. Choose the smallest boundary that matches the work, then install from the verified v0.2.0 release.

Choose by coordination boundary

Every package is complete on its own. The options are alternatives by fit, not steps in a maturity ladder.

Selected harness: Workspace Harness

workspace-coordination

Workspace Harness

Medium

A coordinator index that preserves child-local ownership.

I have autonomous child folders inside one containing workspace.

Best for
Contained child projects that share one workspace boundary and a small shared index.
Not for
Independent repositories or a single project with no child coordination.
What it changes
Creates a workspace control directory and child-local coordination records.
View full prompt
Install Workspace Harness (`workspace-coordination`) v0.2.0 from https://github.com/fabianomag/agent-harnesses/releases/download/v0.2.0/workspace-coordination-0.2.0.zip. Before any write, confirm the explicit target and resolve exactly one Python 3.10+ executable available to the user or system as `<python>` (for example `python3`, `python`, or `py -3`); reuse only that executable and never use a private Codex runtime. Download the ZIP and its adjacent `.sha256` sidecar into an isolated temporary directory, verify the checksum before extraction or execution, then extract it. From the extracted bundle root run:
`<python> -B installer.py doctor workspace-coordination --target "<target>" --json`
Stop without writes on a mismatch and only recommend a better fit; never silently substitute another harness. Then run:
`<python> -B installer.py install workspace-coordination --target "<target>" --dry-run --json`
`<python> -B installer.py install workspace-coordination --target "<target>" --apply --json`
Follow `package/README.md` inside the extracted bundle to initialize the target, then run from the bundle root:
`<python> -B installer.py verify workspace-coordination --target "<target>" --json`
Report success only when this final result contains `ready=true`. Clean up temporary files and report the receipt plus `uninstall`/rollback instructions. Do not edit unrelated documentation, `PATH`, or `.gitignore`, and do not install a global Skill.