In short, Device Studio is the part of gethome studio, the Mac app, that builds your own devices from a description. Plug an ESP32 board into your Mac and say what it should do: an agent plans the device with you, lists the parts and the wiring, writes and builds the firmware, and — when you press Flash — puts it on the board and into your gethome home, then writes the automations it needs, each added only when you press Add. It is in early access by waitlist: a free trial period first, then a subscription.
Early access · join the waitlist. Coming to gethome studio for Mac. Plug in a board and say what it should do: an agent plans it with you, then writes and builds the firmware. Press Flash, and it joins your home.
Filmed in one take on 20 October 2026 — 3 min 34 s from plugging the board in to both rules on. Download the film (MP4, 5 MB)
A real run, replayed. The agent plans, writes and builds; you accept the plan, then press Flash and Add — try them here, as the person did.
Board: Waveshare ESP32-S3-Zero · ESP32-S3 · 4 MB flash · 2 MB PSRAM. Home: My Home.
The person: “Let’s make the LED on the board light up when motion is detected by the motion sensor. There is only one sensor in the house right now.”
✓ Looked at the home, looked up the board
Plan: The board’s LED lights up when the motion sensor sees someone. The ESP32-S3-Zero joins My Home as a light called “Motion LED”. The hub turns it on when Motion sensor T1 87BC sees motion, and off when the sensor reports the room is clear. You can also switch it from the gethome app.
The person pressed Write the firmware.
What you need: USB-C data cable (To flash the board, and to power it); USB phone charger (5 V) (To power the board once it’s flashed).
How to connect it: USB-C cable → Board USB-C port — That’s all. The LED is already on the board (GPIO 21), and the motion sensor is your existing one in My Home..
✓ Built motion-led
✓ Built motion-led — 1.1 MB of 1.3 MB
✓ Checked which boards are plugged in, wrote a file, updated the project
The agent asked: The plugged-in board is your “LED test” board. Should I flash Motion LED onto it and replace LED test? The person answered: Yes, replace LED test.
Studio asked: Flash Motion LED onto the ESP32-S3? This board runs LED test in LED test — flashing replaces it. It takes under a minute. The person pressed Flash.
Motion LED is in “My Home” — Done in 40 seconds. (Check the board, Fetch the build, Write to the board, Listen to it start, Join the home)
✓ Flashed motion-led, looked for motion-led in the home, read how the home writes automations
The agent: Motion LED is in My Home and online. Now I’ll check the two rules with the hub.
✓ Checked “Motion LED off when clear” with the home twice
The agent: The hub accepts both rules. Here’s the first one:
Add “Motion LED on when motion” to “My Home”? When: Motion detected · Motion sensor T1 87BC. Then: Switch on · Motion LED. The person pressed Add: “Motion LED on when motion” is on in “My Home”.
Add “Motion LED off when clear” to “My Home”? When: Motion stops · Motion sensor T1 87BC. Then: Switch off · Motion LED. The person pressed Add: “Motion LED off when clear” is on in “My Home”.
Sped up. Left out: the step where the Wi-Fi password was typed.
Board: AI-Thinker ESP32-CAM, on its ESP32-CAM-MB USB board. Home: none.
The person: “A camera on my Wi-Fi, without a home: the AI-Thinker ESP32-CAM on its MB board. Use the gethome library’s camera so I can open the still and the live stream in a browser on my Mac. No flash LED, nothing else.”
✓ Looked up the board 3 times, looked through the project
Plan: A Wi-Fi camera you open in a browser on your Mac. One ESP32-CAM that joins your Wi-Fi on its own (no gethome home) and serves a still photo and a live video stream that you open by its address in Safari or Chrome. The flash LED stays off.
The person pressed Write the firmware.
What you need: Micro-USB data cable, short (Must carry data, not only charge; short and thick avoids restarts); 5 V USB power supply, 1 A or more (For running it away from the Mac; the camera and Wi-Fi together need at least 500 mA).
How to connect it: ESP32-CAM (all pins) → ESP32-CAM-MB sockets — Push the camera board straight into the MB board, antenna end away from the USB socket, so the pin labels match; OV2640 ribbon cable → Camera connector on the ESP32-CAM — Already fitted on most boards — check the little latch is closed. Nothing else to wire. Don’t connect anything to IO0 or IO16 — the camera and its memory use them. If the log says “Brownout detector was triggered”, the power is too weak: use a shorter cable or a stronger charger.
✓ Looked through the project, built wifi-camera
✓ Built wifi-camera — 1.2 MB of 2 MB
The agent: The build is clean: it uses 62% of the board’s space. I’ll update the project memory, then we can flash.
✓ Wrote a file, updated the project, checked which boards are plugged in
The agent: Your ESP32-CAM is plugged in through its MB board (CH340, 4 MB flash). Asking Studio to flash it now. After flashing, Studio will ask you for your Wi-Fi name and password.
Studio asked: Flash Wi-Fi camera onto the ESP32-D0WD-V3? Studio writes the firmware over USB. It takes under a minute. The person pressed Flash.
Flashing Wi-Fi camera (Check the board, Fetch the build, Write to the board, Listen to it start, Connect to Wi-Fi)
✓ Reading wifi-camera’s log
Sped up. Left out: the Wi-Fi name and password, and the board’s address.
Board: Waveshare ESP32-S3-Zero · ESP32-S3 · 4 MB flash · 2 MB PSRAM. Home: none.
The person: “Test device: the built-in RGB LED changes color once per second—red, green, blue—and logs the step number and color every second.”
✓ Looked up the board
✓ Updated the project
Plan: The built-in LED cycles red, green, blue — one step per second. A simple test to prove the board, the build and the flashing all work. No wiring at all: the colour LED is already on the board. Every second the LED moves to the next colour and the board prints a line like “Step 4: green” to its log.
The person pressed Write the firmware.
✓ Wrote devices/rgb-test/rgb-test.ino
✓ Built rgb-test
✓ Built rgb-test — 300 KB of 1.3 MB
✓ Wrote CLAUDE.md
✓ Checked which boards are plugged in
Studio asked: Flash RGB LED test onto the ESP32-S3? The person pressed Flash.
Flashing RGB LED test
✓ Flashed rgb-test
✓ Read rgb-test’s log
Sped up. The agent’s report after reading the log isn’t whole in the recording, so it is left out.
The motion sensor tells the hub, the hub runs the rule the agent wrote, and the board it flashed lights up — in the room, and in the app.
A hand passes the sensor, the hub runs the rule, and the board lights the shelf. Paused to explain — for real, it takes under a second.
In the app, like any other light. Motion LED on the Devices pane, and its rule’s recent runs — in the App Store’s gethome for iPhone.
What Device Studio does today, before anyone outside has used it.
Invitations will go out in waves, to the people on the waitlist.
Device Studio starts with a board and a sentence. These are next:
Then projects of many devices that work as one — the agent planning a whole space, not one gadget.
In short, Device Studio is the part of gethome studio, the Mac app, that builds your own devices from a description. Plug an ESP32 board into your Mac and say what it should do: an agent plans the device with you, lists the parts and the wiring, writes and builds the firmware, and — when you press Flash — puts it on the board and into your gethome home, then writes the automations it needs, each added only when you press Add. It is in early access by waitlist: a free trial period first, then a subscription.
Not yet. Device Studio is built and has run on real boards — the film is one take of it — but it isn’t in the gethome studio you can download today. Early access will open in waves to the people on the waitlist, with an invitation by email, and start with a free trial period.
Device Studio’s early access will start with a free trial period, with nothing to pay. After it, Device Studio will work by subscription, sold on the web and never inside the iPhone app. There is no price yet.
Boards of the ESP32 family — about 400 that its toolchain builds for, eleven of them checked pin by pin — and a Raspberry Pi, in Python. Studio reads which chip is plugged in and checks it against the plan before it flashes. Arduino and Raspberry Pi Pico boards are next.
Only for a device that joins your home, and for the automations Device Studio writes, which run on the hub. A device can also talk to your own system over Wi-Fi, or run on its own — the Wi-Fi camera opens in a browser with no hub at all.
What you write, the photos you add and the project’s files — and, when you give a project a home, that home’s device names, rooms, readings and rules. In early access these will go to our server, and from it to Anthropic, whose model the agent runs on. Your Wi-Fi password and a board’s settings go from your Mac to the board over USB, and nowhere else.
Yes. A project exports as a folder that builds with plain arduino-cli, the device libraries are MIT-licensed, and the way a device talks to the hub is documented.
No. You press Flash before anything is written to a board, and Add before a rule reaches your home — and the agent asks before it replaces a board’s program. Every change it makes to a project is kept, with the way back to it.
Join the waitlist for early access. It will start with a free trial period, and we’ll write when your invitation is ready.
Your address is used only to invite you to early access, and deleted when you ask. Privacy Policy