{"slug": "the-agent-s-next-stop-is-your-pocket-why-mobile-may-be-the-agent-s-best-form", "title": "The agent's next stop is your pocket: why mobile may be the agent's best form", "summary": "A developer argues that mobile devices, not browsers, are the ideal platform for AI agents, citing the shift from desktop-bound interaction to asynchronous, decision-focused mobile use. The developer released DeepSeek Phone Harness, an open-source tool that lets users dispatch agents and return for results, embodying the principle that users shouldn't have to babysit agents.", "body_md": "We moved agents from the terminal to the browser. Now it's time to move them into your pocket. This isn't \"mobile adaptation\" — it's a shift in interaction paradigm.\n\nDeepSeek Harness just went open source, and the community is excited — models, tools, agent loops, all pluggable. But amid the noise I noticed something:\n\nEveryone's discussing what agents\n\ncan do. Almost nobody discusseswhere you use them.\n\nLet's talk about the second one — and I'll give you my own answer.\n\nFirst generation: open a terminal, sit down, watch.\n\nSecond generation (Web GUI): open a browser, sit down, watch.\n\nEssentially it's still **\"you must be seated at the computer.\"** But an agent's whole value is that it does the work *for* you — and yet you have to babysit it. Is that reasonable?\n\nAll these share one trait: **you're not at the computer, but the agent is working.** Who's the remote? The phone is the only answer.\n\nI used to think mobile = shrunk web. After actually building it, I found mobile's interaction logic is fundamentally different:\n\n**1. From \"multiple windows\" to \"a single timeline\"**\n\nThe web has panels side by side: conversation, tool output, approval dialogs. Mobile naturally has one **vertical timeline** — user message, agent reasoning, tool cards, approval cards, question cards, all linear. The agent's work becomes a **replayable pipeline**, which is clearer, not less.\n\n**2. From \"clicking around\" to \"making decisions\"**\n\nOn desktop you click everywhere. On mobile, thumb reach is limited, which forces interactions into **\"look once → decide\"**: allow this tool call or not? How to answer this question? — judgment calls, not browsing sessions.\n\n**3. From \"accompanying\" to \"async\"**\n\nOn desktop you sit with the agent. On mobile you **dispatch → leave → come back for results.** That pushes the agent side to do state management properly (task queues, result retention, failure notifications) — which is exactly where agent products are heading.\n\nBased on the above, I built [DeepSeek Phone Harness](https://github.com/2903077918-lgtm/DeepSeek-phone-harness):\n\nIt's no revolutionary invention — just a plain answer: **\"when the agent works for you, you shouldn't have to be there.\"**\n\n**What do you think is the agent's next form?**\n\nComment below — this is a topic worth arguing about.", "url": "https://wpnews.pro/news/the-agent-s-next-stop-is-your-pocket-why-mobile-may-be-the-agent-s-best-form", "canonical_source": "https://dev.to/joey020907/the-agents-next-stop-is-your-pocket-why-mobile-may-be-the-agents-best-form-3p10", "published_at": "2026-08-16 06:54:51+00:00", "updated_at": "2026-08-16 07:11:31.829882+00:00", "lang": "en", "topics": ["ai-agents", "ai-products", "developer-tools", "artificial-intelligence"], "entities": ["DeepSeek", "DeepSeek Phone Harness", "DeepSeek Harness"], "alternates": {"html": "https://wpnews.pro/news/the-agent-s-next-stop-is-your-pocket-why-mobile-may-be-the-agent-s-best-form", "markdown": "https://wpnews.pro/news/the-agent-s-next-stop-is-your-pocket-why-mobile-may-be-the-agent-s-best-form.md", "text": "https://wpnews.pro/news/the-agent-s-next-stop-is-your-pocket-why-mobile-may-be-the-agent-s-best-form.txt", "jsonld": "https://wpnews.pro/news/the-agent-s-next-stop-is-your-pocket-why-mobile-may-be-the-agent-s-best-form.jsonld"}}