Work keeps dying at the seam.

The problem we're building against

Design happens in one tool, code in another, and the coordination somewhere else again. Every time work crosses a boundary it is exported, re-pasted and re-explained — and something goes missing each time: a convention, a decision, a reason the next tool has no way of knowing.

Three studios, one shared project

airis OS is built around one project that three studios share:

• Design Studio — chat with a design agent, ship UI with brand systems enforced, live preview while you iterate. This is the studio in active use today.
• Code Studio — a deep coding agent workspace with editor, terminal, plan mode, and diffs, turning a design into a real, working application. In development.
• Team Workspace — brief a leader agent and watch designer and coder teammates work in parallel, with live per-agent status. In development.

Because all three studios operate on the same project, moving work between them is a handover, not an export. Decisions, conventions, and preferences travel with the work.

The handover vision

The canonical path we're building toward: design a dashboard, hand it to Code Studio, dictate the behavior, and get back a real application — not a mock. No re-exports, no re-briefing, nothing lost at the seam. Project memory keeps every agent aligned on decisions, conventions, and preferences for that project specifically, distilled rather than dumped.

Local-first, BYOK philosophy

airis OS is local-first — your project and its memory live on your machine — and BYOK: bring your own API key, or use an agent CLI subscription you already have (Claude Code, Codex, Gemini CLI, and others). No fake lock-in, no telemetry by default, no cloud dependency to get work done.

What's next

Design Studio is live. AirisCode and AirisWorkteams — the code and team-orchestration studios — are actively in development. We're posting concrete, dated updates on the blog and releases pages as they ship, rather than promising a roadmap we can't commit to.