{"slug": "where-deepseek-phone-harness-goes-next-and-how-you-can-shape-it", "title": "Where DeepSeek Phone Harness goes next — and how you can shape it", "summary": "The developer of DeepSeek Phone Harness, an open-source tool that runs DeepSeek AI on mobile phones, has published a roadmap prioritizing push notifications, a PWA offline shell, and a persistent PTY terminal based on user requests. The project, which is about 4,000 lines of plain Node.js with no dependencies, is seeking contributors to implement these features.", "body_md": "#\nWhere DeepSeek Phone Harness goes next — and how you can shape it\n\nA roadmap, an honest status check, and a call for contributors. The most-requested feature ships first.\n\nTwo weeks ago this was a sketch. Today [DeepSeek Phone Harness](https://github.com/2903077918-lgtm/DeepSeek-phone-harness) runs on my phone every day. Here's where it's headed — and where you come in.\n\n##\nStatus check (honest)\n\n**Working well:**\n\n- Chat + streaming typewriter, multi-turn sessions\n- Tool cards: icon, status, file path, expandable args/result\n- Approval cards +\n`ask_user_question`\n\nanswer cards (no more deadlocks)\n- Model switching, image attachments, thinking disclosure\n- Terminal, file browser, task history, session management\n- Zero npm dependencies; runs on any Node 22+\n\n**Known limits (being honest):**\n\n- Web page, not a native app (PWA covers most of it)\n- Terminal runs commands one at a time — no full PTY interactivity yet\n- No push notifications yet — you poll, it doesn't call you\n- Cloud channel requires deploying your own Worker\n\n##\nRoadmap — most-requested first\n\n-\n**Push notifications** — task finished, approval needed → phone notifies without opening the page\n-\n**PWA offline shell** — add to home screen, feels native\n-\n**Persistent PTY terminal** — interactive commands, not just run-and-collect\n-\n**Multi-device / multi-account** — one agent, several controllers\n-\n**Native shell (Tauri/Electron)** — if the demand shows up\n\n##\nHow you can shape it\n\n-\n**Open an issue** with your most-wanted feature — the roadmap above is literally \"what people asked for\"\n-\n**PR welcome**: the codebase is ~4000 lines of plain Node + one HTML file. No build step, no framework to learn. A focused PR is a weekend at most\n-\n**Report the ugly**: a weird hang, a wrong tool card, a confusing flow — file it, I read everything\n\n##\nThe rule\n\nThe roadmap is ordered by request count, not by my preference. **If your feature isn't on the list, that's because nobody asked for it yet.** So ask.\n\nRepo:\n\n[https://github.com/2903077918-lgtm/DeepSeek-phone-harness](https://github.com/2903077918-lgtm/DeepSeek-phone-harness)\n\n*What's the one feature that would make you use this daily? One line is enough.*", "url": "https://wpnews.pro/news/where-deepseek-phone-harness-goes-next-and-how-you-can-shape-it", "canonical_source": "https://dev.to/joey020907/where-deepseek-phone-harness-goes-next-and-how-you-can-shape-it-gmm", "published_at": "2026-08-16 07:10:21+00:00", "updated_at": "2026-08-16 07:41:17.894714+00:00", "lang": "en", "topics": ["developer-tools", "artificial-intelligence", "ai-products"], "entities": ["DeepSeek Phone Harness", "DeepSeek", "GitHub"], "alternates": {"html": "https://wpnews.pro/news/where-deepseek-phone-harness-goes-next-and-how-you-can-shape-it", "markdown": "https://wpnews.pro/news/where-deepseek-phone-harness-goes-next-and-how-you-can-shape-it.md", "text": "https://wpnews.pro/news/where-deepseek-phone-harness-goes-next-and-how-you-can-shape-it.txt", "jsonld": "https://wpnews.pro/news/where-deepseek-phone-harness-goes-next-and-how-you-can-shape-it.jsonld"}}