aide
Self-hosted AI workspace for developers and engineers. Bring your own models, work with local or SSH projects, and automate coding and project workflows with AI agents, plugins, skills, and MCP. Keep your files, tools, and reviewable changes in one place.
Could not verifysource: GitHubGoMITcommit 903de5aa948b
Go, MIT licensed. The project labels itself: ai agent, ai workspaces, developer tools, docker, golang, mcp, plugins and self hosted.
Argusic could not get aide running. An Argusic agent installed it in 15 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Source install requires Docker (not available). 62 Python unit tests pass, 124 Node.js CJS tests pass, all 566 documentation links verified, and all checked JS frontend files have valid syntax in this container without Docker. 3 pre-existing test failures remain due to container environment limitations (missing zip, Python 3.12 pathlib import internals, missing desktop browser runtime).
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 10 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page. 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.
- Docker Engine and Docker Compose v2 are required but not installed in this container. The project depends on Docker for building and running the aide backend (Go service inside a container). Source install flow cannot proceed.
- test_launcher_contract: 'zip: command not found' - the `zip` utility is required by scripts/package-release-assets.sh which is called by one of the launcher-contract tests.
- test_cad_step_curve_check: test_sha_guard_prevents_sdk_import_and_source_mutation fails because mocking builtins.__import__ on Python 3.12 triggers pathlib to import ntpath internally before reaching the SHA256 guard.
- desktop-capture.test.cjs: 'ReferenceError: File is not defined' - this test requires browser/desktop runtime APIs not available in Node.js CLI.
- Install time
- 15 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- python3 -m unittest: 62 Python tests pass across 10 test files. node tests: 124/125 CJS tests pass. scripts/check_docs.py: PASS (566 files, 2573 links). node --check internal/server/web/app.js: syntax OK. git diff --check: clean.
- Model tokens used
- 355,935
- Exact commit tested
- 903de5aa948b
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
class WiringTests(unittest.TestCase):
@classmethod
def setUpClass(cls):
import sys
sys.path.insert(0, str(Path(__file__).resolve().parent))
def test_preflight_precedes_fingerprint_and_builder(self):
import inspect
from test_launcher_contract import module
Good, the fix is clean. Now let me generate the final report.
tokens used
355,935
Good, the fix is clean. Now let me generate the final 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
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- 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
- An agent with no time limit did not get it running.
- Took 15 minutes to install, slower than the median of the 83 comparable projects Argusic has measured.
Of the 84 ai-agent projects Argusic has installed and timed, aide was the 72nd fastest to reach a running state, and 58 of 84 reached one at all.
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 | Did not run | 20.00 | 0.14 | |
| Argusic Runner | 1/3 | Did not run | 0.00 | 0.07 |
Topics (from GitHub)
ai-agentai-workspacesdeveloper-toolsdockergolangmcppluginsself-hostedskillsworkflow-automation
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/aide)Questions
- Does aide run?
- Argusic could not verify that aide runs. Argusic installed and launched it on a clean machine in 15 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test aide?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 903de5aa948b. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test aide?
- The run that produced this verdict cost $0.14: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does aide take to install?
- 15 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 aide need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing aide?
- 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 aide compare with the alternatives?
- Of the 84 ai-agent projects Argusic has installed and timed, aide was the 72nd fastest to reach a running state, and 58 of 84 reached one at all.
- Where is the evidence for aide?
- 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.