orca-q
The open source | Next Generation database editor
Runssource: GitHubhomepageTypeScriptMITcommit dc786eac8737
TypeScript, MIT licensed. The project labels itself: dbms, electron, mariadb, mysql, nuxt, postgresql, redis and sql.
orca-q runs. An Argusic agent installed it in 6.5 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Production build compiles, Nuxt server listens on :3000 and returns HTTP 200; 686 unit tests pass, 457 Nuxt tests pass.
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 100 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 v18.19.1 lacks node:util.styleText needed by @clack/core3 minutes
- Missing echarts dependency — build failed resolving echarts/charts1 minute
- npm peer dep conflict @nuxtjs/storybook requires storybook@~9.0.5 vs root ^10.4.10.2 minutes
- postinstall electron-builder crashes on require() of ESM module @noble/hashes/blake2.js0.2 minutes
- Install time
- 7 minutes
- Cold machine to finish
- 14 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- node .output/server/index.mjs started and curl http://localhost:3000 returned 200
- Model tokens used
- 180,884
- Exact commit tested
- dc786eac8737
- 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.
1. **Peer dependency conflict** (`@nuxtjs/storybook` ↔ `storybook`) — used `--legacy-peer-deps` 2. **Node.js v18 too old** (missing `node:util.styleText`) — upgraded to Node 22 via `nvm` 3. **ESM `postinstall` crash** (`electron-builder` → `@noble/hashes`) — used `--ignore-scripts` **Missing runtime dependency** `echarts` — installed it to fix the production build. Not listed in … ## Test Results | Suite | Files | Passed | Failed | Notes | | ------- | ----- | ------ | ------ | ----- | | Unit | 79 | 686 | 0 | Clean pass | | Nuxt | 70 | 457 | 22 | Pre-existing failures (localforage/happy-dom, no canvas for a… | Build | ✅ | | | Production build succeeds, server starts and returns HTTP 200 | ## Final Launch `node .output/server/index.mjs` listens on `http://[::]:3000` — `curl` returned `200`.
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.
- Installed in 6.5 minutes.
- 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 MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
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 6.5 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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/orca-q)Questions
- Does orca-q run?
- Yes. orca-q runs. Argusic installed and launched it on a clean machine in 7 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test orca-q?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit dc786eac8737. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test orca-q?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does orca-q take to install?
- 6.5 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 orca-q need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing orca-q?
- 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.
- Where is the evidence for orca-q?
- All 2 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.