An offline-first, open-source AI Operating Environment.
Aidos is a headless runtime that brings AI agents and tools under your complete control. Run AI models locally, manage projects and goals, execute tools (Git, shell, custom plugins), and organize output—all on your device, with privacy by default.
Aidos is a smarter, AI-aware replacement for your terminal, IDE, and knowledge base combined. It:
- Runs offline — Full capability without internet; cloud is optional.
- Respects privacy — Your data stays on your device by default.
- Gives you control — Fine-grained permissions; you decide what each agent can do.
- Integrates everything — Git, shell, filesystem, HTTP, custom tools via plugins.
- Reasons and plans — AI engines for language, embeddings, voice, and vision.
- Organizes your work — Track goals in an editable Intent Graph; sessions run to accomplish them.
- Understand the architecture: Read ARCHITECTURE.md (2–4 pages). It's a map to the RFCs and explains how the engines fit together.
- Dive into RFCs: Read individual RFCs based on your interests (see ARCHITECTURE.md for recommendations).
- Contribute or use: See CLAUDE.md for development practices and ways to help.
I want to use Aidos: → See RFC-0050: Android or RFC-0051: Desktop for UI plans. → RFC-0099: Roadmap shows what's coming.
I want to write plugins/extensions: → RFC-0060: Plugin SDK.
I want to contribute to core: → RFC-0002: Runtime Architecture. → CLAUDE.md for development practices.
I want to understand the philosophy: → RFC-0000: Vision. → RFC-0001: Principles.
Projects — Git repositories with an Intent Graph (goals), Resources (docs), and Artifacts (outputs).
Sessions — Long-lived agents that run in a project. Each has permissions and can accomplish goals.
Intent Graph — Editable, persistent representation of what you want to achieve (not implementation details).
Tools — Git, shell, filesystem, HTTP, custom plugins. Unified interface through Tool Broker.
AI Engine — Supports LLMs, embeddings, voice, vision. Runs locally by default; cloud is optional.
Knowledge Engine — Synthesizes understanding from your project files, docs, and history.
See ARCHITECTURE.md for the full picture.
Project overview:
- ARCHITECTURE.md — Map to the RFCs; start here.
- docs/README.md — Documentation structure.
- docs/principles.md — Ten core principles.
- docs/vision.md — Mission statement.
- docs/roadmap.md — Index into the three levels of plan.
- docs/decisions.md — Why the architecture is this and not something else.
RFCs (62):
- All architectural decisions documented as RFCs in docs/rfcs/.
- See docs/rfcs/README.md for RFC process and index.
Repository:
docs/— Documentation, RFCs, architecture.ARCHITECTURE.md— This document's bigger sibling; navigation guide.CLAUDE.md— Development practices, contributor guidelines, AI assistance info.
License: Aidos is licensed under the European Union Public Licence (EUPL-1.2). This is a strong copyleft license compatible with GPL. You're free to use, modify, and distribute Aidos, with the requirement that modifications remain open source.
See LICENSE for full details.
We welcome contributions: code, RFCs, documentation, plugins, ideas.
- Read CLAUDE.md — Development practices and contribution guidelines.
- Read relevant RFCs (see ARCHITECTURE.md for navigation).
- Open an issue or PR on GitHub.
For AI-assisted development, see CLAUDE.md.
Current phase: Phase 0 (Contracts) complete as of 2026-08-03. Phase 1 (Execution kernel) not yet started.
Phase 0 produced three checkable artifacts rather than prose: schema/ — 53 tables
of canonical DDL, validated in CI; agent/kernel/ — the KMP contract surface,
compiling with contract tests and no implementations; and
docs/decisions.md — 24 architecture decisions with none open. 45 of the
62 RFCs are Accepted; what remains Draft is deliberate and listed in
docs/rfcs/README.md.
No feature implementation exists yet. That is the accurate statement, and the roadmap is ordered so it stays accurate rather than optimistic.
- RFC-0099: Roadmap — the phases and why they are in that order
- MVP roadmap — the ordered work breakdown, with gates
- PIPELINE.md — the roadmap: what is open and what is next
- lessons.md — what the project learned the hard way
- Architecture questions: See ARCHITECTURE.md.
- RFC questions: Read the relevant RFC(s) in docs/rfcs/.
- Development questions: See CLAUDE.md.
- Open issues: GitHub issues (coming soon).
Next: Read ARCHITECTURE.md to understand how everything fits together.