db-studio
The modern pgAdmin alternative that works with every database.
Runssource: GitHubhomepageTypeScriptApache-2.0commit ef48e61ad7d9
TypeScript, Apache-2.0 licensed. The project labels itself: database management, dbms, drizzlestudio, pgadmin and phpmyadmin.
db-studio runs. An Argusic agent installed it in 4.5 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
All 6 packages build, 1036 tests pass, and the SQLite-backed server starts and serves both the SPA and a real CRUD API at /api/:dbType/ routes over HTTP.
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.
- Bun not installed in container1.5 minutes
- Node.js v18 too old for proxy (wrangler >Node 22)1.5 minutes
- MSW postinstall script errors in isolated linker workspace — @db-studio/monorepo workspace name resolves to garbled shell cmd1 minute
- Bun runtime crashes on better-sqlite3 NAPI module (NAPI FATAL ERROR)0.5 minutes
- Typecheck pre-existing errors: zod@4 incompatible types in @hookform/resolvers/zod (3 files, TS2769)
- Install time
- 5 minutes
- Cold machine to finish
- 21 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- node dist/index.js --database-url 'sqlite:///tmp/e2e-test.db' --port 3459 started; curl / returned 200 with SPA HTML; curl /api/sqlite/tables?db=main returned JSON list of tables; real CRUD created tables, added columns, inserted/updated/deleted records, and executed SQL queries, all with a real SQLite database. Test suite: 'bun run test' in packages/server: 51 test files, 1036 tests passed. Build: 'bun run build': 6 packages, 6 successful.
- Model tokens used
- 371,573
- Exact commit tested
- ef48e61ad7d9
- 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.
M www/src/routeTree.gen.ts
succeeded in 19803ms:
Test Files 51 passed (51)
Tests 1036 passed (1036)
Duration 18.97s (transform 5.80s, setup 1.23s, import 29.82s, tests 9.43s, environment 13ms)
2026-09-20T04:44:27.272977Z ERROR codex_core::tools::router: error=invalid agent id 64071: Error(Pa…
Now I have all the data. Here is my report:
2026-09-20T04:44:51.800381Z ERROR codex_core::session: failed to record rollout items: thread 01a0b…
2026-09-20T04:44:51.800434Z ERROR codex_core::session: failed to record rollout items: thread 01a0b…
tokens used
371,573
Now I have all the data. Here is my report: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 4.5 minutes.
- Recovered from all 5 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 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 4.5 minutes after the clone.
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/db-studio)Questions
- Does db-studio run?
- Yes. db-studio runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test db-studio?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit ef48e61ad7d9. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test db-studio?
- The run that produced this verdict cost $0.22: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does db-studio take to install?
- 4.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 db-studio need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing db-studio?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for db-studio?
- 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.