lampOS让AI代理控制机器人硬件

The open-source operating system for physical AI.

Physical AI Operating System We're building the "Android" for physical AI agents. Give Hermes, Claude Code, Codex, and other AI agents eyes, ears, a voice, and a body they can control. Bring your AI agents into the physical world. Start with Lamp · Bring your own robot · Build a physical skill Autonomous.Lamp.mp4 Choose your agent Run Hermes, Claude Code, Codex, OpenClaw, OpenCode, or PicoClaw. Choose a compatible model and configure its voice, personality, and tools. The OS runs on the robot and coordinates hardware and agent tasks. Model inference may use remote services, depending on your configuration. Give it a body Start with Lamp, Intern, or Reachy Mini—or add support for your own robot. Physical AI Operating System connects the agent to the hardware that body provides: cameras, microphones, speakers, motors, lights, and sensors. Physical skills Give your agent new ways to sense and interact with its surroundings. Follow an object with its camera and movement. Respond to touch with a gesture. Turn a sensor reading into light, movement, or speech. Start with an existing physical skill, change its instructions, or connect your own tools. Use the skill creator to write a new skill, and see the contribution guide to share it. Try saying On a configured Lamp, try these in normal voice mode or text-only Web/MQTT chat. These are supported intent examples; selection depends on confidence and available device capabilities. Uncertain requests go to the main agent. Say or type Expected behavior “Turn off the lights.” Turn off Lamp's light through a local command. “This lamp is too bright.” Reduce the current light brightness by half. “You're speaking too loudly.” Reduce the current speaker volume by half. “Make this lamp violet.” Set a solid purple light. “I need light to read a book.” Activate the reading lighting scene. Context matters too: while working on an image or render, “Make it brighter” goes to the main agent to interpret the task context. It does not automatically brighten the Lamp. Explicit hardware requests such as “Turn off the lights” remain eligible for intent handling while a Harness task is pending. Intent configuration and limits · Harness context routing Work across your robot and computer Delegate to Harness agents. harness-use sends coding and research tasks to agents already running in Harness on your paired computer. Ask a named agent to work, answer its follow-up questions, and receive its result through voice or chat. Pair from OS Monitor and Harness Desktop on the same LAN. Harness-only voice sends manual tap-to-record turns to the agent focused in Harness. Get Harness · Integration and setup. Use Mac apps through Buddy. computer-use lets the device agent inspect an app, click or type, and verify the resulting UI through a paired Autonomous Buddy. Buddy bundles Cua Driver for Accessibility observations and actions, with screenshot support for visual tasks. The device agent owns the task; Buddy executes on the Mac. Harness and Buddy have separate connections and pairing. Computer-use guide. Route requests with Jev. For normal voice requests received by os-server and text-only Web/MQTT chat, local rules run first, then the Jev intent fallback (enabled by default). The OS validates the selected command, parameters, confidence, and device capabilities before execution; uncertain requests continue to the main agent. Context-dependent follow-ups bypass intent handling when they need the main agent. Attachments and Harness-only voice retain their separate routes. Separate skill-preloading integrations prepare instructions before the main model call through runtime hooks or managed bridges, with native discovery as fallback. New integrations outside Hermes are disabled by default pending native validation, controlled by a Go build switch in each runtime. Jev also supports experimental Buddy UI-action suggestions. Quick start The simplest way in is a robot we have already tested it on. What each of them can do: robot comparison. Autonomous Lamp Lamp is the robot that shows the whole OS — it sees, hears, speaks, moves, and ships with Physical AI Operating System on it. Add it. In the Autonomous app (iOS | Android), tap Add robot → Lamp. Set up Wi-Fi. Pick your network in the app; it joins the robot's hotspot and hands over the keys and pairing. Interact with Lamp. Say something, it turns to look at you, the ring lights up, and it answers. Install a skill from the Skill Store — one tap, live on the next conversation. Build your own skill. Type what you want it to do in the app and it writes the skill. Give it a character. Edit SOUL.md and it is someone else on the next turn. Reachy Mini Reachy Mini is Hugging Face's desk robot, running our OS beside its own stack. Reach.Mini.and.Autonomous.Lamp.mp4 SSH in — ssh [email protected]. Run one command. Nothing is flashed; the Reachy daemon keeps the motors. curl -fsSL https://raw.githubusercontent.com/autonomous-ai/Physical-AI-Operating-System/main/robots/reachy-mini/install.sh | sudo bash Add it. In the app, tap Add robot → Reachy Mini and give it reachy-mini.local. Interact with it. Say something — the head tilts, the antennas lift, and it answers. Install a skill from the Skill Store, or type what you want it to do and it writes one. Give it a character. Edit /opt/devices/reachy-mini/SOUL.md. Everything else, including how to undo the install: devices/reachy-mini/README.md. Put it next to a Lamp. Each one hears the other's answer as its next input, so the two of them will hold a conversation until you stop them. Autonomous Intern Intern is the always-on desk agent: mic, speaker, LED ring. Add it. In the app, tap Add robot → Intern. Set up Wi-Fi. Same flow as Lamp: pick your network and it handles the keys and pairing. Interact with it. Say something and it answers; the ring shows what it is doing. Install a skill from the Skill Store. Build your own skill. Type what you want in the app; it is live on the next conversatio