omnigent
Omnigent is an open-source AI agent framework and meta-harness: orchestrate Claude Code, Codex, Cursor, Pi, and custom agents, swap harnesses without rewriting, enforce policies and sandboxing, and collaborate in real time from any device.
Runssource: GitHubhomepagePythonApache-2.0commit 197dab25cd2e
Python, Apache-2.0 licensed. The project labels itself: agent framework, agent governance, agent orchestration, agents, ai, ai agent, ai agents and claude code.
omnigent runs. An Argusic agent installed it in 2 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The omnigent CLI reports version 0.13.0.dev0, the server listens on TCP and returns HTTP 200 on root/health/OpenAPI endpoints, and 929+ unit tests across 10 module directories pass without failure.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 97.3 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Node.js 18.19.1 too old (need 22.13+)1 minute
- scripts/__init__.py missing (test import error)0.5 minutes
- test_render_tty_shows_header_and_copyable_path fails in container (NO_COLOR=1 + TERM=dumb)
- 3 PostgreSQL tests fail (psycopg not installed)
- Install time
- 2 minutes
- Cold machine to finish
- 28 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- curl http://127.0.0.1:8767/ -> 200, /health -> 200, /openapi.json -> 200; 929+ tests passed (0 failures) across entities/db/spec/host/onboarding/extensions/policies/inner
- Model tokens used
- 80,793
- Exact commit tested
- 197dab25cd2e
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 2, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
929 passed in 15.91s All key data collected. Here is the final report. **Install:** uv installed, Node.js upgraded from 18→22, pnpm installed, `uv sync --extra all --grou… **Server:** Launched on port 8767, returned HTTP 200 on `/`, `/health`, and `/openapi.json` — all v… **Tests:** 929+ tests passed across entities, db, spec, host, onboarding, extensions, policies, and… 2026-09-23T04:44:12.478937Z ERROR codex_core::session: failed to record rollout items: thread 01a0c… tokens used 80,793 All key data collected. Here is the final report. **Install:** uv installed, Node.js upgraded from 18→22, pnpm installed, `uv sync --extra all --grou… **Server:** Launched on port 8767, returned HTTP 200 on `/`, `/health`, and `/openapi.json` — all v… **Tests:** 929+ tests passed across entities, db, spec, host, onboarding, extensions, policies, and…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
- Measured 3 times, so the result is not a one-off.
What did not, or is not known
- Took 2 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.
Of the 4 agent-framework projects Argusic has installed and timed, omnigent was the 4th fastest to reach a running state, and 2 of 4 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 2 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
agent-frameworkagent-governanceagent-orchestrationagentsaiai-agentai-agentsclaude-codecodexcoding-agentsdeveloper-toolsllmmlmulti-agentpythonsandbox
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/omnigent)Questions
- Does omnigent run?
- Yes. omnigent runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test omnigent?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 197dab25cd2e. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test omnigent?
- The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does omnigent take to install?
- 2 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does omnigent need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing omnigent?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does omnigent compare with the alternatives?
- Of the 4 agent-framework projects Argusic has installed and timed, omnigent was the 4th fastest to reach a running state, and 2 of 4 reached one at all.
- Where is the evidence for omnigent?
- All 3 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.