{"slug": "why-i-open-sourced-the-tool-i-built-just-for-myself", "title": "Why I open-sourced the tool I built \"just for myself\"", "summary": "A developer open-sourced DeepSeek Phone Harness, a tool originally built for personal use to remotely control a desktop agent from a phone. The project, released under MIT license with zero dependencies, aims to share hard-won knowledge about the agent's event stream, including a critical bug where the agent-question channel is separate from the approval channel, causing silent deadlocks. The developer found that open-sourcing improved the tool significantly within a week.", "body_md": "It started as a selfish project: a phone remote for my own desktop agent. Three reasons made me push it public. The third one surprised me.\n\nI built [DeepSeek Phone Harness](https://github.com/2903077918-lgtm/DeepSeek-phone-harness) for one reason: I was in bed at 1 a.m., wanted to send a task to the agent on my computer, and refused to get up. Pure selfishness.\n\nIt worked so well that I kept using it. And then I had to decide: keep it private, or open it up?\n\nThe hardest bug — the one that made tasks hang forever — was invisible until you knew it existed: **DSH's agent-question channel is separate from its approval channel.** Miss it, and every `ask_user_question`\n\ncall deadlocks your pipeline silently.\n\nThere's no way to discover this by reading docs. You have to capture a real event stream, notice a frame type nobody told you about, and chase it for two days. **That kind of hard-won knowledge should be public** — someone else shouldn't have to re-pay that tuition.\n\n\"Phone as a remote for a desktop agent\" is a genuinely useful pattern. But right now it lives in scattered, platform-specific implementations. An MIT-licensed, zero-dependency reference implementation lowers the floor: anyone can clone it, read ~4000 lines, and build their own — for DeepSeek Harness, or any agent runtime with a similar event model.\n\nOpen-sourcing it forced me to do things I wouldn't have bothered with otherwise:\n\n**The tool got better in the week after open-sourcing than in the week before.** That surprised me, and it's the reason I'll keep building in public.\n\nNothing, really. But if you take one thing: **when you fix a nasty bug nobody warned you about, write it down and put it where others can find it.** That's the entire spirit of this project.\n\nRepo (MIT, zero dependencies, three-minute setup):\n\n*Have you open-sourced something you built \"for yourself\"? What changed? I'd genuinely like to know.*", "url": "https://wpnews.pro/news/why-i-open-sourced-the-tool-i-built-just-for-myself", "canonical_source": "https://dev.to/joey020907/why-i-open-sourced-the-tool-i-built-just-for-myself-56j1", "published_at": "2026-08-16 07:10:20+00:00", "updated_at": "2026-08-16 07:41:20.663915+00:00", "lang": "en", "topics": ["ai-agents", "developer-tools"], "entities": ["DeepSeek Phone Harness", "DeepSeek"], "alternates": {"html": "https://wpnews.pro/news/why-i-open-sourced-the-tool-i-built-just-for-myself", "markdown": "https://wpnews.pro/news/why-i-open-sourced-the-tool-i-built-just-for-myself.md", "text": "https://wpnews.pro/news/why-i-open-sourced-the-tool-i-built-just-for-myself.txt", "jsonld": "https://wpnews.pro/news/why-i-open-sourced-the-tool-i-built-just-for-myself.jsonld"}}