Model or dataset
taracodlabs/aiden avatar
taracodlabs/aiden

Aiden's pipeline ends in Proof, not in a zero exit code

Aiden — Autonomous AI agent that operates your computer with prompts: browser control, terminal execution, workflows, tools, recovery systems, and persistent memory. Built solo. AGPL-3.0.

899 stars155 forksTypeScriptAGPL-3.0

At a glance

What is it?
An AGPL licensed autonomous work engine for Windows, Linux, WSL and macOS in API mode, installed from npm as aiden-runtime. Its job pipeline tracks approvals, effects, evidence and verdicts as separate records, its manifest accepts only Node 20 or 22, and the environment example mixes three variable prefixes while documenting the switch that skips every confirmation prompt.
Who is it for?
Aiden is worth reading if you are building an agent that has to prove what it did rather than report what it believes it did, because the pipeline refuses to treat a successful command or a model saying done as completion, and the artifacts are separated so interrupted work can be reconciled. Three things to check first.
Can I use it commercially?
Yes, with strict conditions. AGPL-3.0 is a network copyleft licence: if people use a modified version over a network, for example as a hosted service, you must offer them its source code under the same licence.
Is it still maintained?
Yes. The repository last received commits 32 days ago.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 19, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • taracodlabs/aiden899 ★ · +79
Star history
Repository2026-09-112026-11-19
taracodlabs/aiden820899

79 Stars in the last 69 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Three variable prefixes in one environment example

The environment example opens with its own instructions: copy it to `.env`, keep that file out of git, and never commit real credentials. The posture it describes is local by default. The API server port is set to 4200, the bind address is documented as localhost only with a note to widen it to 0.0.0.0 only for remote or LAN access such as a headless server or WSL2, and the CORS origin is documented as localhost only with a wildcard as the opt-in. Browser timeouts default to 15000 milliseconds, debug logging is off, and the user data directory defaults to a path under the Windows application data folder.

What is inconsistent is the naming. The server port is `MY_SERVER_PORT`, while the bind address, CORS origin, browser flags, user data, config directory and log file all use an `AIDEN_` prefix. Then the two most consequential switches use a third name entirely: `DEVOS_AUTO_APPROVE` and `DEVOS_HEADLESS`.

The same header also states the intended default model: Aiden works fully offline with only Ollama configured, and all cloud provider keys are described as optional fallbacks.

One variable skips every confirmation prompt

The approval design is the project's main claim, and it is visible in both the pipeline and the environment file.

The controls are named as risk-tiered approvals, trust levels, budgets, interruption, scoped permissions, leases and generation fencing, all described as keeping consequential actions visible. The job pipeline then places Approval as its own stage between Effect and Execution, so an action has to pass through a recorded gate rather than follow straight from the plan.

The escape hatch is one line in the env example. `DEVOS_AUTO_APPROVE=false` sits there with a comment saying that setting it to true skips all confirmation prompts for CI or automation. The default is the safe side, and the flag is named for the opposite of what it does, so a reader scanning a deployment configuration has to notice both the prefix and the polarity.

A second switch, `DEVOS_HEADLESS`, controls whether browser automation runs without a visible window, and a third near it runs Chromium headless for CI and server deployments. Both default to false.

Eleven stages, and exit code zero is not the last one

The workflow is drawn as a single chain: a goal becomes a job, which becomes a plan and its claims, which become an attempt, which becomes an effect, then an approval, then an execution, then evidence, then a verification, then a verdict, and finally a proof.

The sentence that explains the chain is the design statement of the project. Aiden does not treat a successful command, or a model saying done, as proof. Jobs, Attempts, Effects, approvals, Evidence, Verification, Verdicts and Proof are each tracked separately, with the stated reason being that interrupted, stale, conflicting or externally uncertain work can be recovered and reconciled honestly.

That separation is what makes the remaining features make sense. Verification and Verdicts imply something else already exists, namely a run that produced an effect worth checking. Durable evidence is referenced in the codebase use case, where the described sequence is to snapshot a repository, understand its structure, preserve existing user work, make conflict-safe changes, run structured tests and builds, perform Git operations and verify the final state with evidence. The claim is not that the agent is reliable, but that its output is inspectable enough to argue about.

The manifest admits Node 20 and 22 and nothing else

The runtime constraint is written as an engine range rather than a minimum:

code
"engines": {
    "node": ">=20 <21 || >=22 <23"
}

So Node 20 and Node 22 are the accepted versions, and Node 21, Node 23 and anything after are outside the declared range. The package manager is pinned too, at npm 10.9.8, and the distribution name is `aiden-runtime` while the repository is called aiden.

Two command names are installed, `aiden` and `aiden-runtime`, and both point at the same bootstrap file, `./bin/aiden-bootstrap.cjs`. The declared entry module is `./dist/cli/v4/aidenCLI.js`, a path that keeps a `v4` segment inside a package numbered 4.21.2. Workspaces are declared for `packages/*`.

A dependency detail stands out in the bundle list: the model context protocol SDK, the Slack bolt library, express, an IMAP client and the Twilio library are all bundled rather than installed. Those five decide what the agent can reach without asking for anything else to be present, since a messaging and email stack is available the moment the package is installed.

