Project
Roadmap
Planned items show direction, not shipped capability. The rest of the docs describe only what works today.
- macOS and Linux connectors; Windows Node and Android Node in testing
- Agent access, approvals, Activity and durable receipts
- Plugins, Skill, MCP OAuth, CLI and SDK
- Teams, member policies and named device sharing
- Official hosted service and the same app for self-hosting
- Validate Windows and Android compatibility and runtime reliability
- Direct device-to-device transfer with a rate-limited relay
- Signed releases and unattended updates
- Keychain and keyring storage for device keys
- Quotas, retention and external artifact storage
- Enterprise SSO, SCIM and SIEM export
- More local executors and device integrations
- Community tool plugins and Skills
The opportunity beyond one computer
Different Nodes can contribute different environments to the same agent: code on a Mac, builds and GPU programs on Linux, local Windows tools and Android app actions. This enables device-spanning workflows when the relevant tools, permissions and dependencies exist.
Directions include shared lab machines, household devices and locally connected instruments. Television, watch, printer or other hardware support needs a concrete connector or local tool integration; these are future possibilities, not current support.
What will not change
- The device keeps the final say over what runs on it.
- Hosted and self-hosted run the same product.
- Permissions and receipts stay independent of any single agent vendor.