Distribution

🔵 Assembled archive with binaries and documentation — for working without source code.

17.1 What's inside

Path	What it is
`bin/agent-os[.exe]`	unified CLI. Subcommands: `serve` (HTTP server + site + widget + API), `bench`, `scrape`, `hook`, `route`, `tool`, `office`, `module` (`module workflow run`), `pdf-exporter`, `mcp-fake`. Subcommands are extensible by modules (registry `agent_os_cli`)
`bin/officecli_pdf_exporter[.exe]`	PDF exporter plugin for OfficeCLI (headless Chromium, auto-download); thin shim over `agent-os pdf-exporter`, must be placed next to `agent-os`
`bin/libduckdb.so` / `bin/duckdb.dll`	DuckDB runtime (Linux / Windows) — must be placed next to the binaries
`docs/`	playbook (`agent-os-docs/`) — configuration, agents, tools, hooks
`skills/`	skill playbooks for agents (`.agents/skills/*/SKILL.md`)
`config/`	starting config tree (server.yaml + budgets.yaml + demo agents `hello-agent` and `mcp-demo-agent`)
`config/plugins.yaml` (optional)	list of native plugins (DLLs) loaded at startup
`.env.example`	environment template
`VERSION`	version
`README.md`	brief memo about the archive

Some optional features download their 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 needs Node.js (npx in PATH).

The server is modular: features (docs, widget, cron, workflow, channels, …) are modules that can be enabled (server.yaml → modules.enabled) and extended with your own (linked crate or native DLL). Native DLLs are placed next to the binaries and listed in config/plugins.yaml; by default the archive does not contain them. See 20-native-plugins and 32-building-a-module.

17.2 Building

Archives are built by scripts in scripts/:

./scripts/build_distrib.sh — Linux (distrib/agent-os-distrib-linux.zip);
powershell -File scripts/build_distrib.ps1 — Windows (distrib/agent-os-distrib-windows.zip).

The scripts build release binaries, package agent_os_docs/ as docs/, .agents/skills/ as skills/, config-starter/ as config/, plus .env.example and VERSION, and compute .sha256.

17.3 Downloading

Archives are served by the server itself:

URL	What
`/distrib/agent-os-distrib-linux.zip` (+`.sha256`)	Linux
`/distrib/agent-os-distrib-windows.zip` (+`.sha256`)	Windows
`/distrib/agent-os-android.apk` (+`.sha256`)	Android

On the site — the "Download" section (/site/download.html). The path to the distribution folder is changed via AGENT_OS_DISTRIB_DIR (default distrib).

Files are served as a stream and support resumption (HTTP Range, response 206): curl -C - -O <url> or wget -c <url> continue an interrupted download.

The Linux archive is rebuilt on the server on every deploy. The Windows archive and APK are built on the developer's machine and published by steps scripts/deploy.sh (the APK — if a fresh build of distrib/agent-os-android.apk is present nearby).

17.4 Quick start from the archive

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

cp .env.example .env        # укажи DEEPSEEK_API_KEY
./bin/agent-os serve

copy .env.example .env
notepad .env
bin\agent-os.exe serve

Local testers — 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 — agent-os module workflow run <workflow.yaml> (formerly workflow_tool).

Then open http://127.0.0.1:3000/widget?model=hello-agent — the widget with the demo agent. Details — in 02-quickstart. The starting config has no config/web/, so /site/ returns 404 until the site is added.