Two days before Databricks' co-founders take the keynote stage at Data + AI Summit, one of them already shipped. Matei Zaharia, who keynotes Monday, published Omnigent on GitHub Saturday, an open-source meta-harness that sits above Claude Code, Codex, Pi, and any custom agent, governing what those agents can do, where they run, and who can watch them work. Open-source projects build momentum on their own clock, stars, forks, Discord activity, rather than a conference clock, so by the time Zaharia walks on stage Monday, Omnigent will already carry a weekend of adoption data into the room.
What Omnigent does
An agent harness is the scaffolding around a model, the tool that lets Claude Code or Codex read files, run commands, and call other tools. A meta-harness sits one level up: a layer that wraps multiple harnesses at once, so the same policies, sessions, and controls apply no matter which underlying agent is running. Databricks describes agent harnesses as having made models swappable, and positions the meta-harness as the next layer of abstraction, where composition, control, and collaboration live. Omnigent wraps Claude Code, Codex, Pi, and custom agents behind one interface, with sessions reachable from terminal, web, desktop, and phone.
Pick a harness, pick a model, the choice is yours, switching is easy, lock-in lives at the model layer if anywhere, that has been the prevailing read on agent tooling. Omnigent quietly reorganizes that picture: its policies track session state and enforce guardrails like cost budgets and permissions at the meta-harness layer rather than through prompts, and its sandbox can intercept network requests so an agent never sees a credential directly. A layer that governs permissions, budgets, and credential access across every coding agent your engineers run amounts to a control plane, and the company shipping it, in the open-source version at least, is also the company that sells the data platform those agents will eventually need to reach.
Where this fits the stack
Databricks draws its own comparison to the shift from managing individual servers to managing fleets through Kubernetes and Terraform, the kind of abstraction jump that, in hindsight, always concentrates power in whoever builds the new layer first. By that comparison, the meta-harness becomes infrastructure sitting above every agent product, the way a cloud control plane sits above the workloads running on it.
Databricks points to Anthropic's own multi-agent research system and a Fireworks-published result on advisor models as evidence that the frontier has already moved up a level, to systems of agents rather than single agents. If that holds industry-wide, whoever owns the layer that coordinates those systems owns something durable, regardless of which models or harnesses win underneath it.
What changes this quarter
Most engineering organizations running multiple coding agents today have no shared view of what those agents cost or what they can touch. A developer with Claude Code, Codex, and a custom agent open at once is running three separate bills with three separate permission models, and nobody outside that developer's laptop knows what any of them did. Omnigent's cost policies let a team cap spend per session and require approval past a threshold, the kind of control that turns "AI coding tools" from an unmonitored line item into something a budget owner can actually see.
The security case is just as immediate. Coding agents commonly need credentials, a GitHub token, a cloud API key, to do their work, and today those credentials typically sit inside the agent's own environment. Omnigent's sandbox brokers that access instead: the agent can be granted the ability to push to a repository without ever holding the token that would let it do something else with that access. For a security team that has been asked, and currently cannot answer, what its AI agents are able to reach, that is a concrete capability gap closing.
The third stake is slower to arrive but larger. Omnigent is free, useful on day one, and built to make switching between Claude Code, Codex, and other harnesses easy. If it becomes the default control layer inside engineering organizations, the integrations that follow, tighter connections to Databricks Genie, to Unity Catalog permissions, to Lakebase, become reasons to consolidate the data platform decision around Databricks as well. The meta-harness does not need to be a sales tool to function as one. Adoption at the developer-tooling layer, today, for free, is how a platform vendor earns a seat at a much larger procurement conversation later.
The meta-harness layer Omnigent defines, policy enforcement, credential brokering, session governance across every coding agent, is the kind of infrastructure that tends to consolidate around whoever ships it first and iterates fastest, regardless of how freely the code itself can be forked. Databricks just claimed that position for itself, two days before its own keynote stage made it official.
Apache 2.0 licensing means no one is locked into Databricks's hosted version of Omnigent today. But a meta-harness earns its lasting value from the policies, integrations, and habits that accumulate inside it over time, the same dynamic that made switching costs real at the data platform layer even when the underlying file formats stayed open.
Zaharia, Matei, and Kasey Uhlenhuth. "Introducing Omnigent: A Meta-Harness to Combine, Control and Share Your Agents." Databricks Blog, 13 June 2026, databricks.com.
