Let AI do more than write code — let it drive your board directly.
Describe a task; the Agent SSHes into your device, runs commands and streams logs back. Chat, terminal, files and flashing — all in one native window. No more tool-switching.
With Moss as the Agent runtime and RDK Studio as the developer surface, we close the loop “Sense → Reason → Decide → Act” end-to-end.
👨💻 Describe the task in natural language → Moss reasons → safety approval → on-device run → logs return → iterate
🔮 ROADMAP: MCP protocol · multi-device cluster orchestration · on-device fine-tuning · voice interaction · ROS topology viz · community skill marketplace · third-party hardware integrations
Take “get a single camera streaming” as an example, and look at the workflow side-by-side.
Every capability is deeply integrated with the Agent — it sees your terminal, understands your files, reads your board status, and steps in when you need it.
Mid-conversation, the AI quietly SSHes into your board and gets it running
Shared context with the chat — the AI can read the exact line that errored
Drag-and-drop transfer, path permissions auto-detected — no more scp
USB devices auto-detected — no separate flashing utility needed
Generic AI editors focus on “how to write good code.” Moss cares about “how to safely operate a physical device.” From driver crashes and dropped cameras to the last-step confirmation on a rm -rf — every detail is purpose-built for robotics engineering.
A dmesg error in the terminal? The AI hands you a diagnosis on the spot — no copy, no paste, no window switching.
Moss reasons in Studio dispatches commands to OpenClaw on the board logs return AI keeps analyzing. End-to-end loop.
Author a skill once and reuse it across boards. Once dispatched, the board executes on its own — field, weak network or no network, it still works.
Moss is the robotics-native Agent runtime built into RDK Studio. It plugs into mainstream LLMs upstream and bridges to the entire RDK lineup downstream via OpenClaw; on the memory side it integrates a 3-layer architecture in collaboration with the Hermes framework, paired with multi-channel orchestration to keep long sessions stable and on-device coordination tight.
On-device guardian and gateway
A local-first multi-channel AI gateway. Together with Moss it forms the cloud-edge dual-agent loop.
Hardware interception · edge compute adapter · long-log triage
Long-session memory engine · collaboration
Through our collaboration with the Hermes framework, Moss ships a 3-layer memory architecture (short-term / session / long-term) that survives across sessions and picks up long-running tasks where you left off.
For individual and community developers. Works with the entire RDK lineup — plug-and-play.