Managing Your Agent Squad From Your Phone

You are not always at your desk. Your agents are always running.

This is the fundamental tension of operating AI agents as a solo builder. The agents do not stop when you close your laptop. They keep running, keep processing, keep hitting API endpoints and consuming resources. And when something goes wrong -- an agent crashes, a key expires, a VPS maxes out its CPU -- you need to know about it whether you are at your desk or on a bus.

Right now, the only way to know something is wrong is to check. Open a terminal. SSH into a server. Look at a dashboard on a desktop browser. If you are away from your computer, you are flying blind.

We are fixing that.

The problem with desktop-only management

We wrote about this in The Three Types of OpenClaw Users. The developer who builds in an IDE but needs to manage from anywhere is stuck with tools that assume a desktop:

• SSH from a phone is technically possible and practically miserable. Typing commands on a mobile keyboard while trying to diagnose a container issue is not a workflow anyone would choose.
• Provider dashboards on mobile are an afterthought. Hetzner, DigitalOcean, AWS -- their mobile experiences are functional but not designed for quick operational tasks. Restarting a server is a multi-step process on a small screen.
• No unified view means that checking on agents across multiple providers requires logging into multiple dashboards from a phone. Each one has its own auth flow and navigation. It is death by a thousand tabs.
• No proactive alerts means you only discover problems when you look for them. Nobody is pinging your phone when an agent goes offline at 2am.

The result is that most operators check on their agents less often than they should, because checking is inconvenient. Problems accumulate silently until they become emergencies.

What we are building: a PWA with push notifications

The LaunchThatBot dashboard is becoming a Progressive Web App. That means you can install it on your phone's home screen and use it like a native app -- with one critical addition: push notifications.

The dashboard you already know, optimized for mobile

This is not a separate mobile app with a subset of features. It is the same LaunchThatBot dashboard, responsive and optimized for small screens. Everything you can do on desktop, you can do on your phone:

• View all your deployments and their current status
• Check agent health and activity
• View structured event logs
• Manage configurations
• Restart deployments
• Monitor resource usage

The difference is that the layouts, navigation, and interaction patterns are designed for touch and small screens. Not a desktop UI crammed into a mobile viewport. A real mobile experience.

Push notifications that tell you what matters

The real shift is proactive alerts. Instead of checking in on your agents, your agents check in with you.

When you install the PWA, you configure which alerts you want to receive. We are building support for:

Agent health alerts

• Agent goes offline or becomes unreachable
• Health check fails after a configurable number of retries
• Agent restarts unexpectedly

Resource alerts

• CPU usage exceeds your defined threshold
• Memory usage exceeds your defined threshold
• Disk space running low on the deployment host

Security alerts

• API key approaching its expiration date
• Failed authentication attempts on the management surface
• Certificate renewal issues

Performance alerts

• Agent error rate spikes above normal baseline
• Response latency exceeds your defined threshold
• Queue depth grows beyond expected bounds

Each alert type is independently configurable. You choose what matters to you, set your own thresholds, and only get notified about the things you care about. No alert fatigue from notifications you did not ask for.

Customizable per agent and per squad

Not every agent needs the same alert profile. A production agent serving real users should wake you up at 2am if it goes down. A development agent running experiments can wait until morning.

Alert configurations are per-agent and per-squad (group of agents). You can set aggressive thresholds for your critical agents and relaxed thresholds for your experimental ones. The notifications respect your context.

What this changes for each user type

For the mobile-first builder

You are already managing agents from your phone. The PWA gives you a purpose-built interface instead of a patchwork of chat apps and web UIs. You get real observability without SSH, and push alerts mean you do not have to keep checking manually.

For the desktop power user

You manage from your desk during the day and want peace of mind when you step away. Push notifications give you that. If something needs attention, your phone tells you. If everything is fine, silence. No need to "just check real quick" before bed.

For the developer who builds at the desk and manages on the go

This is the use case that drove us to build the PWA in the first place. You want deep development tools at your desk and lightweight operational tools everywhere else. The dashboard is the deep tool. The PWA is the lightweight one. Push notifications are the bridge that connects them -- you will know when something needs your attention regardless of where you are.

The experience we are targeting

Here is the day we are building toward:

You deploy three agents on LaunchThatBot from your desktop. You configure alert thresholds: wake me up if any agent goes offline, notify me if CPU exceeds 80%, and warn me if an API key is expiring within 7 days.

You close your laptop and go about your day.

At 3pm, your phone buzzes. One of your agents hit a rate limit on an external API and its error rate spiked. You open the PWA, see the structured error log, and realize the API provider changed their rate limits. You update the agent's configuration to add backoff logic -- from your phone, in two minutes, without opening a terminal.

That is the difference between managing agents reactively (SSH in when you remember to check) and proactively (your agents tell you when they need you). The PWA makes the second one real.

If you are already on LaunchThatBot, the PWA will be an upgrade to the dashboard you are already using. If you are not on LaunchThatBot yet, here is how to get started -- and the mobile experience will be waiting for you when it ships.