aos-ce README

The project's README from github.com/unicity-aos/aos-ce. As one markdown file: README.md.

AOS Community Edition

AOS Community Edition is the open agent operating system for people who want an inspectable, composable environment for agents.

It owns the Community Edition product surface: the aos CLI, HTTP API, distributions, first-party capsules, provider and model experience, and Unicity Audit.

Workspace layout

crates/       Product CLI, HTTP API, control client, and shared product code
capsules/     First-party production capsules
distros/      Community distribution manifests and release metadata
docs/         Product and operator documentation

Install

The supported installer installs the aos product command, its pinned runtime, and the exact 22 Community Edition capsules built from this source tree under the product-owned ~/.aos root:

curl --proto '=https' --tlsv1.2 -fsSL https://aos.unicity.ai/install.sh | sh
aos init

aos init, including aos init --offline, provisions from those local, product-versioned capsule assets. A fresh Community installation automatically resumes Astrid's ten-capsule batches after each rate-limit window; installing all 22 capsules includes approximately two minutes of waiting. Completed installs are not repeated, and a stalled batch remains an error. Re-running the installer performs a coordinated product upgrade without rewriting a standalone runtime installation. Every release publishes checksums, Sigstore bundles, GitHub build-provenance attestations, and runtime-compatibility.toml, which pins the exact runtime release and WIT commit. Its machine-readable runtime-compatibility and upgrade/self-heal gates must both be true before a tag can publish. The latter is approved only after the exact candidate preserves a frozen standalone-home clone and boots with freshly generated runtime coordination state.

Command boundary

AOS owns its product roots, including init, status, migrate, update, distro, mcp, daemon, and serve-health:

aos status
aos status --json
aos --principal codex-code mcp serve
aos daemon foreground --workspace /workspace

On Unix, aos daemon foreground replaces the AOS process with the persistent bundled daemon, preserving direct signal and exit-status ownership for process supervisors. On other hosts it waits for the daemon and preserves its exit status. Both paths apply the product-owned runtime home, .aos workspace layout, enforced Community Edition distro, and stderr logging environment. Neither path enables ephemeral lifetime.

Every other runtime root is part of the AOS CLI directly. Arguments, exit codes, and signals pass through unchanged; there is no nested aos astrid or aos runtime namespace:

aos doctor
aos capsule build

When AOS owns a root such as status, init, update, or mcp, its product implementation replaces the lower-level command at that same location. The complete supported surface therefore remains aos <verb>. Release validation compares the exact pinned runtime's public command inventory with AOS's classified root contract, so a new runtime verb cannot enter a product release without an explicit inherit-or-own decision.

aos mcp serve is the product edge shared by Codex, Claude, and Grok. A client that supports MCP form elicitation keeps presenting its own constrained approval forms. When a client does not, the default --interaction auto mode uses a local AOS decision surface: AppKit on macOS, a native Windows dialog, or Pinentry on Linux. --interaction client, native, and deny make the policy explicit. The local bridge accepts only a single boolean or the fixed AOS approval enum; arbitrary strings, password-shaped fields, and URL elicitations are never collected through it.

Build on AOS

Unicity AOS is the operating system in which agents and agent-native software run. Capsules are general user-space building blocks: users can compose them into harnesses, meta-harnesses, connectors, services, or other systems. Community Edition ships Forge as OS construction tooling so a fresh agent can inspect the running system, learn the capsule model, identify a real capability gap, and build and verify a least-privilege capsule. Forge also installs the meta-harness skill, which teaches an agent how to build a governed meta-harness on AOS by treating its instructions, memory, skills, harness code, tools, capsules, traces, and evaluations as an improvable user-space world. The agent is instructed to notice useful extensions during real work and reach for Forge proactively when new code is the right way to improve that world.

See Extending an agent's world on AOS for the world model, research loop, Forge boundary, optional worker pattern, and representative user experiences.

Provisioning another principal keeps the authenticated operator separate from the target environment:

aos --principal operator init --target-principal alice

This AOS release fixes its distribution state to Unicity CE. Use a standalone astrid installation and runtime home to apply another distribution. Homebrew installations update with aos update. Direct installs resolve the signed stable channel by default and can select dev, nightly, or an exact version; all remain fail-closed until their signed metadata is actually published. See Signed AOS release channels.

Import an existing runtime

The aos CLI can deliberately copy compatible state from a standalone runtime installation without changing the source. See Importing standalone runtime state for the exact allowlist, integrity checks, recovery behavior, and command.

License

Except where otherwise noted, AOS Community Edition is dual-licensed under the MIT License or the Apache License 2.0, at your option.

aos-ce (unicity-aos/aos-ce)

Searching Database…

8.5K ·GitHub
这是什么?AOS 社区版是一个开源的“智能体操作系统”,为 AI 智能体提供一个可检查、可组合的运行环境。它以 aos 命令行工具为核心,并包含 HTTP API、预置的 capsule 以及审计工具。
这是命令行工具,还是会取代我电脑系统的真正操作系统?它不是替代系统。它运行在 Linux、macOS 或 Windows 之上,以 'aos' 命令加一个随附守护进程的形式存在,并提供固定的 22 个 'capsule'(模块化的用户空间构建模块)。智能体可以把这些 capsule 组合成 harness、连接器或服务。
哪些编程智能体真正能与它对接?运行 aos mcp serve 会开放一个 MCP 接入端,由 Codex、Claude 和 Grok 共用。如果客户端没有自己的 MCP 审批界面,AOS 会改用原生的本地审批对话框(macOS 上为 AppKit,Windows 上为原生对话框,Linux 上为 Pinentry)。
安装会立即完成吗?不会。全新安装会在每个速率限制窗口之后分批继续安装 capsule,每批十个,因此装齐全部 22 个 capsule 大约需要等待两分钟。如果某一批停滞不前,会被视为错误,而不会被悄悄重试。
Forge 是用来做什么的?Forge 是随社区版附带的系统构建工具。它让智能体能够检查正在运行的系统,找出真实存在的能力缺口,并构建和验证一个最小权限的 capsule 来填补这一缺口。
meta-harness 技能有什么作用?它教智能体如何在 AOS 上构建一个受管控的 meta-harness。智能体需要把自身的指令、记忆、技能、代码、工具、capsule、运行轨迹和评估都视为一个可以持续改进、并随时间不断扩展的世界。
我能从已有的独立 AOS 运行时导入状态吗?可以。aos 命令行工具可以有意地从独立的运行时安装中复制兼容的状态,且不改动源端内容。复制时遵循白名单,并带有完整性校验和恢复机制。
Unicity Audit 是什么?它是社区版产品的一部分,与 aos 命令行工具、HTTP API 以及各分发版本并列。不过 README 并未详细说明其具体的审计机制。
What are similar projects?ruflo, openrig, hyperfide, gitagent, Raven, cynative, newsjack, grok-build
Size
22 MB
Stars
8.5K
Age
3mo
Commits · 90 Days