Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Claude Code Remote Control

code.claude.com

Post reply on HN
Print view View original

201–210 of 336 posts

Re: Claude Code Remote Control

#201

Post by k8si »

exitb wrote: post #195

Maybe it’s related to what I tend to use the agents for, but I guess I don’t understand what is this for. Typically I try to structure the tasks in a way that require me to do or check something important when the agent gets back to me. If the agents query is trivial enough I can respond from my phone, it was likely not needed at all. If the agent finished - fine. It will have to wait until I get back in front of the…

- Plan mode -> answer questions/make corrections, continue planning

- Some of us don't do full yolo mode all the time, then tool approvals or code reviews are required, nice to do a quick review and decide if you need to go back to your computer or not

- Letting claude spin or handle a long-running task outside of normal work hours and being able to check in intermittently to see if something crashed

Re: Claude Code Remote Control

#203

Post by bavell »

elliotbnvl wrote: post #134
adamtaylor_13 wrote: post #100

Earlier quoted context omitted.

That's a bummer. I was looking forward to testing this, but that seems pretty limiting. My current solution uses Tailscale with Termius on iOS. It's a pretty robust solution so far, except for the actual difficulty of reading/working on a mobile screen. But for the most part, input controls work. My one gripe with Termius is that I can't put text directly into stdin using the default iOS voice-to-text feature baked i…

I’ve been doing this for a while [1], but ultimately settled on a building a thin transport layer for Telegram to accept and return media, and persistent channels, vastly improved messaging UX, etc. and ended up turning this into a ‘claw with a heartbeat and SOUL [2]. [1] https://elliotbonneville.com/phone-to-mac-persistent-termina... [2] https://elliotbonneville.com/claude-code-is-all-you-need/

Great posts! So far [2] is the only "claw" that has caught my interest, mostly because it isn't trying to do everything itself in some bespoke, NIH way.

Re: Claude Code Remote Control

#204

Post by david_shaw »

ValentineC wrote: post #197
yosefk wrote: post #189

Earlier quoted context omitted.

Coding is a solved problem. Problems with the code - these are far from solved, in fact they're multiplying, but coding is definitely solved

What does "solving" coding mean?

> What does "solving" coding mean?

Maybe this was sarcasm, but it's a good point:

"Coding" is solved in the same way that "writing English language" is solved by LLMs. Given ideas, AI can generate acceptable output. It's not writing the next "Ulysses," though, and it's definitely not coming up with authentically creative ideas.

But the days of needing to learn esoteric syntax in order to write code are probably numbered.

Re: Claude Code Remote Control

#205

Post by BloondAndDoom »

fny wrote: post #93

This is an extremely clunky and buggy prerelease, so don't try to hot fix prod from the toilet without a different mobile frontend. Right now: - You can't interrupt Claude (you press stop and he keeps going!) - At best it stops but just keeps spinning - The UI disconnects intermittently - It disconnects if you switch to other parts of Claude - It can get stuck in plan mode - Introspection is poor - You see XML in the…

Exactly my experience, I know they vibe code features and that’s fine but it looks like they don’t do proper testing which is surprising to me because all you need bunch of cheap interns to some decent enough testing

Re: Claude Code Remote Control

#206

Post by rfw300 »

monkeydust wrote: post #163
fny wrote: post #93

This is an extremely clunky and buggy prerelease, so don't try to hot fix prod from the toilet without a different mobile frontend. Right now: - You can't interrupt Claude (you press stop and he keeps going!) - At best it stops but just keeps spinning - The UI disconnects intermittently - It disconnects if you switch to other parts of Claude - It can get stuck in plan mode - Introspection is poor - You see XML in the…

Struggled with it also, given up (for now). I thought coding was a solved problem Boris?

I have little doubt where things are going, but the irony of the way they communicate versus the quality of their actual product is palpable.

Claude Code (the product, not the underlying model) has been one of the buggiest, least polished products I have ever used. And it's not exactly rocket science to begin with. Maybe they should try writing slightly less than 100% of their code with AI?

Re: Claude Code Remote Control

#207

Post by fittingopposite »

jasonjmcghee wrote: post #158

Posted elsewhere but will copy here. Been doing this for a while. - - - get tailscale (free) and join on both devices install tmux get an ios/android terminal (echo / termius) enable "remote login" if on mac (disable on public wifi) mosh/ssh into computer now you can do tmux then claude / codex / w/e on either device and reconnect freely via tmux ls and tmux attach -t - - - You can name tmux and resume by name via tm…

Yes. Doing the same. What is the advantage of this new feature? Tmux/Tailscale/Termius give you full control of your terminal. Or mainly to save the end user the hassle to set it up correctly?

Re: Claude Code Remote Control

#208

Post by fudged71 »

jasonjmcghee wrote: post #158

Posted elsewhere but will copy here. Been doing this for a while. - - - get tailscale (free) and join on both devices install tmux get an ios/android terminal (echo / termius) enable "remote login" if on mac (disable on public wifi) mosh/ssh into computer now you can do tmux then claude / codex / w/e on either device and reconnect freely via tmux ls and tmux attach -t - - - You can name tmux and resume by name via tm…

Do you have an alias or something so that every time you open CC, tmux is running?

How do you deal with multiple concurrent sessions of CC with this setup?

How important is mosh? I wasn't able to get it set up the last time I tried... ran into a bunch of issues.

Re: Claude Code Remote Control

#209

Post by sp1nningaway »

piker wrote: post #24

Running Claude Code from a phone just seems like a recipe for Alzheimer’s. Rest, then focus and build.

This kind of release shows Anthropic as a company is suffering from the same thing we all are right now. Removing the friction from having an idea and executing it stops you from remembering The Point. Yes, programming from your phone is an exciting modality and maybe even the future of how we work, but coding from your bedroom, AND the toilet, AND the woods AND your office is definitely (hopefully) not the future.

I wonder if is anyone working on an AI framework that encourages us to keep our eye on the big picture, then walk away when a reasonable amount of work is done for the day.

Yes, individuals are creating cool mobile coding solutions and Anthropic doesn't want to get left behind. I know I'm working my ass off at work right now because LLM coding makes it fun, but I also often don't prioritize what I'm doing for the big picture because I just try every thing that comes into my inbox, in order, because it's so fast to do with Claude Code.

We all sense it!: https://newsroom.haas.berkeley.edu/ai-promised-to-free-up-wo...> https://ghuntley.com/teleport/> https://steve-yegge.medium.com/the-ai-vampire-eda6e4f07163>

Re: Claude Code Remote Control

#210

Post by mattnewton »

exitb wrote: post #195

Maybe it’s related to what I tend to use the agents for, but I guess I don’t understand what is this for. Typically I try to structure the tasks in a way that require me to do or check something important when the agent gets back to me. If the agents query is trivial enough I can respond from my phone, it was likely not needed at all. If the agent finished - fine. It will have to wait until I get back in front of the…

I don't dangerously accept permissions outside of a few scripts I have reviewed as safe. This means claude gets stuck often when testing it's work, but also means it doesn't uninstall production workloads from the kubernetes cluster.
Post reply on HN