DEVELOPER PREVIEW

Build with Omnix.

Omnix is a modular Cognitive System for OS-hosted applications and services. Rust owns reusable behavior; Dart bindings make selected capabilities accessible without requiring Rust knowledge. The host retains presentation, consent and OS integration. Its standalone Core module provides the Cognitive Engine for model execution.

01 / GETTING STARTED

Run your first local example

Start from a current source checkout with Flutter, Rust and Windows build tools installed. The root example lets you explore local conversations and the available modules. You will need a compatible local model; follow the example README for model files and build prerequisites.

cd example
flutter pub get
flutter run -d windows

Core runtimes, Storage backends and Nexus protocols are explicitly selected. Rust modules can be consumed independently of their Flutter bindings.

Host app / service
    → Handwritten API (Rust or Flutter binding)
    → Selected Rust modules
    → Native runtime / database / protocol
ONE IMPLEMENTATION, TWO ENTRY POINTS

Native control. Approachable APIs.

Rust developers can use the independent module crates directly or select capabilities through the Omnix facade. You own lifecycle and host integration without depending on Dart or Flutter.

Dart developers can use individual module packages or the composed Omnix API. Both expose the same Rust implementation, including agent orchestration and workflow execution. In a Flutter application, you supply the interface, media capture, permissions and OS integration.

Start with Core for one local model. Add Storage, Knowledge, Workflow or Nexus when the application needs them. Choose Omnix when you want those capabilities composed behind one system API. No account or marketplace is required for standalone use.

The API promise

Choose your capabilities, receive streaming events and control resource lifecycles through explicit APIs. Unsupported operations return clear errors. APIs may change during the developer preview; check the runtime and platform notes when planning your integration.

02 / ARCHITECTURE

Clear contracts, replaceable internals

Host application→Omnix API→Provider adapters→Model runtime

Public Dart contracts are handwritten, so you can use them without working with generated bridge code. Rust-only applications have no Flutter dependency. Omnix composes optional agent capabilities; Core runs models, Workflow manages durable tasks, and Nexus checks remote authority before dispatch.

DEVELOPER GUIDE

Build a Cognitive System

Embed Omnix in your application, service or device. Supply capabilities through public tool definitions and host callbacks, select skill instructions and grant access explicitly. Rust owns the agent loop; your host owns OS integration, consent and the interface. You do not need to understand generated bridge code or internal orchestration.

Use OmnixAgentExtensions to supply tools and skills for the optional agent capability. Tools execute callbacks provided by your host; skills describe how to use them. Skill instructions do not grant device permissions or install executable code. Character profiles and downloadable executable extensions are not currently available.

Build an end-user experience like OmniAsk, or embed Omnix in your own product. If your app accepts resources from Omnies or another catalog, validate their compatibility and request any required permissions in your host. Neither OmniAsk nor an Omnies account is required to embed Omnix.

Integration notes

You can combine media input and tools when your chosen model and runtime support them. Rust handles validation, execution bounds and session state; your host supplies callbacks, storage configuration, permissions and OS services. Background execution is subject to the target operating system's limits.

03 / MODULES

Capability boundaries

Select the capabilities your application needs. Each module can be used independently or combined through the Omnix API.

CoreModel execution, streamed text, cancellation, embeddingsNative preview
StorageSQLite records and Qdrant vectorsNative preview
AgentsOptional root composition: model/tool loop, skills and host callbacksNative preview
WorkflowDurable steps, retry rules, results and recovery; host-owned triggersNative preview
KnowledgeProfile-bound indexes, attributed retrievalNative preview
NexusPaired A2A access; experimental MatterExperimental
PLATFORM ROADMAP

Beyond the current native integrations.

Linux and browsers are future OmniAsk targets. Planned browser integrations include JavaScript or WebAssembly model runtimes, with LiteRT-LM and llama.cpp as candidate paths, plus browser-compatible storage and networking.

A browser app is the first web milestone; an extension for browser automation is a later direction. iOS, macOS and Safari are also on the roadmap. These integrations are not yet available as supported end-to-end targets.

Nexus can also connect systems that do not embed the rest of Omnix. We are exploring Rust libp2p for connectivity across consumer networks, alongside A2A messaging and local access controls. libp2p is not currently integrated.

04 / RELEASE STATUS

What the preview means

Omnix now powers OmniAsk. You can explore local inference, streamed agents, host tools, knowledge retrieval and durable workflows through its developer-preview APIs. Feature availability depends on your model, runtime, device and host integration.

AndroidLiteRT-LM powers the current OmniAsk integration, including compatible Gemma image/audio input and host tools. OS permissions and background limits still apply.Product integration
WindowsTry native examples for LiteRT-LM and llama.cpp text generation, persistence and retrieval. Model and accelerator compatibility varies.Native examples
CPU / GPUSelect a backend where your runtime supports it. GPU availability and performance depend on your device. General NPU support is not yet available.Device-dependent
Other targetsiOS, macOS, Linux, web and embedded integrations are not currently supported end to end. Follow the platform roadmap for future availability.Future integrations
NexusExplore A2A exchanges and experimental Matter controller adapters. Production networking and smart-home integrations are not yet available.Experimental
Plan your integration

Find build prerequisites, runtime compatibility notes and tested configurations in the repository. Explore the technical documentation.