TL;DR: Ground Control Chat shows every Claude Code session running on your Mac as a little pixel pilot marching down a neon city street on your phone. Cyan means working. Lavender means idle. Pink means one of them needs you. Tap a pilot to read the conversation and send new orders from anywhere. I designed and built it solo, and it is free on the App Store.

What is Ground Control Chat?

It is a phone app for people who run AI coding agents on their Mac. You run one command on the Mac, scan a QR code, and every Claude Code session you have open shows up on your phone as a creature with its own face and its own walk. You can read every reply as it streams in, and you can type a new instruction that lands in your actual terminal at home.

No account. No signup. One command and a QR code.

Why would an AI coding agent need a phone app?

Here is the thing nobody tells you about agentic coding. The model is not the bottleneck anymore. Waiting is.

You give an agent a real task and it works for eight minutes. Sometimes twenty. During that time you are supposed to sit and watch a terminal, because at some unpredictable moment it will stop and ask you one question. Miss the question and the twenty minutes were nothing.

So you end up chained to a desk by a tool that was supposed to free you. I ran three or four sessions at once for months and the real cost was not tokens, it was attention. I could not leave the room.

Ground Control started as a selfish fix. I wanted to know, from the train, whether anyone needed me.

Why little creatures instead of a list?

My first version was a list. Session name, status badge, timestamp. It was correct and it was useless.

A list makes you read. When you glance at your phone between two stops you do not want to read, you want to know. So I threw it out and made the status physical. Each session becomes a pilot that walks. Working pilots march. Idle pilots stand around. A pilot that needs you turns pink and stops.

Now the answer to "is everything fine" is a half second glance at a street, not a scan of six rows of text. That is the whole product in one decision.

The creatures are generated from the session identity, so a session always hatches the same face. That sounds like a toy detail. It is not. Recognition is what lets you skip reading. After two days you stop parsing names and start recognizing who is who, the same way you recognize a friend from across a street.

What was the hardest part to design?

Trust in the pink state. If the app ever tells you nothing is wrong while an agent sits waiting for input, the product is dead. Nobody gives a monitoring tool a second chance after it lies once.

So the entire design bends toward one rule. Never miss a pink. Everything else, the animation, the street, the palette, was allowed to be playful precisely because that one thing is treated as sacred.

That is a lesson that transfers to every product I work on. Pick the one promise you cannot break, defend it absolutely, and then let yourself have fun everywhere else.

How does the privacy side work?

Your pairing key is generated on your Mac and only ever travels through the QR code you scan with your own phone. Traffic is end to end encrypted. The relay routes sealed bytes it cannot read, and nothing is stored.

This was not a feature decision, it was a permission decision. I am asking people to pipe their source code and their private repositories through a phone app. That only works if the honest answer to "what can you see" is "nothing".

What did building it teach me?

• Ambient beats accurate. A glanceable signal you actually check wins against a detailed dashboard you open twice a week.
• Personality is a memory aid. The creatures are not decoration, they are how you tell six sessions apart without reading.
• Setup friction kills developer tools. One command and a QR code was the target from day one. Every account screen I did not build is a user I did not lose.
• Build for your own pain. I shipped this fast because I did not have to research the problem. I was the problem.

How does this connect to my design work?

Ground Control is my third app on the App Store, after Glimpse Vision AI and AnimaEcho. All three were designed and engineered by one person, which is only possible because of how much the tools changed. I wrote about that shift in how I use Claude Code as a designer.

Shipping my own products is also how I stay useful to clients. It is very hard to advise a founder on AI product decisions if you have never had to answer for one yourself.

FAQ

What is Ground Control Chat?

An iPhone app that lets you monitor and control the Claude Code sessions running on your Mac. Each session appears as a pixel pilot whose color tells you if it is working, idle, or waiting on you.

What do I need to use it?

A Mac running Claude Code, plus the Ground Control daemon, which you start with a single command. Then scan the QR code with the app.

Is it private?

Yes. The pairing key never leaves your devices except through the QR code you scan, traffic is end to end encrypted, and the relay stores nothing and cannot read what passes through it.

Who made Ground Control Chat?

Carlos Lastres, an Apple Design Award winning product designer and software engineer based in Tokyo, designed and built it solo.

Where can I download it?

Free on the App Store.

Carlos Lastres is an Apple Design Award winning product designer and software engineer based in Tokyo, a 3x TEDx speaker and a United Nations speaker. He designs products that turn attention into revenue, and ships his own apps end to end.