Yes. omg.dev runs. Argusic installed and launched it on a clean machine in 62 minutes, hitting 3 errors on the way, and recorded the session.

How did Argusic test omg.dev?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 015f45a98970. One attempt is recorded, and the full method is on the methodology page.

What did it cost to test omg.dev?

The run that produced this verdict cost $0.44: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does omg.dev take to install?

62 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 omg.dev need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing omg.dev?

3 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for omg.dev?

The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

omg.dev

omg.dev, Remote control for claude, codex, cursor, opencode, pi, grok, jcode with mobile client

Runssource: GitHubTypeScriptMITcommit 015f45a98970

TypeScript, MIT licensed. The project labels itself: ai agents, claude code, codex, coding agents, developer tools, ios app, mcp and opencode.

omg.dev runs. An Argusic agent installed it in 62 minutes and hit 3 errors on a clean machine with no GPU, and the whole session was recorded.

Dependencies installed, typecheck passes, the server starts on 127.0.0.1:8766 and all API endpoints respond correctly, and the test suite runs 5356 passing tests with only environment-specific failures related to Chromium, dbus, mobile native modules, and AI agent credentials.
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 93.3 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs
Argusic Score: 93.3 / 100
cost of the verifying run: $0.44 (measured)
recorded runs: 1
last tested: 2026-10-29
stars: 552
forks: 0
open issues: 0
watchers: 0
created: -
last push: -

Subject data from GitHub, linked at the top of this page. 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.

Time lost to each failure while testing omg.dev, drawn from the recorded run — Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

bun not found in container, installed via npm --prefix ~/.local2 minutes
thinking level test failed because opencode now has reasoning levels in the local model catalog cache1 minute
44 test failures are environment-specific (Chromium/desktop, mobile/native, dbus, AI agent subscriptions, hosted service) — see test_depth note

Install time: 62 minutes
Cold machine to finish: 38 minutes
Errors hit and fixed: 3 hit, 2 fixed with no human help
How the result was proved: bun run serve started and api/settings returned 200 with 32 keys; /api/sessions returned live session data; /api/agents returned agent catalog; bun run typecheck exited 0; bun test ran 5411 tests. bun doctor reported server responding and Codex CLI found at /usr/local/bin/codex
Model tokens used: 614,882
Exact commit tested: 015f45a98970
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

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

    code: "ENOENT"
      at async webIndexResponse (/work/repo/src/commands/serve.ts:2321:41)
      at async fetch (/work/repo/src/commands/serve.ts:12552:110)
GET - http://127.0.0.1:8766/ failed
[artifact-refresh] scheduler stopped
exec
/bin/sh -lc 'pkill -f "bun run src/cli.ts serve" 2>/dev/null; sleep 1; echo "cleaned"' in /work/repo
 exited 143 in 0ms:
Here is the complete assessment.
tokens used
614,882
Here is the complete assessment.

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.
Ran without a GPU, so it does not need one to start.
Licensed MIT, as reported by its host.

What did not, or is not known

Took 62 minutes to install, slower than the median of the 105 comparable projects Argusic has measured.
Hit 3 errors during setup, 1 of which were not solved.
Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 106 ai-agents projects Argusic has installed and timed, omg.dev was the 103rd fastest to reach a running state, and 78 of 106 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.

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

tested by	attempt	outcome	score	cost USD	when
Argusic Runner	1/3	Runs	93.33	0.44	2026-10-29 07:54 UTC

Topics (from GitHub)

ai-agents claude-code codex coding-agents developer-tools ios-app mcp opencode remote-development self-hosted

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/omg.dev.svg)](https://argusic.com/subject/omg-dev)

Questions

Does omg.dev run?: Yes. omg.dev runs. Argusic installed and launched it on a clean machine in 62 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test omg.dev?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 015f45a98970. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test omg.dev?: The run that produced this verdict cost $0.44: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does omg.dev take to install?: 62 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 omg.dev need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing omg.dev?: 3 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does omg.dev compare with the alternatives?: Of the 106 ai-agents projects Argusic has installed and timed, omg.dev was the 103rd fastest to reach a running state, and 78 of 106 reached one at all.
Where is the evidence for omg.dev?: The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.