meta-harness · governance · agent teams

Omnigent Field Guide

A concise, sourced guide to Omnigent: what it is, how it fits above coding agents, and where it matters for teams.

This knowledge base turns a long research report into durable pages: concepts, architecture, policies, workflows, Hermes usage, limitations, and primary sources.

Start with the concept View architecture Open sources

The shortest useful map

Omnigent sits above the harnesses. It gives sessions, policy, sandboxing, interfaces, and collaboration a common place to live.

Omnigent architecture diagram showing users, interfaces, server, runner, harnesses, policies, sandboxing, and sources.
Users → interfaces → Omnigent server → runner/host → Claude Code, Codex, Hermes, Pi, custom YAML agents.

Guide pages

Each page is deliberately small and source-linked so the guide can evolve as the project matures.

What Omnigent is, why a meta-harness exists, and how it differs from a single agent harness or SDK.

open page →

The server-runner model, interfaces, harness abstraction, credentials, deployment targets, and sandbox boundary.

open page →

How Omnigent maps to org-level governance, SSO, cost control, auditability, and managed Databricks tradeoffs.

open page →
08

Sources

Primary official sources and corroborating coverage used for the field guide.

open page →