Does cli-continues run?

Yes. cli-continues runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 4 errors on the way, and recorded the session.

How did Argusic test cli-continues?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit e486cd22a592. 2 attempts are recorded, and the full method is on the methodology page.

What did it cost to test cli-continues?

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

How long does cli-continues take to install?

10 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 cli-continues need a GPU?

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

What goes wrong when installing cli-continues?

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 cli-continues?

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.

cli-continues

resume any AI coding session in another tool, Claude Code, Copilot, Gemini, Codex, Cursor

Runssource: GitHubTypeScriptMITcommit e486cd22a592

TypeScript, MIT licensed. The project labels itself: ai coding assistant, claude code, cli, context transfer, cursor, gemini cli, github copilot and session management.

cli-continues runs. An Argusic agent installed it in 10 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Node.js upgraded to v22.14.0 (via /tmp/), pnpm installed and builds approved, project compiles with tsc with zero errors, all 28 test files pass (917/919), CLI binary functions (help, version, scan, list all work), and biome passes with warnings only.
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 96.7 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs
Argusic Score: 96.7 / 100
cost of the verifying run: $0.03 (measured)
recorded runs: 2
last tested: 2026-09-18
stars: 1,535
forks: 39
open issues: 16
watchers: 7
size: 3 MB
created: 2026-01-31
last push: 2026-05-07

Subject data from GitHub, linked at the top of this page, refreshed 2026-09-23. 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 cli-continues, 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.

Node.js v18.19.1 lacks node:sqlite (needs >=22.5)2 minutes
pnpm not available on PATH1 minute
pnpm blocked esbuild postinstall1 minute
Biome lint errors in test files1 minute

Install time: 10 minutes
Cold machine to finish: 7 minutes
Errors hit and fixed: 4 hit, 4 fixed with no human help
How the result was proved: pnpm test exited 0: 917 passed, 2 skipped, 0 failed across 28 files; node dist/cli.js --help printed full usage; --version returned 4.1.1; scan returned 'Total sessions: 1'; list displayed session table; pnpm run check (lint+build) exited 0
Model tokens used: 92,035
Exact commit tested: e486cd22a592
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.

7. **CLI verified** — `--help` prints full usage, `--version` returns `4.1.1`, `scan` finds session…
tokens used
92,035
All tasks complete. Here's my report:
**What I did:**
1. **Node.js too old (v18.19.1, needs v22.5+)** — Downloaded and activated Node v22.14.0.
2. **pnpm missing** — Installed globally via npm.
3. **pnpm approve-builds** — Approved esbuild binary builds.
4. **Biome lint errors** — Ran `biome check --write --unsafe` to auto-fix 21 files (import style, t…
5. **Build verified** — `tsc` compiles without errors.
6. **Tests verified** — `pnpm test` passes: 917 passed, 2 skipped, 0 failed across 28 test files.
7. **CLI verified** — `--help` prints full usage, `--version` returns `4.1.1`, `scan` finds session…

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 MIT, as reported by its host.
Measured 2 times, so the result is not a one-off.

What did not, or is not known

Took 10 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.

Of the 4 ai-coding-assistant projects Argusic has installed and timed, cli-continues was the 3rd fastest to reach a running state, and 4 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 10 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 by	attempt	outcome	score	cost USD	when
Argusic Runner	2/3	Runs	100.00	0.03	2026-09-18 13:22 UTC
Argusic Runner	1/3	Runs	93.33	0.04	2026-09-09 06:01 UTC

Topics (from GitHub)

ai-coding-assistant claude-code cli context-transfer cursor gemini-cli github-copilot session-management

Embed the badge

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

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

Questions

Does cli-continues run?: Yes. cli-continues runs. Argusic installed and launched it on a clean machine in 10 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test cli-continues?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit e486cd22a592. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test cli-continues?: The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does cli-continues take to install?: 10 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 cli-continues need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing cli-continues?: 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 cli-continues compare with the alternatives?: Of the 4 ai-coding-assistant projects Argusic has installed and timed, cli-continues was the 3rd fastest to reach a running state, and 4 of 4 reached one at all.
Where is the evidence for cli-continues?: 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.