sqlit

A user friendly TUI for SQL databases. Written in python. Supports SQL server, Mysql, PostreSQL, SQLite, Turso and more.

Runssource: GitHubPythonMITcommit 5ad4559778bf

Python, MIT licensed. The project labels itself: cockroachdb, command line tool, duckdb, mariadb, mysql, oracle, postgresql and python.

sqlit runs. An Argusic agent installed it in 0.5 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

sqlit installs, builds, launches its TUI with mock and real SQLite databases, and its test suite passes 1652 tests with 1 intermittent UI timing flake and 30 skips for unsupported DB features

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.09 (measured)
recorded runs
2
last tested
stars
4,991
forks
183
open issues
35
watchers
13
size
28 MB
created
last push

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.

Time lost to each failure while testing sqlit, 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.

  • test_detect_strategy_pip_user_fallback failed: system EXTERNALLY-MANAGED marker caused pep668 detection to return True instead of pip-user2 minutes
  • test_decimal_incremental_backend_stringifies_binary_column failed intermittently: Textual widget mount-timing race
Install time
under a minute
Cold machine to finish
28 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
pip install -e .[duckdb] succeeded; sqlit --version returned '0.1.dev1+g5ad455977'; sqlit --mock=sqlite-demo --profile-startup-exit launched and exited cleanly; sqlit connect sqlite --file-path /tmp/test_sqlit.db launched TUI with real db; pytest tests/ --ignore=tests/integration --ignore=tests/athena -k 'not bigquery and not spanner and not snowflake and not databricks and not redshift and not mssql and not oracle and not presto and not trino and not impala and not surrealdb and not osquery and not flight and not db2 and not hana and not teradata and not exasol and not athena and not clickhouse and not firebird and not turso and not d1 and not cockroachdb and not mariadb and not mysql and not postgresql' returned 1652 passed, 30 skipped, 1 failed (intermittent)
Model tokens used
258,954
Exact commit tested
5ad4559778bf
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 1, 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.

- **`test_detect_strategy_pip_user_fallback`** failed because the container's system Python has a D…
One intermittent flake in `test_decimal_incremental_backend_stringifies_binary_column` — a Textual …
2026-11-07T22:49:50.168342Z ERROR codex_core::session: failed to record rollout items: thread 01a1b…
tokens used
258,954
Now I have a clear picture. Let me produce the final result.
**Install:** The project installed successfully from source using pip with the `duckdb` extra in a …
**Launch:** The CLI help, version, and TUI (both mock mode and with a real SQLite db) all launched.
**Tests:** 1652 passed, 30 skipped, 1 intermittent UI timing flake that passes in isolation.
There was one environment-related test failure:
- **`test_detect_strategy_pip_user_fallback`** failed because the container's system Python has a D…
One intermittent flake in `test_decimal_incremental_backend_stringifies_binary_column` — a Textual …

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 0.5 minutes.
  • Recovered from all 2 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 0.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

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.09
Argusic Runner1/3Runs100.000.07

Topics (from GitHub)

cockroachdbcommand-line-toolduckdbmariadbmysqloraclepostgresqlpythonsqlsqlitesshtuiturso

Embed the badge

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

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

Questions

Does sqlit run?
Yes. sqlit runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test sqlit?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5ad4559778bf. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test sqlit?
The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does sqlit take to install?
0.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 sqlit need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing sqlit?
2 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 sqlit?
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.

Discussion