A new category

Open Aya — a project-native intelligent browser that remembers your work and keeps your data portable.

The browser is the workspace. Aya is the operating system. Projects are the filesystem. Memory is persistent. Capabilities are invisible services. Evidence is the trust layer. A category neither a chat app nor a browser fully occupies.

Work is organized around objectives you can leave and return to — full context restored from your projects, not a chat scrollback. 43 capabilities run as invisible services, routed across planner, executor, memory, verifier, and critic strategies — every step auditable through a public evidence harness, not a brochure.

The browser: is the workspace.
Aya: is the operating system.
Projects: are the filesystem.
Memory: is persistent.
Capabilities: are invisible services.
Evidence: is the trust layer.

Open Aya OS

Intelligence Card

Live system facts. Every number on this card is generated at request time from the runtime registry or the public eval database — there is no separate marketing source to drift.

Live

Model layer

anthropic/claude-sonnet-4.6 (conversation tier)
anthropic/claude-opus-4.6 (extended thinking, 10k budget)
google/gemini-3-flash (multimodal)
anthropic/claude-opus-4.6 (SWE-Bench leader)

Agent layer

6 routed strategies: planner, executor, memory_retriever, verifier, router, self_critic

Strategy-Auction routing implemented as system-prompt routing rules

Memory layer

Supabase + browser IndexedDB (local-first)

Kinds: short-term turn cache · long-term background consolidation · GraphRAG knowledge edges

Tool layer

6 built-in tools across 43 apps

Web search · Code execution (Code Lab) · File store (Spatial Files) · Calendar / Notes / Word Processor · …

Local-first status

Browser storage supports guest and offline-capable features; AI and connected services may use remote APIs

Cloud sync status

Supabase persists supported account, project, conversation, and vault records when signed in

Apps in registry

Generated from lib/app-registry.ts

Routed agents

Strategy-auction policies, system-prompt routed

Eval score (avg)

29.6%

Across 79 completed runs

Last eval run

Aug 27, 2026, 04:01 AM

UTC server time

Avg latency / task

2,329ms

Wall-clock, includes network hop

Audit mode

Public — every eval result writes a reasoning trace to /api/aya/inspect and aggregates to /api/aya/audit

A/B comparison — pass rate by route

baseline

—

Claude Sonnet 4.6, no spine (control)

aya_pipeline

—

Claude Sonnet 4.6 + 7-stage cognitive spine

aya_reasoner

—

Claude Opus 4.6, extended thinking (10k)

What you can verify, right now, without an account.

Public eval API. /api/evaluate accepts a prompt and returns the canonical result shape (task_id, category, answer, agents_used, confidence, latency_ms, cost_estimate, memory_used, audit_trace).
Public status JSON. /api/aya/status lists every capability flag with an honest functional / claimed marker — no inference required.
Public audit aggregates. /api/aya/audit publishes the A/B verdict between baseline Claude Sonnet 4.6, Aya's 7-stage cognitive pipeline on anthropic/claude-sonnet-4.6, and the anthropic/claude-opus-4.6 reasoner (extended thinking, 10k budget) across all completed runs.
Three live demos. Reasoning, memory, and agent routing run a canned task end-to-end and show the full reasoning trace.
No claim without a receipt. Every superlative on this site links to a reproducible run with a JSON trace. Where data isn't available yet, we say so plainly instead of rounding up.

What we are not yet, and how you'll know when we are.

Open Aya OS is not AGI and does not claim to be. ARC-AGI alignment refers to architecture (multi-strategy reasoning, verifier loops, cost-per-task accounting) — not to a published score.
The strategy auction is currently implemented as deterministic system-prompt routing rules, not as six independent learned policies. The /eval harness measures the lift this routing actually provides over a Claude Sonnet 4.6 baseline running the same conversation tier without the cognitive spine — so the A/B delta isolates the wrapping, not a model upgrade.
“Self-improving” refers to per-user memory consolidation (Auto-Dream) and TinyAdapter parameter drift, not to weight updates of the underlying base model.
Pass rates on /receipts are computed from real, persisted eval runs. If a tier shows “no data”, no run of that tier has completed yet.

OpenAyaEnter the beta

A working AI OS in the browser · Beta

Your operating system is becoming intelligence.

Aya is an objective-first AI operating layer that runs in the browser—so your workspace, context, tools, and governed memory can meet you anywhere a browser can run.

Enter the beta See how Aya works

Attention held

ObjectiveContextBounded actionReceipts

Available in this buildA working AI OS in the browser In active developmentConnected functions are being hardened Direction, not a promiseA cloud OS available through any capable browser—on any machine

Open source · Human governed · BetaScroll to explore

The OS moves to the cloud

The browser is no longer just where software is viewed. It is becoming the portable surface where an intelligent operating layer can live.

Not another chatbot. A whole working environment, available wherever the web is.

Operating layer

Begin with an objective, not an app

Aya organizes work around what you intend, then brings conversation, files, tools, and next actions into one coherent workspace.

Continuity

Your context moves with you

The durable layer lives beyond a tab. Governed memory and portable files let Aya resume the work wherever you securely sign in.

Interface

The browser becomes the computer

Text, voice, tools, and visible system state meet in one interface that can run anywhere a capable browser can run.

Where Aya stands

Useful now. Unfinished by design.

This build is both a working product and a hypothesis made visible. We are publishing the functioning pieces now so the design, limits, and principles can be evaluated while the system develops.

Available in this build01

A working AI OS in the browser

The current build brings objectives, context, conversation, tools, and bounded action into one browser-delivered operating environment you can enter now.

Inspect current capabilities

