llm/9ad11e16-7acb-4923-bb7e-5d14cd36cf3f/batch-7-750bce27-a069-45ae-af34-315c88a74ff2-input.json
The following is content for you to classify. Do not respond to the comments—classify them.
<topics>
1. Novelty vs. Rebranding Old Tech
Related: Commenters frequently note that SSHing into a remote machine is a standard practice that has existed for decades, comparing the article's framing to the infamous 'Dropbox comment' on Hacker News. Users express confusion over why a basic remote administration workflow is being presented as a new concept called 'Doom Coding,' while others argue that the integration of LLM agents like Claude Code provides a fresh layer of utility to the established setup.
2. Mobile Ergonomics and Friction
Related: A major theme is the physical difficulty of coding on a smartphone. Commenters discuss the pain of typing on touchscreens, the inability to view side-by-side diffs effectively on small screens, and the general clumsiness of managing terminal windows without a physical keyboard. Many users argue that while the setup is technically possible, the lack of screen real estate and input precision makes it impractical for serious engineering work.
3. Chat-Based and Async Interfaces
Related: To bypass the limitations of mobile terminal UIs, users suggest and share workflows that use chat interfaces like Telegram, Email, or WhatsApp to interact with coding agents. These setups allow users to send prompts and approve pull requests via natural language messages or buttons, treating the coding process as an asynchronous conversation rather than a real-time terminal session, which resolves many formatting and typing issues.
4. Session Persistence with Tmux
Related: Technical advice heavily features `tmux` (terminal multiplexer) as an essential tool for this workflow. Commenters explain that standard SSH connections drop when a mobile device sleeps or switches networks, whereas `tmux` allows the session to persist on the host machine. This enables users to seamlessly resume their work exactly where they left off, regardless of connectivity interruptions or app switching.
5. Alternative Mobile Environments
Related: Users discuss various apps and environments that serve as alternatives to the article's Termius setup. Android users advocate for Termux, which provides a local Linux environment without needing a remote host, while iOS users recommend Blink Shell or Shellfish for better Mosh and SSH integration. Some also mention using native Pixel terminal features or running local LLMs directly on the device to avoid latency and dependency on internet access.
6. Mental Health and Downtime
Related: The concept of 'Doom Coding' sparks a philosophical debate about work-life balance. Commenters question the healthiness of filling every moment of downtime with productivity, suggesting that time spent waiting or commuting might be better used for rest, observation, or 'micro-exercises.' There is criticism of the compulsion to code constantly, with some arguing that being present in social situations or relaxing is more valuable than 'vibe coding' on a phone.
7. Reliability and Network Latency
Related: The discussion highlights the technical challenges of mobile connectivity, specifically latency and dropped connections. Tools like Mosh (Mobile Shell) are frequently recommended over standard SSH because they are designed to handle intermittent networks and roaming between Wi-Fi and cellular data without killing the session. Tailscale is praised for simplifying the networking layer, though some prefer Wireguard for a lighter-weight alternative.
8. Wake-on-LAN and Power Usage
Related: Critiques of the requirement to leave a computer running 24/7 lead to discussions on energy efficiency and remote wake capabilities. Users share solutions using Wake-on-LAN (WOL) via routers or Raspberry Pis to turn on powerful machines only when needed. Others mention macOS settings like `caffeinate` or specific power configurations to ensure the host machine remains accessible without wasting electricity around the clock.
9. Verification and Code Review
Related: A critical point raised is the danger of 'fire-and-forget' coding with LLMs on mobile. Users note that verifying the code generated by AI is difficult on a phone due to limited visibility and syntax highlighting. The conversation touches on the risks of deploying code or merging pull requests without the ability to properly audit the logic or run tests, suggesting that mobile workflows are better suited for prototyping than production engineering.
10. Security Risks of Remote Access
Related: Several commenters express concern over the security implications of the proposed setup. Issues include leaving a computer unlocked at home, opening SSH ports (even via VPN), and the potential for bad actors to gain access to a local network. Discussions involve best practices such as using key-based authentication, locking the keychain via command line, and the general risks of exposing a development machine to remote connections.
11. Vibe Coding vs. Engineering
Related: There is a distinction drawn between 'vibe coding'—prompting an LLM to generate scripts or apps—and traditional software engineering. Some users view this workflow as 'slop' or merely prompting, lacking the depth of actual problem-solving, while others find it empowering for quick prototypes or hobby projects. This theme reflects broader tensions regarding the changing nature of software development in the age of generative AI.
12. Web-Based and Cloud Alternatives
Related: Users suggest that browser-based solutions like GitHub Codespaces, Replit, or self-hosted web IDEs (like `opencode`) offer a superior experience to terminal tunneling. These tools often provide better UI elements for mobile browsers and abstract away the need to manage hardware or VPNs, allowing users to code via a web interface that handles state management and environments automatically.
13. Social Acceptability
Related: The humorous notion of 'coding at the club' mentioned in the article draws specific reactions. Commenters joke about or criticize the anti-social nature of pulling out a phone to code in social settings like parties or bars. This overlaps with the 'doom scrolling' comparison, with some users suggesting that using a phone for work in social spaces is just as rude or 'gross' as using it for social media.
14. Hardware Workarounds
Related: To mitigate the interface limitations of smartphones, users discuss hardware additions such as folding phones, external Bluetooth keyboards, and 'thin client' setups using old laptops or tablets. Some mention specific devices like the 'Clicks' keyboard case or using AR glasses, highlighting that while the phone provides the compute or connection, better peripherals are often needed for actual productivity.
15. Agentic Workflows and Automation
Related: Discussions extend beyond simple coding to fully automated agentic workflows. Users describe setups where agents running on home servers are triggered via mobile to perform tasks, run scans, or manage infrastructure autonomously. This shifts the mobile interaction from writing code to orchestrating agents that perform the heavy lifting, reporting back status via push notifications or chat messages.
16. Subscription Fatigue vs. Open Source
Related: Comments reflect a wariness of paid subscriptions for tools like Claude Pro, Tailscale, or premium terminal apps. Users advocate for open-source alternatives such as Ollama for local LLMs, Wireguard for VPNs, and various free terminal emulators. There is a sentiment that basic remote coding shouldn't require a stack of monthly fees when free tools can achieve similar results with slightly more configuration.
17. Educational Value of LLMs
Related: Some users highlight the learning aspect of this workflow, noting that interacting with Claude Code allows them to understand new concepts (like API behaviors or network scanning) through the generative act. This counters the 'slop' narrative, suggesting that 'doom coding' can be a valid educational tool for hobbyists or those looking to understand how their devices and networks function.
18. Thin Client Philosophy
Related: The thread revisits the concept of thin clients, where the mobile device acts merely as a window into a powerful remote machine. Users compare this to historical mainframe/terminal workflows, arguing that the phone doesn't need to be powerful if it just renders text from a desktop. This philosophy underpins the preference for SSH/Mosh over running heavy local IDEs on the phone.
19. Code Quality and Maintenance
Related: Skepticism arises regarding the quality of code produced during short mobile bursts. Commenters worry about creating 'spaghetti code' or unmaintainable projects when working in fragmented sessions on a phone. However, others argue that for small utilities, prototypes, or personal tools, the quality is sufficient, and the ability to iterate quickly from anywhere outweighs the lack of rigorous structure.
20. Gatekeeping vs. Encouragement
Related: The comment section illustrates a divide between experienced users who gatekeep the term 'coding' or mock the setup, and those who encourage the experimentation. While some dismiss the article as trivial, others defend the author's enthusiasm, noting that lowering the barrier to entry and finding new ways to engage with technology is positive, even if the underlying methods are not strictly new.
0. Does not fit well in any category
</topics>
<comments_to_classify>
[
{
"id": "46520132",
"text": "I just use ConnectBot to ssh to my house. It runs tmux and vim well, especially with a little pocket-size folding bluetooth keyboard to go with it."
}
,
{
"id": "46518975",
"text": "Hang on, is Claude running on your phone/tablet and installing large dev dependencies right there? Or which parts of this stack are you replacing with termux?"
}
,
{
"id": "46520392",
"text": "Yeah, everything runs on the phone"
}
,
{
"id": "46523043",
"text": "Didn't vscode have a web browser version you could self host so where is the cursor version, anysphere?"
}
,
{
"id": "46519292",
"text": "If you don’t write a single line of code that’s not coding.\n\nOtherwise my customers are coders to. they to the same. The difference is the recipient of the order"
}
,
{
"id": "46519219",
"text": "I was coding a lot many years ago with a Nokia N900.\n\nThe loss of the physical keyboard ruined everything for me. I really need the sense of touch."
}
,
{
"id": "46522134",
"text": "Similarly I used to write Python on my Motorola Droid with the slide-out keyboard. But my touchscreen typing style these days relies heavily on auto-correct and trying to enter code is a real exercise in frustration."
}
,
{
"id": "46525340",
"text": "Did I read that right, that you have to have your computer unlocked at all times?\n\nYeah what can go wrong when you are travelling and your computer is at home unlocked lmao?"
}
,
{
"id": "46518872",
"text": "I run Claude Code on my phone itself via Termux."
}
,
{
"id": "46524928",
"text": "Does anyone have any good advice or resources on a good workflow to do this with web apps? There's some stuff I'd really like to solve, for myself/family, that would require a front and back-end with persistent storage.\n\nI would love to easily be able to set this up easily when a new idea pops into my mind and then have something running (locally or securely in some cloud) within a few hours/days. I wouldn't want to spend a ton of money for this though, nor have a lot of overhead to manage.\n\nEdit: In addition, I'd like some safeguards where I can't have the LLM of choice accidentally delete stuff or do other unintended things on my network."
}
,
{
"id": "46526403",
"text": "Replit is $25 a month but the best mobile allinone coding I have tried so far easy to push to host etc and you can kick off a stage then just pickup building where you left off anytime the termius/tmux/tailscale is fine but lot more effort even after you reach the command line. Horses for courses."
}
,
{
"id": "46518123",
"text": "I already doom code! I’ve always found coding a highly addictive activity and struggle to stop when I should. So for me it’s a hard no thanks :-)"
}
,
{
"id": "46518321",
"text": "This is very relatable - hence keeping \"doom\" in the moniker. Stay strong my friend"
}
,
{
"id": "46524229",
"text": "Vibe coding is not coding (unless by vibe-coding you meant buttplug.io)"
}
,
{
"id": "46524115",
"text": "Can't we do the same with an SSH client such as Termius?"
}
,
{
"id": "46519280",
"text": "I built my AI dungeon master game and play it using my phone, Tailscale, and an app called Termius.\n\nhttps://github.com/derekburgess/dungen"
}
,
{
"id": "46518867",
"text": "Vibe coding is such a bad word. It should be called prompting. Thats all it really is. Its like calling a point and click UI programming"
}
,
{
"id": "46524092",
"text": "I feel it depends whether you inspect and edit the code as part of the workflow, or just test what the AI produced and give feedback without participating in the coding yourself."
}
,
{
"id": "46526139",
"text": "Most of the slop i witness is the latter. This is evident in huge multi 10K pull requests. The code is just an artifact, while the prompting is the \"new\" coding."
}
,
{
"id": "46517690",
"text": "ha, I've recently been studying the original DOOM source code - does that count?"
}
,
{
"id": "46518005",
"text": "Yes"
}
,
{
"id": "46522483",
"text": "just don't"
}
,
{
"id": "46522448",
"text": "doom coding"
}
,
{
"id": "46517982",
"text": "Claude not needed to \"code from anywhere you are\" and certainly not from your phone. no LLM needed. no agents. Tailscale or any other VPN not needed\n\nuse a laptop. (trying to do it with only a phone-factor UI is madness.) have a mobile-friendly ISP if desired or needed. solved. been solved for decades\n\nso much of the AI BS hyping is about inventing supposedly unsolved problems. like Google showing me ads to convince me to use Gemini to write a README. no thanks, kids, have been able to do that for many decades using only my brain, eyes, fingers and vi/vim"
}
,
{
"id": "46518175",
"text": "How do I use a laptop while standing on a train each day? It sounds like a laptop is sufficient for you, but I suspect (based on myself and other responses in this thread) that a laptop is not always viable for many people; this tutorial appears targeted toward those people.\n\nI’ve actually considered a neck/shoulder support for a laptop in the past but decided against it because it’d be cumbersome and make me a theft target.\n\nAs for AI, personally speaking I use AI coding tools to allow me to continue enjoying some hobby side projects with less free time available with a kid. It’s been a massive boost to my happiness in a generally low stakes area. I’m curious to see if I can get a similar unlock on my short and interrupted commute times as well, which is why I (personally) find this article interesting."
}
,
{
"id": "46518243",
"text": "dont try to code while standing on a train. one of many antpatterns a wise engineer should learn to avoid, as part of polishing our craft. also: dont juggle chainsaws, etc ;-)"
}
,
{
"id": "46518523",
"text": "but also dont try coding on a laptop. use a proper desktop, or better yet, get time on a mainframe. the problem has been solved forever, juat do work from the workplace at a dedicated terminal, built for doing that work at."
}
,
{
"id": "46522281",
"text": "Not coding on a laptop is actually good advice?! My argument would be that you shouldn't be doing any work without plugging your laptop into a full size keyboard and mouse at least. And, ideally, at least one external display of some form (I recommend 2 or 3, but it depends on exact setup/total resolution/etc.). But it's your body, not mine.\n\nRegarding terminals, how often does this requirement occur in practice? Assuming it does, you can probably use your laptop for it, in which case, see above."
}
,
{
"id": "46519369",
"text": "groan HN needs a mute/block feature so we can mute/block folks like you. toxic. get a life"
}
,
{
"id": "46520513",
"text": "I wouldn’t want to code but I could easily be working on plans with Claude."
}
,
{
"id": "46518176",
"text": "You can't bring a laptop to the club! Truthfully I haven't tried so I will keep you posted."
}
,
{
"id": "46519466",
"text": "revived an ipad mini 2 (2013), rooted it and ssh-ed in and let claude handle the tailscale setup, terminal emulator selection, and prep work. perfect form factor and can test web apps via browser."
}
,
{
"id": "46524213",
"text": ">so much of the AI BS hyping is about inventing supposedly unsolved problems. like Google showing me ads to convince me to use Gemini to write a README.\n\nOkay, but how are you going to write your AGENTS.md file??"
}
,
{
"id": "46517804",
"text": "you missed the part where you're using tmux to have the same session between your phone and your laptop"
}
,
{
"id": "46518497",
"text": "Just learned about tmux lol - thank you for this!"
}
,
{
"id": "46521998",
"text": "Guys hear me out. If you ssh into your raspberry pi or any PC you could open console and run nano text.md file. Then you can manage your todo list from any device remotely. Stop doom scrolling and start disrupting todo subscription services. /s"
}
]
</comments_to_classify>
Based on the comments above, assign each to up to 3 relevant topics.
Return ONLY a JSON array with this exact structure (no other text):
[
{
"id": "comment_id_1",
"topics": [
1,
3,
5
]
}
,
{
"id": "comment_id_2",
"topics": [
2
]
}
,
{
"id": "comment_id_3",
"topics": [
0
]
}
,
...
]
Rules:
- Each comment can have 0 to 3 topics
- Use 1-based topic indices for matches
- Use index 0 if the comment does not fit well in any category
- Only assign topics that are genuinely relevant to the comment
Remember: Output ONLY the JSON array, no other text.
36