Your AI assistant does the thinking. The robot does the walking, looking, listening and talking. A small bridge program on the robot joins the two together, and our one-prompt setup helps you build it.
Pick one of our four bots. The kits take an afternoon or two to build; the pre-built Rider-Pi comes ready.
Pop it on your home Wi-Fi, then link it to your AI assistant with a small bridge program (our setup prompt walks you through building it).
Say hello. It hears you, thinks it over, moves and replies in the voice you've picked.
Copy this into your AI assistant, swap in your robot's name, and it'll walk you through setup one step at a time, safety limits included.
Hi! I've just bought a home robot and I'd like your help setting it up so I can talk to you through it. My robot: [ROBOT MODEL] (Freenove Robot Dog Kit FNK0050 / SunFounder PiDog / Yahboom Rider-Pi CM4 / Yahboom Rider-Pi CM5) My computer: [Windows / Mac / Linux] My experience: [total beginner / done a bit of coding] Please guide me step by step. Give me ONE step at a time, tell me exactly what to type or click, and wait for me to say "done" (or paste any error) before moving on. Part 1: Get the robot running 1. Flash Raspberry Pi OS onto the microSD card using Raspberry Pi Imager. Set the hostname, my Wi-Fi, a username and a strong password, and enable SSH in the Imager settings. 2. Boot the robot, find it on my network and connect over SSH. 3. Update the system and install the maker's official Python library and examples for my exact robot model. Use the maker's own documentation; if you're unsure of a command, tell me to check their docs rather than guessing. 4. Run calibration if my robot needs it. 5. Test each part separately, one at a time: movement (slowly, on the floor, away from stairs and edges), camera (take one test photo), microphone (record 3 seconds) and speaker (play a test sound). Part 2: Build a small, secure bridge on the Pi Help me write a small Python program on the Pi that lets me talk to you through the robot: - Security first: no open ports on my home router and no port forwarding. The Pi should only make OUTBOUND connections, for example an outbound websocket/HTTPS connection or a private network such as Tailscale. Keep keys in a separate config file that never gets shared or uploaded, and explain each choice in plain English. - Voice in: wake word or push-to-talk, then speech-to-text. - Voice out: text-to-speech through the robot's speaker, with a voice I can choose. - A short, fixed list of commands the robot will accept: move forward/back, turn left/right, look around, take a photo, speak, and a simple patrol of the room it's in. Anything not on the list gets ignored. Safety limits (please build these in from the start) - Low speed caps and short move durations by default. - Saying "stop" (or pressing a button) halts all movement immediately, every time. - No stairs, edges or tables. Stop if a sensor sees an obstacle or a drop. - The camera and mic are only used when I ask, never recording in the background. - A privacy indicator (an LED, the screen or a sound) whenever the camera or mic is on. - A battery-low warning and a safe stop. How I'd like you to work - Test one small piece at a time and confirm it works before adding the next. - Ask me before anything risky or hard to undo (deleting files, changing network or router settings, running things as root, or anything that costs money). - Be honest about what my robot can't do and about any lag. - If something's beyond my robot's hardware, say so and suggest a simpler option. Let's start with Part 1, step 1.
Three parts work together. None of it is magic, and you stay in charge of every bit.
It understands what you say, decides what to do and talks back. It's the same assistant you already chat to on your phone or computer.
A small program on the robot's Raspberry Pi. It passes your assistant's instructions to the motors, camera, mic and speaker, and sends back what the robot sees and hears.
Legs or wheels to move, a camera to look, and (on most bots) a mic and speaker to chat. It only does what the bridge tells it to.
The thinking happens online, so each request takes a trip from the robot to your AI assistant and back. Expect a second or two between speaking and the robot replying or moving. That's normal, and it's why our setup keeps moves short and slow.
Photos and audio go from the robot to your AI assistant when you ask for them, and are covered by that assistant's own privacy settings. Our setup prompt asks for the camera and mic to be used only when you ask. More on that on our peace of mind page.
Check the Wi-Fi name and password (they're case sensitive). Many small boards only like 2.4 GHz networks, so make sure that band is switched on, and move the robot closer to your router for the first setup.
Test the camera in the maker's own app or example first. If that works, ask your AI assistant to check the bridge step that handles photos; paste in any error messages and it'll help you fix them.
Check the bridge program is running and the robot is online. Try a simple command such as "stand up" or "say hello" before anything fancy.
A second or two is normal. Much longer usually means weak Wi-Fi or a busy connection, so move the robot or your router a bit closer together.
Usually it's the battery. Charge it fully and try again. If it keeps happening, check the maker's guide for calibration or servo settings.
Still stuck? Paste the error into your AI assistant along with our setup prompt, or read the FAQ.
This is a general-purpose prompt, not an official integration with any AI assistant or robot maker. Always follow the maker's own safety instructions.