Objective-first workspace and projects
Chat, inspectable context, approvals, and receipts
Voice where browser support and permissions allow
Operator and Data Vault surfaces where configured

In active development02

Connected functions are being hardened

Memory, tools, voice, Operator, and external data connections exist at different levels of maturity. Their behavior can change as reliability and governance improve.

Read the beta status

Some functions require an account or connected provider
Tool use remains permission- and deployment-dependent
Voice depends on browser, microphone, and speech services
Interfaces and system behavior will continue to evolve

Direction, not a promise03

A cloud OS available through any capable browser—on any machine

Aya's direction is a device-agnostic operating layer delivered through the web: governed context, tools, and continuity that can meet a person wherever they securely sign in.

Follow the direction

Browser-delivered and cloud-based
Portable, attributable context
Continuity across devices and sessions
A software environment—not a hardware dependency
No Aya hardware product has been announced

The browser is not the limitation. It is the distribution model.

As AI settles into the computing stack, the operating system can become cloud-based and browser-delivered: one governed environment that follows you across laptops, phones, tablets, shared machines, and whatever comes next.

Aya starts there now. The current beta is a real browser workspace; seamless continuity across every device and deployment remains an active direction, not a finished claim.

Power should remain legible.

Aya is designed around a simple belief: capable intelligence should increase your agency, not quietly replace it.

Context you can inspect

Aya shows what she knows, what she inferred, and what shaped the answer.

Permission before action

Tools and data access remain bounded by the authority you explicitly grant.

Work with receipts

Important actions leave a trail you can review instead of disappearing into a black box.

Try the current build

Bring an objective.
Test the possibility.

Enter the working beta through Aya's system initialization. Expect a real workspace, evolving behavior, and functions whose availability depends on your account, permissions, browser, and connected services.

Enter the beta

OpenAyaEnter the beta

A working AI OS in the browser · Beta

Your operating system is becoming intelligence.

Aya is an objective-first AI operating layer that runs in the browser—so your workspace, context, tools, and governed memory can meet you anywhere a browser can run.

Enter the beta See how Aya works

Attention held

ObjectiveContextBounded actionReceipts

Open source · Human governed · BetaScroll to explore

The OS moves to the cloud

The browser is no longer just where software is viewed. It is becoming the portable surface where an intelligent operating layer can live.

Not another chatbot. A whole working environment, available wherever the web is.

Operating layer

Begin with an objective, not an app

Aya organizes work around what you intend, then brings conversation, files, tools, and next actions into one coherent workspace.

Continuity

Your context moves with you

The durable layer lives beyond a tab. Governed memory and portable files let Aya resume the work wherever you securely sign in.

Interface

The browser becomes the computer

Text, voice, tools, and visible system state meet in one interface that can run anywhere a capable browser can run.

Where Aya stands

Useful now. Unfinished by design.

This build is both a working product and a hypothesis made visible. We are publishing the functioning pieces now so the design, limits, and principles can be evaluated while the system develops.

Available in this build01

A working AI OS in the browser

The current build brings objectives, context, conversation, tools, and bounded action into one browser-delivered operating environment you can enter now.

Inspect current capabilities

Objective-first workspace and projects
Chat, inspectable context, approvals, and receipts
Voice where browser support and permissions allow
Operator and Data Vault surfaces where configured

In active development02

Connected functions are being hardened

Memory, tools, voice, Operator, and external data connections exist at different levels of maturity. Their behavior can change as reliability and governance improve.

Read the beta status

Some functions require an account or connected provider
Tool use remains permission- and deployment-dependent
Voice depends on browser, microphone, and speech services
Interfaces and system behavior will continue to evolve

Direction, not a promise03

A cloud OS available through any capable browser—on any machine

Aya's direction is a device-agnostic operating layer delivered through the web: governed context, tools, and continuity that can meet a person wherever they securely sign in.

Follow the direction

Browser-delivered and cloud-based
Portable, attributable context
Continuity across devices and sessions
A software environment—not a hardware dependency
No Aya hardware product has been announced

The browser is not the limitation. It is the distribution model.

Aya starts there now. The current beta is a real browser workspace; seamless continuity across every device and deployment remains an active direction, not a finished claim.

Power should remain legible.

Aya is designed around a simple belief: capable intelligence should increase your agency, not quietly replace it.

Context you can inspect

Aya shows what she knows, what she inferred, and what shaped the answer.

Permission before action

Tools and data access remain bounded by the authority you explicitly grant.

Work with receipts

Important actions leave a trail you can review instead of disappearing into a black box.

Try the current build

Bring an objective.
Test the possibility.

Enter the beta

Open Aya

What you can verify, right now, without an account.

What we are not yet, and how you'll know when we are.

Your operating system is becoming intelligence.

Not another chatbot. A whole working environment, available wherever the web is.

Begin with an objective, not an app

Your context moves with you

The browser becomes the computer

Useful now. Unfinished by design.

A working AI OS in the browser

Connected functions are being hardened

A cloud OS available through any capable browser—on any machine

The browser is not the limitation. It is the distribution model.

Power should remain legible.

Context you can inspect

Permission before action

Work with receipts

Bring an objective.Test the possibility.

OpenAya OS

Your operating system is becoming intelligence.

Not another chatbot. A whole working environment, available wherever the web is.

Begin with an objective, not an app

Your context moves with you

The browser becomes the computer

Useful now. Unfinished by design.

A working AI OS in the browser

Connected functions are being hardened

A cloud OS available through any capable browser—on any machine

The browser is not the limitation. It is the distribution model.

Power should remain legible.

Context you can inspect

Permission before action

Work with receipts

Bring an objective.Test the possibility.

Bring an objective.
Test the possibility.

Bring an objective.
Test the possibility.