Agents At Work

Monitor and control AI agents from your phone

Android

Mac

Developer Tools

Development

Visit WebsiteSee on Product Hunt

Hey hunters! 👋 I'm Sergey, the maker of Agents At Work. The problem: I kick off Claude Code on long-running tasks, then walk away from my Mac. Every time, the same thing happened. I'd come back an hour later to find the agent stuck on a permission prompt it asked ten minutes in, just sitting there waiting for a yes/no I never saw. Or it had crashed silently. The "let it run autonomously" promise of these CLIs falls apart the moment you're not at the keyboard to babysit them. I actually started building this for myself before Claude shipped its own remote control and mobile features. I figured Anthropic would eventually build something like it, and they did. But once I had my own bridge running, it was already doing more: full conversation context, detailed permission prompts, and it wasn't locked to one agent. I'm constantly switching between Claude Code, Codex, Gemini, and Grok depending on the task, and I didn't want a separate babysitting workflow for each one. That's when I decided to generalize it and make it public instead of keeping it to myself. A few things I looked at before building this: - Claude.ai mobile lets you dispatch tasks to Claude while your Mac is awake, which is great for simple jobs. But it only controls Claude, gives limited real-time visibility, has simpler permission prompts, and no conversation feed. No Codex, Grok, or Gemini. - Generic push tools (Pushover, ntfy, etc.) just send a notification. No context, no way to reply or approve from the alert itself. - OpenClaw does remote control over Telegram for quick commands, but setup is involved and there's no dedicated UI showing full session context. So I built the bridge I wanted. Hooks on the agent side write events straight to Firestore, a small daemon keeps a heartbeat and listens for commands, and the phone app shows a real conversation feed instead of a beep. When the agent hits a tool call that needs approval, you get a push notification with the actual question and tappable options. Answer from your phone, and the daemon sends the keystroke back into the terminal session so the agent continues. You can also drop a note mid-session, like "skip the tests for now," without opening a laptop. End-to-end encryption (AES-256-GCM) went in once I realized I was piping real prompts and file paths through a third-party backend, and I wasn't comfortable with that myself. If I wouldn't use it that way, I wasn't going to ship it to anyone else. Right now it supports Claude Code, Codex CLI, Gemini CLI, and Grok CLI, with native iOS, Android, and macOS apps. Auth is QR-only on mobile: scan and go, no passwords. How do you handle unattended agent sessions today? Happy to dig into the architecture, the encryption approach, or why I went with four agents instead of just one.