Device Kit (8DK), Preview
8DK, the Device Kit
Give an 8gent vessel any device, consent first.
Not usable with a running vessel yet
8DK v1 is a library in 8gent-code (#3362), merged to main on 2 October 2026 by #3364. It is not yet in a release and not on npm. No running vessel can pair a device until slice 2 (#3363) ships the /device route. See Status and roadmap.
A vessel is a running copy of the 8gent daemon, the always-on 8gent process that apps connect to. Once slice 2 (#3363) ships, paired devices will connect to it too.
A device says what it can read and what it can do. A person pairs it and picks what to allow. Each allowed capability becomes a tool the agent can call, and every call passes the same permission checks as the rest of 8gent.
In three steps
- Declare. The device describes itself in a manifest: an id, a name, and a list of capabilities. Each capability either reads the world (Can read, a sensor) or changes it (Can do, an actuator).
- Pair. The vessel shows a 6-digit code on the device and in a consent prompt. The person checks the codes match and ticks the capabilities to allow. Nothing is allowed by default.
- Use. Each allowed capability becomes an agent tool. Capabilities nobody allowed are invisible to the agent, and refused if it names them anyway. Revoke or unpair and the next call is refused.
What it is not
- Not firmware or a device runtime. 8DK is the vessel side, plus a small helper a device can use to answer calls.
- Not a remote shell. There is no generic "run a command" capability. Each capability is named, typed and allowed separately.
- Not a cloud service. A device pairs with your own vessel.