
Coding Agents in Your Pocket: The New Wave of Remote Control Apps
App Store companions now drive Claude Code, Codex, and Copilot from your phone. A builder’s checklist for E2E encryption, approvals, and multi-machine pairing.
Muhammad Tayyab

OpenAI’s Dots keep working after chat ends. A practical builders checklist for permissions, connected apps, approval gates, and monitoring.
At DevDay on 29 September 2026, OpenAI shipped Dots: always-on agents with their own cloud computer, a browser, and hooks into thousands of connected apps. The pitch is not “a smarter chat reply.” It is an agent that can keep researching, drafting, coding via Codex, and nudging you after you close the thread.
That is the product shift founders and builders need to design for. When the agent keeps working overnight, the real product surface is no longer the conversation—it is what you enabled, what still needs your say-so, and how you notice when it drifted.
This guide is a practical enable / gate / monitor checklist. It is not a feature dump, and it is not a security incident walkthrough. Treat it as the ops layer you should set before you let a Dot sit next to Slack, email, or your laptop.
Per OpenAI’s Introducing dots post, each Dot runs on GPT-6 Astra, gets a dedicated cloud machine, and can use plugins to reach more than 4,000 apps. You can message or call it in ChatGPT, reach the same agent in Slack or Microsoft Teams, and (soon) text it. Context is meant to travel with the agent across those channels.
Two details matter more than the mascot UI:
Rollout at launch: Pro and Business Premium in eligible markets (with regional caveats—Pro access was reported as limited outside the EEA, Switzerland, and the UK at start), one included Dot, Enterprise/Edu/Healthcare as admin-gated beta. Conversations with the Dot do not burn ChatGPT message limits; work it kicks into Codex or ChatGPT Work still counts.
Meta’s Muse landed a few weeks earlier as a consumer-leaning personal agent: plans, forms, shopping, travel, a dedicated app/WhatsApp surface, and its own secured cloud VM. Dots sit closer to work continuity—ChatGPT plus Slack/Teams, research and document loops, Codex for software, and (for companies) a preview of specialist dots with provisioned identity and systems access.
Both products sell the same structural idea: an agent with a computer that keeps going after you leave. If you already evaluated Muse as a product shape, Dots is OpenAI’s answer in that category—with a different home surface and a heavier workplace skew. For a security-oriented Muse checklist, see the earlier post on this site; this piece stays on how to operate an always-on agent day to day.
Use this as a go-live pass. Defaults are not a strategy.
Plugin permissions apply across Dots, ChatGPT, ChatGPT Work, and Codex (privacy & safety FAQs). Granting a write-capable email or CRM connection for “one chat experiment” also arms the always-on agent.
Do:
Don’t:
Connected apps are how Dots become useful—and how quiet mistakes become public. OpenAI’s own examples include drafting an invoice from an email thread and sending it after approval, or watching feedback and preparing PRs. Those workflows only stay safe if write destinations are intentional.
Prioritize connections in this order:
Slack/Teams deserve a special note: enabling channel presence means the Dot can post with its own identity, and channel members can see those messages. Only the Dot’s owner directs it; other people’s DMs do not start work. Still, a visible agent in a shared channel is an organizational surface, not a private notepad.
Dots ship with defaults for independent action vs confirmation. Custom Rules let you allow, require approval for, or block supported actions. They cannot override core takeovers (for example, changing a password), Auto-review, or the read-only limits on proactive research.
OpenAI’s ladder is useful to internalize:
Practical rule for founders: write Custom Rules before the first overnight run. Examples worth encoding early:
Auto-review sits in front of actions that can affect accounts or share information (OpenAI cites checking email recipients and body before send). Treat it as a seatbelt, not a chauffeur. OpenAI’s own line is blunt: Dots can still make mistakes—always review consequential work.
Always-on without inspection is just unattended automation with better branding.
Build a habit:
Enterprise operators should also review cloud capabilities (browser, network, computer use, password manager) independently of “Use dots.” The cloud machine does not inherit a member’s VPN or browser sessions—sign-ins on the agent machine are their own policy problem.
If you only remember one section, make it this.
Proactive research is fine for “watch this inbox / calendar / dashboard.” It still means the agent may pull more of your connected world into private notes and later conversations. Enable the watch list deliberately.
That sequence is boring on purpose. Persistent agents reward boring ops.
Always-on agents are no longer a lab demo. With Dots, OpenAI put a cloud computer and a plugin graph behind a teammate-shaped interface. The builders who get leverage will be the ones who treat permissions, connected apps, approval gates, and monitoring as first-class product decisions—not afterthoughts.
If you are wiring agents into a real product or team workflow and want a second set of eyes on the enable / gate / monitor design, get in touch.
Muhammad Tayyab builds consumer and AI products, including DripScore and projects under dawnapps.co. He writes for founders and builders shipping AI-native apps—practical systems, not hype decks.

App Store companions now drive Claude Code, Codex, and Copilot from your phone. A builder’s checklist for E2E encryption, approvals, and multi-machine pairing.

Meta’s Muse Mac 0-day showed how a stolen agent token can reach email, WhatsApp, camera, and linked devices. A practical trust checklist for founders.

Plugin4Shell showed SHA pinning alone can’t stop AI coding-agent plugin RCE. Here’s a practical builder checklist: versions, hosts, auto-updates, and hardening.