Plug any ACP agent into Omnigent with your tools and governance built in
If you run an agent that speaks the Agent Client Protocol, whether it's Qwen Code, Goose, Grok, Kilo Code, or something you built in-house, you can now point Omnigent straight at it and drive it from the same web UI as every other agent.
Before this, a new agent meant a new integration. The generic acp harness
removes that step: you give Omnigent a launch command and it speaks ACP against
whatever that command starts. Omnigent renders the agent's streaming output,
reasoning, and tool cards, routes its permission requests through your
contextual policies as approval cards, and honors interrupts. It also hands the
agent Omnigent's own builtin tools (session, sub-agent, skill, and policy
tools) alongside the agent's native ones, so an outside agent runs inside your
governance from the first turn.
A custom ACP agent running in the Omnigent web UI, with its tool calls routed through Omnigent's governance.
Each ACP agent brings its own auth, so log into it through its own CLI first;
Omnigent stores no credential. Register an agent with omnigent setup, then
configure harnesses, then Custom ACP agent, then Add, giving it a name,
a launch command, and an optional model. Paste-ready commands include:
qwen --acp
goose acp
grok agent stdio
kilo acp
Each registered agent gets a stable slug and surfaces as its own harness id,
acp:<slug>, in the web picker and in agent YAML. To launch one straight from
the CLI:
omni run --harness acp:<slug>
See the harnesses docs for the full setup, config
format, and the OMNIGENT_ACP_MCP=0 switch if you want to turn the builtin-tool
bridge off.
Enjoying Omnigent? If this is useful to you, give us a star on GitHub ⭐. Come say hi on Discord, or download the latest release.