“Find my Pi’s specs, then open YouTube on its desktop.”
System information, browser launch, and a screenshot to see the result.
See Linux functionsYour agents. Your devices.
Hardware, Linux computers, and your Home Assistant home.
Connected to the agents you already use.
Keep it on your own machine? CLI, SDK, or self-hosted
Copy this prompt: Read https://www.openlaunch.dev/docs/sdk.md and https://www.openlaunch.dev/docs/functions.md. Help me build an openlaunch adapter for my device, publish its actual functions, and test an action end to end. Use the live API schemas. Keep device setup credentials, device credentials and agent credentials separate. Have me enter credentials privately in my terminal, never in chat.
Start with something useful.
Connect a computer, bring your home into the loop, or add a device of your own.
A Linux computer
Inspect your Pi, open a browser, and control its desktop with the access you enable.
Set up LinuxYour Home Assistant home
Discover entities, run scenes and scripts, and call your connected devices’ functions.
Connect Home AssistantA device you build
Start with an Uno or ESP32, or write an adapter for the hardware you have.
Explore the SDKAsk for what you actually need.
Your agent reads the device’s functions, requests an action, and follows its receipt.
“Turn on the test toggle, read its state, then turn it off.”
A real service call and state read. Start with a helper; no hardware needed.
Try the test helper“Show ‘hello’ on my Uno, then check its health.”
Built-in functions today. Add your own handlers as your project grows.
Connect an UnoExample requests. Available functions depend on your adapter and saved grants. See what’s been verified →
Put your devices in the flow.
One device or a whole Home Assistant installation. Your agent uses the same connection.
Your agentChatGPT · Codex · Any MCP client→openlaunchFunctions · Access · Receipts→Adapter or gatewayLinux · Home Assistant · SDK→Your devicesComputers · Homes · Hardware
Choose the access. Grant individual functions, choose an expiry, and revoke access from your console.
Follow the result. See what was queued, delivered and reported. Device state and physical verification stay distinct.
Use the interface that fits.
Your hardware.
Your functions.
Describe the inputs. Write the handler. Connect your agent.
Adapters publish the functions they actually implement. Your agent discovers the current schema through MCP, API or CLI, with the same permission checks across all three.
Start with one device.
Free hosted access. MIT licensed. Self-host it when you want.
Open your console See pricing →Latest updates →