Discover
Know what a connected device can sense and do.
Your agentReason & decide
gadgets.botHardware SDKThe camera sends an observation to your agent through the SDK.
First up: gadgets.bot — agent-to-hardware SDK. In development.
Your agent.
Connected to hardware.
Our first focus is the tooling between an agent and a physical device. A common way to discover capabilities, connect, and interact—without designing around a single agent vendor.
Connect
Give your existing agent a path to that hardware.
Interact
Turn inputs and agent decisions into physical behavior.
TWO DIFFERENT DEPLOYMENT MODELS
Agent harness→MCP surface→Local bridge→Device
Your agent can run elsewhere. A local bridge connects its tools to device capabilities and returns observations.
INITIAL SDK DIRECTIONInputs→On-device model + runtime→Outputs
The model runs on the hardware itself. Memory, compute, power and the model determine what is possible; this is a separate runtime problem.
LONGER-TERM DIRECTIONProposed architecture. SDK implementation has not started; initial board and harness support is being defined.
Explore the SDK planSmall devices.
Bigger possibilities.
Start with a behavior you want to exist in the world.
A desk voice companion
A physical way to speak to an agent and hear a response.
A sensor-aware assistant
Give an agent context from the room around you.
An agent-controlled display
Bring useful information off the chat window and onto your desk.
Build, learn and evolve.
Across the device lifecycle.
Our vision brings people and agents together across the device lifecycle—from composing and verifying a build to observing its behavior and improving it over time.
The SDK is our starting point. Over time, shared projects and evidence from real builds can help the community develop more capable, reliable devices.
COMPOSEVERIFYRUNLEARNEVOLVE
Good questions.
Can I use my existing agent?
That is the SDK’s goal: let you bring an existing agent harness or a custom agent instead of adopting one prescribed assistant. Initial adapters and supported interfaces are still being selected and tested.
Does the model run on the device?
Not necessarily. An agent running on your computer, server or cloud can interact with a connected device through a bridge. Running a model on the device itself is a different setup and part of the wider direction.
Can I try the SDK today?
Not yet. The repository currently contains research and the proposed design; SDK implementation has not started. There is no SDK installer or public release yet.
Which boards and agent frameworks will work?
ESP32-family boards and Raspberry Pi are part of the research, alongside MCP-facing integrations. They are candidates, not a published compatibility guarantee. A tested support matrix will accompany implementation.
Is this just an SDK?
The SDK is the first focus. The wider electrondreams vision includes composing devices from verified parts, remixing projects and working with agents across a device’s lifecycle.