Giving everyone a team of agents. AI as a team, not a tool.

Everyone is building an AIOS. We built The AIOS.

the-aios.com — the live site (EN · ES · PT) · Operating Manual — read it online or take the PDF: first principles through to 24/7 containment.

For anyone navigating AI-overwhelming days — senior executives, builders, founders, operators. AI alone multiplies confusion. The AIOS gives you the structure where clarity emerges, then allows you to amplify yourself and your team with AI co-workers.

The journey feels like: Prompt → Context → Intent → Collaboration → Second Brain → AI Company. AI moves from tool to assistant to your full team. Human moves from prompter to first-brain, to orchestrator.

If you want to make the most of AI without losing what makes you irreplaceable — and without IP/PII risk — this is for you.

Used daily by senior executives, founders, builders, and operators — on personal vaults, ventures, and the work that ships.

The AIOS turns AI into a team — a legal you, an accountant you, a marketing you, a software engineer you. You can run them all and be their orchestrator, or let one AI co-worker run the rest as your chief of staff who never sleeps and absorbs the coordination overhead with the best agentic culture.

The AIOS exists to make you and your team exponential, to give you the bandwidth you need and move at the speed the era demands. It is not here to replace anyone but to compound everyone, leveraging as many specialized co-workers as you need.

Each stage builds on the last. Each next stage returns ~10× the leverage.

• Week 1: Automate — Gain speed, do faster. Daily plans, drafts, syntheses — 30 minutes becomes 30 seconds.
• Week 2: Amplify — Gain bandwidth, do more. Agents draft proposals, write in your voice, research while you sleep — you stop being the bottleneck.
• Month 1: Agency — Gain autonomy, do agentic. AI co-workers act on your behalf with judgment, within trust boundaries you've defined.

• Amplify intelligence, not artificial. Human + AI beats human alone or AI alone.
• Context, not prompts. Prompts are the artifact most people optimize. Context is the substrate that determines what those prompts can do.
• Trust earned over time. Autonomy compounds with judgment — like a good A-Player on a real team.
• Portable, not proprietary. The AIOS is the layer; the LLM is interchangeable. Plug Claude (recommended), Gemini, or your best model.

Three things you install, two things you read, and one that quietly sets the rules.

• aios — the framework, and the place to start. A vault plus the machinery around it: 20+ slash commands for the daily rituals, 30+ task agents across six bundles, 40+ skills, bundled MCP servers, and hooks that give every session a real clock and a live context readout. Path-agnostic install at ~/aios/. GPL-2.0-or-later.
  • company-template — the venture-context scaffold, forked via /aios:company --create. One mount, and every teammate's Claude session inherits the same context layer: who the company is, what it sells, how it decides. Optionally carries company-specific agents, plugins, hooks, MCPs, skills and templates.
• aios-glass — for people who work in an editor. A glass layer over the framework for Google Antigravity or any VS Code-compatible editor: rituals as buttons, agents you can browse and spawn, /company and /collaborate spaces, vault navigation. The terminal becomes optional rather than required. On Open VSX; pairs with Foam for [[wikilink]] navigation. GPL-2.0-or-later.
• aios-app — for everyone. The same control plane as a standalone Mac app: Home, a live panel, real claude sessions in real terminals, a vault explorer with git markers, viewers for markdown/HTML/PDF — and a four-step setup that takes a machine with nothing installed to a working AIOS without opening a shell. A Developer-ID-signed, notarized .dmg with signature-verified auto-update. GPL-2.0-or-later.

Glass, not engine holds across both surfaces: they run the real claude CLI against your real vault, surfacing and triggering what the framework already does — never reimplementing it. And app-only is a first-class topology, not a lesser one: no editor required.

• site — the-aios.com, the web-native sibling of the Operating Manual. A guided walk from what it is through architecture, toolbox, rhythm, trust and containment — trilingual (EN · ES · PT), with the manual embedded at /manual. Next.js + Tailwind, static export. MIT.
• org — the-aios.org, the commons and marketplace surface. The root is the home of the open framework, its license and its name; /plugins is where the ecosystem's plugins, credentials and extensions live, and where vendors and coaches set up shop. Branded placeholders today.

• .github — the org-level community health files, which inherit as defaults to every repo here: CONTRIBUTING (the custom/ rule, commit and CHANGELOG format, GPL-2.0-or-later inbound terms, the anti-personal-content discipline), SECURITY, issue and PR templates. Anonymized and operator-agnostic by design — a repo overrides these only when it has something genuinely specific to add.

CI on the framework runs a multi-job validation gate on every PR — repo structure · plugin manifests · YAML frontmatter · capability counts · migration drift · personalization hygiene — so a broken contribution fails before review rather than after merge.

Amplify yourself and your team — with AI co-workers. Not zero people. Compounded people.