Also broken for me.

First of all /remote-control in the terminal just printed a long url. Even though they advertise we can control it from the mobile app (apparently it should show a QR code but doesn't). I fire up the mobile app but the session is nowhere to be seen. I try typing the long random URL in the mobile browser, but it simply throws me to the app, but not the session. I read random reddit threads and they say the session will be under "Code", not "Chats", but for that you have to connect github to the Claude app (??, I just want to connect to the terminal Claude on my PC, not github). Ok I do it.

Now even though the session is idle on the pc, the app shows it as working... I try tapping the stop button, nothing happens. I also can't type anything into it. Ok I try starting a prompt on the pc. It starts the work on the PC, but on the mobile app I get a permission dialog... Where I can deny or allow the thing that actually already started on the pc because I already gave permission for that on the PC. And many more. Super buggy.

I wonder if they let Claude write the tests for their new features... That's a huge pitfall. You can think it works and Claude assures you all is fine but when you start it everything falls apart because there are lots of tests but none actually test the actual things.

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

Struggled with it also, given up (for now).

I thought coding was a solved problem Boris?

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 into the keyboard.

On top of that is something they should have had from earlier times. My biggest pain point is to not to be able to continue from my phone. I just use a service to pipe telegram to any cc session in the dev machine. This is the number 1 reason why I got excited by openclaw in the first place but its overkill to have it just to control cc

Why couldn't they prompt Claude code to fix all the issues?

I think they should be aware that CC is big enough codebase that they can't vibe code anymore.

Sounds like something that was vibe coded :)

Remember 100% of Claude Code is written by Claude

> - You can't interrupt Claude (you press stop and he keeps going!)

This is normal behavior on desktop sometimes its in the middle of something? I also assume there's some latency

> - At best it stops but just keeps spinning

Latency issues then?

> - It can get stuck in plan mode

I've had this happen from the desktop, and using Claude Code from mobile before remote control, I assume this has nothing to do with remote control but a partial outage of sorts with Claude Code sometimes?

I don't work for Anthropic, just basing off my anecdotal experience.

check out codecast.sh its so far ahead :)

oh. i was excited for a native alternative to happy coder, or sshing to a tmux session, but i guess not:/

[dead]