llm/9ad11e16-7acb-4923-bb7e-5d14cd36cf3f/batch-6-3b04de59-7d1d-4d62-abd5-2b9116cbd65b-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": "46518646",
"text": "I am a huge fan of driving agents from my phone, though this is one of the places where I don’t think terminal UIs work. Agents need a web UI for phones."
}
,
{
"id": "46524084",
"text": "Just install proper development tools on the device, some examples from my setup,\n\n- Pydroid\n\n- C# Shell .NET IDE\n\n- Pascal N-IDE\n\n- Shader Editor"
}
,
{
"id": "46518150",
"text": "I am looking for some open source terminal for iphone .I have code server running which i can just use terminal from vs code on safari"
}
,
{
"id": "46522379",
"text": "I’m wary of enabling ssh/remote login. It seems like it could be an attack vector."
}
,
{
"id": "46517983",
"text": "to keep your mac awake:\n\ncaffeinate -di"
}
,
{
"id": "46518202",
"text": "Thank you! Did not know about this command before - good to know"
}
,
{
"id": "46517671",
"text": "Please mask your identifiers, unless they are already spoofed. You potentially give out a lot of your info to bad actors.\n\nOther than that, love it :)"
}
,
{
"id": "46518148",
"text": "Thanks! I did not sppof! I thought that since it was my local Tailnet, only devices on that net could connect. I just rebuilt the network as a precaution."
}
,
{
"id": "46518511",
"text": "Most of the time it's probably fine, but we should assume we don't know about all the attack vectors bad actors might use, so better safe than sorry.\n\nI forgot to say that I _absolutely loved_ the photos!"
}
,
{
"id": "46518645",
"text": "Very true! Was that Rumsfeld, right? Unknown unknowns?\n\nAnd thank you! I'm glad you appreciated the humor. I'm still a novice builder, so the thought of ssh-ing to my home computer from a plane geeks me out. I'm about 20 years late but I'm here now!"
}
,
{
"id": "46517873",
"text": "Does this approach work for anyone? For my life, I've found that if I'm not behind the computer then I'm not in a productive situation anyway, even with AI access. I don't have a setting where I can concentrate for a long time and think clearly. For examole when watching children, doing groceries, during transit (probably have to change train in 20m, or walking to next destination). No convenient access to a notepad and pen. On a phone it's also inconvenient to do research.\n\nFor me personally I've found two better uses of in-between time:\n\n1. Micro exercises. Really important for health and longevity, especially when it's hard to find dedicated time for exercise.\n\n2. Resting. This means no phone. Yeah hard to resist doom scrolling. Just relaxing muscles and breathing exercises, calming down the nervous system. Increases long term resillience and reduces stress.\n\nSo I'm a bit puzzled. If you are in a situation where you can concentrate, why not just pull out a laptop? Typing on phone is really annoying. Even complex conversations with AI I prefer doing on a laptop.\n\nPerhaps there are coding tasks where the prompt is not too complex and it's more about writing code. But you still have to review the result. That's even more annoying on a phone than writing text."
}
,
{
"id": "46517943",
"text": "I feel similarly. I am happiest and healthiest all round when I focus on the one thing I have chosen to do at any given time rather than figuring out ways to multi-task.\n\nI do however enjoy choosing to do math/coding adjacent activities for leisure or learning sometimes when I'm away from the computer. I've found that it was a net positive in my life to add in puzzles/exercises that I can do with pen and paper in those circumstances."
}
,
{
"id": "46518457",
"text": "Yeah, even if I'm on a plane or a train I probably wouldn't pull out my laptop.\n\nLack of space, vibrations etc. even though I can do a lot of work offline if the internet is spotty. It's just not enjoyable.\n\nI prefer to read or chill out.\n\nI kind of envy people who are like oh yeah I coded the feature on the flight... I can't really get in the zone in that environment.\n\nSaying that, I assumed this post was a joke. ssh to a work machine or a personal machine through a VPN is not new, even if you happen to run claude code in that terminal.\n\nI'm interested in these \"micro exercises\"."
}
,
{
"id": "46523202",
"text": "Micro exercises: It's nothing fancy. While walking in the park, watching the kids play, waiting in a queue or in the train or something, when you have a minute to spare, you can do wall push ups, isometrics, leg raises, step jacks, squats, row pull with your jacket against a pole, etc. Exercises that don't require equipment. If you get an exercise band then you can carry it with you (very light and compact) and then there will be more types of exercises you can do. This will raise some looks, but they tend not to be negative, some people even praise me for staying active in unusual contexts.\n\nAnother thing I can recommend is Chinese style radio calisthenics (guang bo ti cao, look it up on Youtube, all Chinese people learn it in primary school and do them daily at school). Full body cardio like and stretching exercises that you can do while staying in one place (you just need space around you). Takes 5-10m, better warming up than just walking and swinging arms and covers a lot of basic things. The entire approach seems virtually unknown in the west."
}
,
{
"id": "46518018",
"text": "It worked for me for finishing my app (vps+shellfish+gemini-cli), I've done a lot of coding like this on the train and in between sets in the gym, picking up on the more complicated stuff when at home.\n\nBut also all of the changes I made from the phone were incremental."
}
,
{
"id": "46518586",
"text": "^^ I probably rely on AI slop than most people on this thread. I've found with the gaps with waiting on Claude Code output match the frequency I'm already checking my phone out of addiction. By no means the healthiest way to spend my time, but if I wanted to spin up a simple website or build out the framework for a project doom coding works for me!\n\nAgreed 100% there are healthier uses of my time!"
}
,
{
"id": "46519970",
"text": "I just have it send me a push notification."
}
,
{
"id": "46523237",
"text": "In between sets!? I've found that if I do any activity in between sets (like watching Twitter) I'll just end up spending way too much and then make the exercise session super long. Also I can't focus and write a serious prompt or review serious results in just or 3 minutes. But maybe it works if the app is sonething you've recently worked on and you already have very clearly in your mind what you want, it just needs to be done."
}
,
{
"id": "46527307",
"text": "For incremental changes 1-2 sentences are usually enough. Also, since the program itself is a workout app with live reload, I can actually fix bugs while I’m using it.\n\nAs for too long of a wait I agree, it makes the sessions longer. Ideal window is after a heavy superset where waiting for 3-5 minutes is not a waste.\n\n(Note that I’m not doing this for my real job, just for my personal project)"
}
,
{
"id": "46523069",
"text": "I think the problem you are having is that you are actually thinking clearly and rationally and are not suffering from this incessant brain rot that is the new normal."
}
,
{
"id": "46520622",
"text": "I love this! This concept on steroids is one of the main reasons I made https://github.com/knowsuchagency/vibora after trying both happy.engineering and Vibe Kanban for remote coding. There's the claude mobile app, too, but I want to run Claude on my own hardware in a terminal"
}
,
{
"id": "46523138",
"text": "Why not Claude Code on web/cloud linked to your GH repo?"
}
,
{
"id": "46519177",
"text": "İ've been using Termux (and Vim) to code on my phone for years, way easier than this setup."
}
,
{
"id": "46520637",
"text": "My setup is very similar.\n\nAfter you log in you can unlock keychain by running this command\n\n‘security unlock-keychain’"
}
,
{
"id": "46519586",
"text": "I was expecting this to be about using Termux or similar. Why are LLMs involved here?"
}
,
{
"id": "46518260",
"text": "Why would I need claude code for remote programming, if I could just use ssh and tmux?"
}
,
{
"id": "46522139",
"text": "Yeah I just built www.makerkit.io for the exact same thing"
}
,
{
"id": "46520357",
"text": "I’ve thought about this many times, maybe with a custom telegram bot!"
}
,
{
"id": "46518498",
"text": "this is literally my setup and it is a game-changer:\n\ntailscale, tmux, codex/claude code, mosh, blink shell (iOS) https://blink.sh/"
}
,
{
"id": "46518784",
"text": "Curious if you are directly running mosh on macOS. Last I checked, it was broken on macOS Tahoe, so I have been relying on tmux for surviving flaky ssh connections."
}
,
{
"id": "46518876",
"text": "i use both tmux and mosh-server\n\ni install them via nix-darwin (I've abandoned homebrew)\n\ni am on Tahoe latest beta"
}
,
{
"id": "46518877",
"text": "claude.ai + vercel and you can do it all without anything but your phone\n\ntheir web interface lets you use Claude code and push changes to a GitHub repository\n\nvercel can auto build from a GitHub repo\n\neven less setup and infrastructure needed"
}
,
{
"id": "46522370",
"text": "I like to \"doom read\" books."
}
,
{
"id": "46523586",
"text": "is termius free, I was wondering if there is a free open source ios terminal"
}
,
{
"id": "46523743",
"text": "Why Tailscale instead of plain wireguard?"
}
,
{
"id": "46524361",
"text": "probably because you just install it, then you log in and youre done. tailscale takes care of the rest. going through any more effort just so you can write some slop code is probably not worth it"
}
,
{
"id": "46522061",
"text": "ollama runs locally in termux preferably on proot-distro (with less \"coding power\")"
}
,
{
"id": "46526585",
"text": "Fixed IPv6 workstation, ssh (pre-shared key) and vim, 4G usb modem, a \"big\" screen, nice battery life, \"code anywhere\" on your workstation (the best would be a \"backpack\" modular system: a RISC-V board in its case slapped to a \"big\" DP/eDP screen on a stand, an usb dvorak [ortholinear|columnar] keyboard, a 4[5]G usb modem (using the USB modem standard) with a IPv6 enable mobile ISP sim card, and a rather good battery pack.\n\n(I even use a webcam to capture what my monitor does display when I do remote coding of low level GFX oriented software! Actually my wayland compositor for linux and AMD GPUs)\n\nBTW, IPv6 = ZERO NAT to setup, delicious.\n\n\"It's magic\"."
}
,
{
"id": "46525310",
"text": "Account created 16 hours ago posting highly dubious AI hype? This user is almost certainly part of the intense astroturfing campaign likely financed by Anthropic that has been ongoing for days/weeks now."
}
,
{
"id": "46524445",
"text": "Calling \"telling the LLM what to do\" coding is dishonest, and I have no respect for any of this."
}
,
{
"id": "46518036",
"text": "> What You'll Need\n\n> A Computer running 24/7 with Internet Connection\n\n> A Smartphone\n\n> A Claude Pro subscription\n\nOr.. just install Termux and do it the same way you do it anywhere else?"
}
,
{
"id": "46518054",
"text": "Termux with a 10-keyless BT keyboard in bed was a comfy way to solve AOC problems considering it released at midnight in my timezone."
}
,
{
"id": "46518246",
"text": "This comment taught me about Termux. Good to know!"
}
,
{
"id": "46521240",
"text": "Make sure you install it via FDroid. Also grab Termux:API to be able to write little apps with bash scripts. Here's one I did which gives a notification based interface to Pandora: https://github.com/ijustlovemath/pbr"
}
,
{
"id": "46518217",
"text": "And what's the recommendation for iOS? Because, as it turns out, the Termux app on the App Store is not the same as the one on the Play Store, just uses the same name."
}
,
{
"id": "46518344",
"text": "use blink https://apps.apple.com/nl/app/blink-shell-build-code/id15948..."
}
,
{
"id": "46518398",
"text": "Or shellfish. [1]\n\n[1] https://secureshellfish.app/"
}
,
{
"id": "46524048",
"text": "Shellfish is underrated. It has a very convenient tmux integration (auto-restore a specific tmux session per host to work around iOS suspending background apps), supports SSH tunneling via other configured hosts, and can be used as an SFTP file provider for other iOS apps. It’s also generally polished and supports the expected standard terminal features.\n\nThere’s a few settings I wished were possible, like using volume buttons as modifier keys in Emacs (I’ve heard about this in other apps), but mostly it works fine."
}
,
{
"id": "46522081",
"text": "Blink will end up giving you an experience similar to the stack in doom-coding (as Blink's local capabilities are very limited thanks to iOS rules) except you have to pay a subscription.\n\nTermux on Android will let you do anything you can do on your standard Linux PC."
}
,
{
"id": "46526069",
"text": "Hmm, maybe I got grandfathered in or something because I paid some set price a few years ago and have not had a subscription for blink, and just use it the same way I would use Ghostty and then ssh into another machine. Use something else if it needs a sub. Some sibling comments had some recommendations."
}
]
</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.
50