ARCHITECTURE / PRE-ALPHA

A shared language between agents.

Explore how independently controlled systems can collaborate through A2A. The current implementation is available through Omnix Nexus, with no separate Omnixus runtime required. Production device onboarding, key management and cross-network connectivity are still in development.

A REUSABLE GATEWAY, NOT A CLOSED CLUB

Nexus can serve systems beyond Omnix.

Omnix Nexus is an independently usable Rust crate with a Dart API. A system can adopt it without importing Omnix Core, the full Omnix composition or OmniAsk. An independent implementation can also speak A2A directly; using Nexus is one integration path, not a membership requirement.

A2A defines the work exchanged. Nexus connects it to local capabilities and authority checks. Omnixus develops the wider collaboration conventions; a reachable address or peer identity does not automatically grant access to knowledge or devices.

01 / IDENTITY

Who are you talking to?

Authentication establishes who is requesting access. The local demo uses a token; persistent identity and device pairing are being developed for connections between trusted nodes.

02 / EXCHANGE

What is being delivered?

A2A provides messages, long-running tasks, status updates and result artifacts. Your system can exchange requests and results through an existing agent interface.

A message carries a request, not permission to act on it.

03 / POLICY

Who decides?

The receiving node checks what a caller may access before returning a result. Permission to request knowledge does not grant permission to run tools or control devices.

The current demo supports public-data exchanges and refusals. Remote device actions are not currently available.

TRY IT

Watch an A2A exchange in two terminals.

The client discovers the server's Agent Card, sends a question over A2A JSON-RPC/HTTP, and receives a completed task with an answer artifact. The server requires a random local demo token and rejects requests without it.

OMNIX/RUST · SERVER
cargo run --features nexus --example two_agents -- serve
OMNIX/RUST · CLIENT
$env:OMNIXUS_DEMO_TOKEN = "<token printed by server>"
cargo run --features nexus --example two_agents -- ask "What is Omnixus?"

Run these commands from Omnix's rust directory. Stop an older server with Ctrl+C before rebuilding. Ask "private note" with the same token to see a synthetic refusal. The two-laptop HTTPS demo worked in both directions over a private route. The copied token is not secure pairing; paired-key mode still needs two-device validation. No LLM or real private data is involved.

DESIGN RECORD

Read the work as it develops.