The npm description drops macOS and the screenshots are labelled

Two small mismatches between what the readme says and what the manifest says are worth putting side by side.

The banner and the heading both list Windows, Linux, WSL and macOS in API mode. The npm description reads as a local-first work engine for Windows, WSL and Linux, with multiple providers and offline Ollama support, so macOS appears in the readme and not in the package metadata. The manifest also carries a custom `aiden` field whose only content is an edition set to pro, which is not explained anywhere in the visible metadata.

The screenshot section is more careful than the manifest, and deliberately so. The gallery holds 34 captures, and a note says they cover the main product surfaces without implying that a provider, account, MCP server or workflow is already connected. The date stamp on the preview is 13 September 2026, and the disclaimer under it says the captures come from a separate unconfigured profile, are not simulated task results or proof of a published release, and do not demonstrate account connections, paid checkout or task execution.

Two expandable sections in the same area contain only HTML comments with no prose between them, so the details that would carry platform, provider, channel and runtime specifics are present as headings and empty as content.

Two licence files and eight release notes at the root

The repository root carries `LICENSE`, a second file called `LICENSE-SKILLS.md`, and a `RELICENSING.md`. Both licence files are in the npm files list, so whatever terms attach to the bundled skills travel separately from the terms attached to the engine.

That distinction matters because the readme leads with Bundled Skills, and the manifest's files array ships a skills directory with three exclusions carved out of it: the installed tree, the pending learned tree and the approved learned tree. In other words, the package ships skill material and carves out the parts a user has installed or that are waiting for review, which is a distinction between the engine's code and the content the engine uses.

Release notes are not filed away. Eight of them sit in the root, covering v4.5.0, v4.17.0, v4.19.0-rc.1, v4.19.0, v4.19.1, v4.21.0, v4.21.1 and v4.21.2, while `CHANGELOG.md` and `SECURITY.md` sit beside them. The install instructions name the stable channel as v4.21.2 through the npm latest tag, and separately point at an archived release candidate, v4.19.0-rc.1, as something to read rather than to install.

A metasearch, a Worker, a directory called moat, and a soul file

The root listing is wide, and a few entries explain what the agent can reach. There is a `searxng/` directory with its own compose file, a self-hosted metasearch instance, and a `cloudflare-worker/` directory beside it. There is `SOUL.md` at the top level, a `personalities/` directory, a `memory/` directory and a `coordination/` directory, so the identity, memory and multi-agent layers each have a home rather than living inside the runtime.

There is also a directory called `moat/`, whose purpose is not stated in the metadata, alongside `capabilities/`, `evals/`, `security/`, `recipes/` and `integrations/`. A `mcp-config-example.json` at the root is the sample wiring for external MCP servers, and `install.ps1` sits beside an `installer/`, a `packaging/` and a `build/` directory, which is a Windows installer path parallel to the npm one.

The installation itself is three commands:

code
npm install -g aiden-runtime
aiden

Running `aiden` starts the setup flow on first launch, and `aiden web` opens the browser Workbench instead. The last three releases are v4.21.0 on 2026-08-24, v4.21.1 on 2026-09-12 and v4.21.2 on 2026-09-13, and the default branch last moved on 2026-09-13.

Editorial conclusion

Aiden is worth reading if you are building an agent that has to prove what it did rather than report what it believes it did, because the pipeline refuses to treat a successful command or a model saying done as completion, and the artifacts are separated so interrupted work can be reconciled. Three things to check first. The environment file is the control surface and it uses three different prefixes, so confirm which variable a given switch actually reads before you rely on it, in particular the one that disables confirmation prompts. The manifest admits Node 20 and 22 only, which excludes the current line for anything that tracks odd or even majors, so a Node 22 host is the only current choice. And the bundled skill content ships under a second licence file next to the main one, so read both before redistributing anything built with the skills.

Frequently asked questions

What does installing Aiden require?

Node 20 or Node 22, since the manifest allows >=20 <21 or >=22 <23 and excludes everything else, with npm 10.9.8 as the declared package manager. The install is npm install -g aiden-runtime followed by aiden, and running aiden web opens the browser Workbench instead of the terminal setup flow.

How does Aiden stop an autonomous agent running unattended?

Risk-tiered approvals, trust levels, budgets, interruption, scoped permissions, leases and generation fencing are named as the controls, and approval is a stage in the job pipeline between an effect and its execution. The escape hatch is a single setting: DEVOS_AUTO_APPROVE is false by default and its comment says true skips all confirmation prompts for CI and automation.

Can Aiden run without any cloud model provider?

Yes. The environment example states that Aiden works fully offline with only Ollama configured and that all cloud provider keys are optional fallbacks, and the manifest description lists offline Ollama support alongside the hosted provider options.

Official sources

  1. License: AGPL-3.0
  2. Project website
  3. README
  4. Releases
  5. taracodlabs/aiden on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/taracodlabs-aiden.svg)](https://hysenlabs.com/projects/taracodlabs-aiden)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/taracodlabs-aiden.svg)](https://hysenlabs.com/projects/taracodlabs-aiden)

Was this useful?