Catalog of agent harnesses — coding-agent runtimes, harness toolkits, and orchestration frameworks used across the FlexNetOS meta workspace.
A FlexNetOS hub: registry.json is the single source of truth, the Rust-native
scripts/validate.sh (the hub-validate crate) keeps it consistent (CI-enforced),
and this README mirrors it. Follows the
Hub Standard.
In scope: agent harnesses — self-contained coding-agent runtimes (e.g. oh-my-pi), harness toolkits/skill frameworks, and orchestration systems for agents.
Out of scope: Claude Code plugins → plugin_hub;
MCP servers → mcp_hub; plain CLI tools →
tool_hub. Rule of thumb: if it's an agent
runtime or the toolkit that builds one, it belongs here.
| Harness | Category | Runtime | Status | Doc |
|---|---|---|---|---|
| oh-my-pi | agent-runtime | multi | stable | doc · run |
| harness | harness-toolkit | node | beta | doc |
| meta-plugin | orchestrator | multi | beta | doc |
| handoff | orchestrator | multi | beta | doc |
| weave | orchestrator | rust | beta | doc |
| rust-port | orchestrator | multi | beta | doc |
| code-research | orchestrator | multi | beta | doc |
The harness toolkit is vendored in-repo at harness/; it now also ships packaged
harnesses (ready-made, runnable, ejectable) as /harness:<name> commands — see the
packaged-harness standard. meta-plugin is the first.
See registry.schema.json for the full field reference. Key
bespoke fields: category (agent-runtime / harness-toolkit / skills-framework /
orchestrator), runtime, and path (for content vendored in-repo).
Add an entry to registry.json, create entries/<id>.md (and a snippets/<id>.sh if
useful), add a Catalog row, then run bash scripts/validate.sh. See the
Hub Standard.