Seven features.
105 capabilities.
Xross is one daemon and a small set of typed services on top of it. Here is every one of them, what it does, and — row by row — whether it runs today. 60 of the 105 do.
CrossFlow
One keyboard, one cursor, every screen you own.
One keyboard and mouse drive several computers as if their screens were one continuous desktop — and a phone stands in as a trackpad and keyboard when there is no mouse to hand. Arrange your displays once; after that the cursor simply crosses the edge and typing follows it. The machine being controlled, never the sender, decides who holds input.
- 2Working today
- 6Being built
- 7Planned
Remote Files
Your own devices, browsable and playable, without a server.
Walk another machine's folders, download a file, or scrub a 44 GB film — with no port opened anywhere. A device exports named folders, an authorized peer lists and range-reads inside them, and Copy Link produces a short-lived URL that VLC, IINA or Infuse can open and seek. The machine holding the file never runs a web server; the HTTP gateway runs on your own loopback.
- 9Working today
- 1Being built
- 5Planned
Terminal & Access
Reach any machine you own, without opening a port.
Three separate, individually authorized ways into a device you own: a first-party terminal where the receiving machine creates the PTY and picks the shell; an exact-target TCP forward for a database or a service; and a SOCKS5 or HTTP CONNECT exit that routes your traffic out through a device you trust. Every one of them is a request the far machine can refuse — it re-reads its own policy file before a PTY is spawned or a socket dialled.
- 12Working today
- 1Being built
- 3Planned
Clipboard & Transfer
Copy here, paste there — and send the file too.
One clipboard across the machines you own, and files that move between them over an authenticated fabric or a plain LAN. A transfer is offered before it lands: the receiver sees name, size and digest, consents, and only then do bytes stage, get verified, and publish with a single rename. It also speaks stock LocalSend, so a device you can reach without an account is still a device you can send to.
- 11Working today
- 1Being built
- 2Planned
Vault & Trust
Your secrets, encrypted on your devices, provable without us.
Credentials and secrets stay as ciphertext that only your enrolled, vault-admitted devices can open. Every device gets its own sealed envelope, so removing a laptop actually removes it — the vault key rotates rather than a server merely declining to serve. The design is deliberately checkable rather than promised: your client enumerates the recipient set and the certificate chain locally.
- 4Working today
- 4Being built
- 10Planned
The Fabric
Your own devices, one private network, no account required.
A small always-on daemon binds one endpoint per profile and gives all your machines a single cryptographic identity. Devices find each other over mDNS on a LAN, dial each other directly across the internet, and fall back to a relay you host yourself when direct is impossible. Every session reports which path is carrying its bytes.
- 10Working today
- 1Being built
- 2Planned
AI & Automation
Give an AI tool your devices, one capability at a time.
The daemon can open a single HTTP listener on loopback and speak MCP on it. Claude Code, or any host that can send a bearer token, connects with a key you minted and can then list your devices, read one machine's live state, and run a named program on another. The same daemon is driven by the CLI and by a typed client SDK — all three through one deny-by-default capability model.
- 12Working today
- 2Planned