How Ponos Launch Works (And Why RocketBuddy Is Nothing Without It)

RocketBuddy is a rocket-shaped shell with an RGB light inside it. On its own, that gets you a nice desk lamp with a fun default takeoff sequence. What turns it into an actual AI companion is Ponos Launch — the free, open-source app that sits between RocketBuddy and the tools you already use, Cursor and Claude. Here's how it works, how we tested it, and why we're giving it away for free with every unit.

What Ponos Launch actually does

Ponos Launch is a small desktop app that talks to RocketBuddy over USB and to your AI tools over MCP (Model Context Protocol) — the same connection standard Cursor and Claude use to reach outside tools. Once it's running, RocketBuddy stops being a static light show and starts reflecting what your agent is actually doing: a long, smooth pulse when a task kicks off, a quick blink when it needs your attention, solid light when you want it just sitting there glowing. No cloud account, no subscription, no telemetry phoning home — it's a local app talking to a local light.

How it connects to your tools

Different AI tools connect differently, and Ponos Launch handles both cases without you thinking about it:

• Cursor and Claude Code — fully automatic. Turn it on once in the app, and Ponos Launch registers itself with both clients. Every time your agent finishes responding, RocketBuddy lights up on its own. Nothing to run, nothing to remember.
• Lovable, Replit, Bolt, and other remote-only tools — these platforms can only reach MCP servers over the internet, not on your own machine, so Ponos Launch can open a secure tunnel out and hand you a link to paste into that platform's settings. Same light, same app, just a different route in.

Unplug RocketBuddy mid-session, plug it back in later — Ponos Launch doesn't keep a connection open in the background, so there's nothing to reconnect or restart. It just finds the device again the next time it has something to show you.

The interface: your lights, your rules

We didn't want to ship a black box, so the app's interface is built to be opened, poked at, and changed. Everything RocketBuddy does on your desk is something you can see and set yourself:

• Light Patterns & MCP Mapping — every colour, every pulse, every blink timing is editable. Don't like the default takeoff glow? Change the colour, the speed, how many times it repeats — and decide which of RocketBuddy's behaviours (task starting, task needing you, just sitting there on) triggers which pattern.
• AI Clients — turn the Cursor and Claude Code connections on or off with a switch, no config files to hand-edit.
• Remote Access — pick a tunnel option, generate your link, and connect Lovable, Replit, or Bolt in under a minute, then shut the tunnel down again when you're not using it.
• Status — see at a glance whether RocketBuddy is connected and which pattern last fired, so you're never guessing why it did (or didn't) light up.

In short: the app controls the lights, and you control the app. Nothing about how RocketBuddy behaves is locked to what we decided looked good in our own testing.

How we tested it

Same approach as the hardware — repetitive, unglamorous, and aimed at making sure it works when you're not paying attention to it:

• Command-line tests — before there was a GUI at all, every light behaviour (on, off, blink, notify, the long takeoff pulse) was runnable and checkable from a terminal, so we could verify each pattern in isolation.
• Unplug-and-replug tests — because a desk companion that breaks every time you bump the cable isn't a companion, we deliberately disconnected RocketBuddy mid-task, over and over, to confirm the app just quietly finds it again instead of hanging or erroring out.
• Fail-silent tests — if RocketBuddy isn't plugged in at all, Ponos Launch should never interrupt or block your actual coding session. We tested that path specifically: no popups, no stalled agent, no error the AI has to deal with.
• Security tests — the remote tunnel only accepts requests with a valid access token, checked in a way that resists timing attacks, and it only ever exposes light controls — never file access or shell commands. We tested it with missing tokens, wrong tokens, and expired tunnels to make sure the door actually stays shut.
• Real-session integration tests — the same live-session testing described in our prototyping post: running Ponos Launch against real Cursor and Claude sessions to confirm the light matches what the agent is actually doing, not what we assumed it would do.

Why we're giving it away

RocketBuddy is the only product we sell. Ponos Launch is free and open-source because the value we're selling isn't the app — it's the moment RocketBuddy takes off when your agent starts working, and the peace of mind that it's not secretly reporting anything back to us. Anyone can read the code, see exactly what it does, and change it if they want something different. We'd rather you trust it than take our word for it.

RocketBuddy ships with the default takeoff sequence out of the box. Install Ponos Launch when you're ready to make it yours, and get in touch through our contact page if you want to be first in line when pre-orders open.