I really don't want to trust an AI company with a remote access door on my setup
Claude Code Remote Control
21–30 of 336 posts
Re: Claude Code Remote Control
#22So Microsoft/Github copilot was ahead of its time with AI driven PRs?
I honestly think this is definitely where (at least part of) the industry is heading, yes.
This is not to say engineers are getting replaced — but, certainly, they are changing their work. And, sure, maybe _some_ of them are being replaced. Not most of the ones I know, though. They are essential to orchestrate, curate, maintain, and drive all of this.
(Now, do they want to orchestrate it? Whole different story...)
Re: Claude Code Remote Control
#23Small UX note: the first time you run the command it only shows a URL. It's not until you run it again that you discover it also generates a QR code, which is actually the fastest way to open it on your phone. Would be nice if the QR showed up on the first run too, almost missed it.
Re: Claude Code Remote Control
#24Running Claude Code from a phone just seems like a recipe for Alzheimer’s. Rest, then focus and build.
Re: Claude Code Remote Control
#25Earlier quoted context omitted.
Perhaps it took a while to figure out how to do it over HTTP, especially the security stuff. With e.g. tmux you'll piggyback on decades of SSH development.
> SSH development. Or Mosh, just like OP said. Mosh handles interruptions much better than SSH does
As I understand it, Mosh piggybacks on SSH. Have they recently dropped the SSH negotiation?
Re: Claude Code Remote Control
#26Running Claude Code from a phone just seems like a recipe for Alzheimer’s. Rest, then focus and build.
On the other hand, you lose a lot of time if you step away from a session and it gets stuck asking for permission to do something simple.
Re: Claude Code Remote Control
#27Running Claude Code from a phone just seems like a recipe for Alzheimer’s. Rest, then focus and build.
There are two types of software engineers: Those who do and then think, or those who think and then do. Claude Code seems to strictly be for the former, while typically the engineers who can maintain software long-term are the latter.
Not sure if we have any LLM-tooling for the latter, seems to be more about how you use the tools we have available, but they're all pulling us to be "do first, think later" so unless you're careful, they'll just assume you want to do more and think less, hence all the vibeslop floating around.
Re: Claude Code Remote Control
#28On Android app it needs Claude GitHub connection with scope to act on my behalf! Otherwise it won't work in the app. Really do NOT like that!
Why does the remote control needs that? For what?
I rather use the common developer tools like termux or mosh etc. on a phone if I need that functionality.
Re: Claude Code Remote Control
#29so is harnessing tmux/tailscale new "rsync/FTP is enough" thing nowadays?
Re: Claude Code Remote Control
#30I really don't want to trust an AI company with a remote access door on my setup
Regular claude code is already a remote access door to your setup, once you've granted a few command execution permissions. (e.g. if it can edit your code and run the test suite)