← Back to main page

Download Agent OS

Distributions for running without source code: compiled binaries, documentation, skill playbooks, starter config, and environment template — separate archives for Windows and Linux.

Download

Platform	Archive	Size	SHA-256
Linux (x86_64)	`agent-os-distrib-linux.zip`	≈ 45.5 MB	SHA-256
Windows (x86_64)	`agent-os-distrib-windows.zip`	≈ 30.3 MB	SHA-256
Android	`agent-os-android.apk`	≈ 9.1 MB	SHA-256

Downloads support resuming (HTTP Range): if the connection drops, continue from the same point — curl -C - -O <ссылка> or wget -c <ссылка>.

The Android app is an Agent OS chat client: a list of agents, their greetings, and communication via the HTTP API. To install, download .apk to your device, open it, and allow installation from unknown sources when the system prompts you. By default, the app connects to the platform's demo server; the address of your own server (and the token, if authorization is enabled) is set in the app's settings.

Archive contents

File	Purpose
`bin/agent-os[.exe]`	Unified CLI. Subcommands: `serve` (HTTP server: website, widget, API, proxy, admin UI), `bench`, `scrape`, `hook`, `route`, `tool`, `office`, `module` (`module workflow run`), `pdf-exporter`, `mcp-fake`. Subcommands are extensible via modules.
`bin/officecli_pdf_exporter[.exe]`	PDF exporter plugin OfficeCLI (thin shim on `agent-os pdf-exporter`; must be located next to `agent-os`)
`bin/libduckdb.so` / `bin/duckdb.dll`	DuckDB runtime — must be located next to the binaries
`config/`	Starter config: `server.yaml`, `budgets.yaml`, demo agents `hello-agent` and `mcp-demo-agent`
`docs/`	Playbook on setting up the server and creating agents (without source code)
`skills/`	Skill playbooks for agents (`SKILL.md` folders)
`.env.example`	Environment variables template
`VERSION`	Build version

Quick start

Run the server from the root of the unpacked archive: config/ and .env are looked up relative to the current folder.

Linux:

unzip agent-os-distrib-linux.zip
cd agent-os-distrib
cp .env.example .env        # откройте .env и укажите DEEPSEEK_API_KEY
./bin/agent-os serve        # http://127.0.0.1:3000

Windows:

powershell -Command "Expand-Archive agent-os-distrib-windows.zip ."
cd agent-os-distrib
copy .env.example .env
notepad .env
bin\agent-os.exe serve

Local testers are subcommands of the same binary: agent-os tool <tool.yaml> '<json>', agent-os hook <hook.yaml> user "hi", agent-os bench --port=3001 --max=3, agent-os scrape <url>. Running a workflow is now agent-os module workflow run <workflow.yaml> (formerly workflow_tool).

In .env, specify DEEPSEEK_API_KEY. Without a key, the server will still start, but agents respond with simulated answers.

After starting, open http://127.0.0.1:3000/widget?model=hello-agent — this is the widget with the demo agent from the starter config. Next — docs/README.md inside the archive: configuring the provider, budgets, and authorization, creating agents, tools, hooks, and scripts (JavaScript/Rhai).

The starter config has no markdown site, so /site/ responds with 404 until you add config/web/ (see "Web content (site)" in the documentation).

What gets downloaded on first use

Some optional features download their own runtime on first use (internet access required): ONNX Runtime and models (security.onnx), OfficeCLI (office_tool), headless Chromium (PDF export, browser_tool). The demo agent mcp-demo-agent requires Node.js (npx in PATH).

For developers with source code

Archives are built by scripts in scripts/:

Linux — ./scripts/build_distrib.sh (on a Linux server);
Windows — powershell -File scripts/build_distrib.ps1 (on a Windows machine).

The script compiles all binaries (cargo build --release --workspace), packages them together with agent_os_docs/ (as docs/) and .agents/skills/ (as skills/) into distrib/ and writes the SHA-256. On the server, the Linux archive is updated automatically on every deploy.