Extensions

AI OS extensions are reviewed, compile-time product modules. They can add routes, navigation, data transforms, and local workflows, but they are not downloaded from a remote marketplace at runtime.

Shipped extensions

Extension	Purpose	Runtime data mode
Trend Finder	Public-source trend intelligence for creators	Collector-backed extension data
AI Rogue	Browser-local roguelike progression	Browser-safe host data plus local game state

Trend Finder and AI Rogue share the AI OS shell but do not share a product contract. Trend Finder owns evidence, sources, scoring, Creator Lens, Watchlist, Brief, and Engine Replay. AI Rogue owns deterministic gameplay, Insight Shards, saves, settings, progression, and local media.

Registration and loading

An extension is registered in source code with a stable ID and a declared set of routes and capabilities. Heavy view code is lazy-loaded so a user who never opens an extension does not pay its full browser cost.

The extension registry does not evaluate downloaded code, install packages, or grant capabilities dynamically. New capabilities require a reviewed code change, matching documentation, and focused validation.

Two data modes

Collector-backed extensions expect their own validated extension item. Trend Finder uses this mode because its public-source collection, scoring, and run provenance belong to the extension.

Host-data extensions can derive bounded state from the AI OS browser data that already exists. AI Rogue uses this mode and does not need an AI Rogue collector item. Its wallet, ledger, preferences, run history, and saves remain inside the browser.

Public demo boundary

The static demo includes reviewed extension states. It does not run Trend Finder collectors or expose local action routes. AI Rogue can run as a browser-local experience because it needs no hosted write service or private machine access.

Continue with the Trend Finder workflow or the AI Rogue gameplay guide.