open-terminal
A computer you can curl ⚡
Runssource: GitHubhomepagePythonMITcommit b58442aa8599
Python, MIT licensed. The project labels itself: agentic ai, ai, ai agents, ai tools and open webui.
open-terminal runs. An Argusic agent installed it in 11 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Open Terminal 0.14.0 is installed in a Python 3.12 venv; the server starts on port 8766, responds to unauthenticated /health with 200 OK, and executes shell commands via POST /execute with correct exit codes and captured output; the MCP server runs on stdio transport after a patch to fix a fastmcp 4.1.6 API change.
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.
- fastmcp 4.1.6 changed the run() API - run_stdio_async no longer accepts host/port parameters, causing TypeError on MCP stdio transport5 minutes
- Install time
- 11 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- open-terminal run --host 127.0.0.1 --port 8766 started successfully; curl -s http://localhost:8766/health returned {'status':'ok'}; POST /execute with 'echo final-verification' returned exit_code:0 output:'final-verification'; GET /api/config returned features; GET /files/view served README.md content; MCP stdio transport responded to initialize with protocolVersion 2024-11-05; open-terminal --help listed commands
- Model tokens used
- 208,628
- Exact commit tested
- b58442aa8599
- 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.
mcp Start the MCP server (requires 'pip install open-terminal[mcp]'). run Start the sandbox API server. Let me also verify the version: exec /bin/sh -lc '/tmp/venv/bin/pip show open-terminal 2>&1 | grep -E "''^(Name|Version)"' in /work/repo succeeded in 314ms: Name: open-terminal Version: 0.14.0 I now have all the information needed. Let me compile the final result. tokens used 208,628 I now have all the information needed. Let me compile the final result.
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 1 error 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 11 minutes to install, slower than the median of the 38 comparable projects Argusic has measured.
Of the 39 agentic-ai projects Argusic has installed and timed, open-terminal was the 26th fastest to reach a running state, and 28 of 39 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
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/open-terminal)Questions
- Does open-terminal run?
- Yes. open-terminal runs. Argusic installed and launched it on a clean machine in 11 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test open-terminal?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit b58442aa8599. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test open-terminal?
- 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 open-terminal take to install?
- 11 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 open-terminal need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing open-terminal?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does open-terminal compare with the alternatives?
- Of the 39 agentic-ai projects Argusic has installed and timed, open-terminal was the 26th fastest to reach a running state, and 28 of 39 reached one at all.
- Where is the evidence for open-terminal?
- 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.