PROJECT STATUS / PRE-ALPHA

Small working steps toward a much larger idea.

Omnixus uses A2A for agent exchange. A public-answer demo has worked on two laptops through an external private route; durable pairing and production networking are still open.

01
Implemented in Omnix

A2A knowledge adapter

Omnix Nexus hosts the A2A code and a two-process localhost demo. Its executor re-verifies the caller before a public-data response.

02
Demonstrated

Two-laptop A2A exchange

A public-answer demo worked in both directions over a private HTTPS route. Tailscale carried requests; it is not an Omnixus protocol dependency. A successful demo is not a generally available network service.

03
Next

Device pairing

Paired-key authentication works in local tests. Cross-device validation, secure onboarding, key management and revocation are the next steps toward connecting devices you trust.

04
Research

Interoperability

The goal is collaboration between Omnix and independent A2A systems. Developers can use standalone Nexus or implement A2A directly, without importing the full Omnix system.

05
Under consideration

Consumer-network reachability

Rust libp2p is a candidate for relay-assisted connectivity, NAT detection and hole punching across home and mobile networks. It is not yet integrated. A2A would remain the message interface, with access controlled by each receiving node.

06
Research

Delegated actions

A future node could request an action from another device, with the receiving owner choosing what to allow. Remote actions are not available in the current demo.

TRY THE PRE-ALPHA

Explore an exchange between two nodes.

Run the local A2A demo to see a public answer returned and a restricted request refused. It uses synthetic data and a local demo token. Production device pairing and remote actions are not yet available.