AXION DYNAMIX PRESENTS · Planned

Axion Dynamix AI Browser

A browser that acts on your behalf — research, forms, purchases, monitoring — with the Axion Dynamix AI OS as its memory and judgement, and every action shown to you before it runs. This page describes a product in design. Nothing here is shipped yet; the status badges are the truth.

The benchmark we have set ourselves

Fellou is the agentic browser to beat — it is very good, and we say so. Our bar is not parity; it is a browser whose agent has long-term memory, computed confidence and a reviewable action log, because those are the parts of the AI OS that already exist and are tested.

Remembers

Sites, preferences, half-finished tasks and the reasons behind past decisions persist across sessions through the AI OS memory store — not a chat history, a model of your work.

Deliberates

Multi-step tasks run through the same council as the IDE: strategy, research, blueprint, then execution with a Verifier that checks outcomes against evidence on the page, not the agent's claim.

Shows its hands

Every click, form field and purchase is proposed first and logged after. Spending and credential use are gated by the AI OS permission system; nothing silent, nothing irreversible without you.

Architecture — stated honestly

A browser engine is tens of millions of lines of C++; nobody rewrites one. What we build in Rust is everything around the engine: the shell, the agent runtime, the action layer, memory, permissions and the sidebar. The engine is the WebKit that macOS already ships and patches (WKWebView, through the Apache/MIT wry embedding) — zero engine download, sites render as they do in Safari. Chromium embedding (CEF) is a tracked alternative if a feature ever needs it, not a promise.

Shipped (in AI OS)

Memory, cortex, permissions

The cognitive substrate the browser will use already exists and is tested in Axion Dynamix AI OS.

Shipped (in IDE core)

Council · Implementer · Verifier

The hierarchical agent runtime is shared with the IDE (27 tests) and will drive browsing tasks.

In build

Rust shell on system WebKit

Engine decision made and spiked: window + WKWebView + page↔agent IPC bridge compiles from this tree. Tabs, sidebar panel and action overlay are next.

Planned

Action layer

DOM-grounded actions (click, type, select, navigate, extract) with pre-execution review and a replayable log.

Planned

Pricing & tiers

Announced at launch; AI OS subscribers will receive a bundle price as with the IDE.

Register interest

No payment, no commitment. We will write once when there is something to download and once when pricing is set. Register by e-mail

Questions

Is this a browser engine rewrite in Rust?

No, and any product claiming that would be misleading you. The engine is the system WebKit; the shell, agent, memory and action layers are ours in Rust.

When?

After Axion Dynamix AI OS and AI IDE reach production on macOS. The agent runtime and memory are already built; the browser shell is not.

Will it beat Fellou?

That is the goal we have set and the standard we will measure against publicly when there is a build. We will not claim it before then.