← Back to context

Comment by fny

16 hours ago

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 output instead of things like buttons

- One session at a time

- Sessions at times don't load

- Everytime you navigate away from Code you need to wait for your session to reappear

I'm sure I'm missing a few things.

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?

    • More generally, Anthropic's reliability track record for a company which claims to have solved coding is astonishingly poor. Just look at their status page - https://status.claude.com/ - multiple severe incidents, every day. And that's to say nothing of the constant stream of bugs for simple behavior in the desktop app, Claude Code, their various IDE integrations, the tools they offer in the API, and so on.

      Their models are so good that they make dealing with the rest all worth it. But if I were a non-research engineer at Anthropic, I wouldn't strut around gloating. I'd hide my head in a paper bag.

      2 replies →

    • I am constantly amazed how developers went hard for claude-code when there were and are so many better implementations of the same idea.

      It's also a tool that has a ton of telemetry, doesn't take advantage of the OS sandbox, and has so many tiny little patch updates that my company has become overworked trying to manage this.

      Its worst feature (to me at least), is the, "CLAUDE.md"s sprinkled all over, everywhere in our repository. It's impossible to know when or if one of them gets read, and what random stale effect, when it does decide to read it, has now been triggered. Yes, I know, I'm responsible for keeping them up to date and they should be part of any PR, but claude itself doesn't always even know it needs to update any of them, because it decided to ignore the parent CLAUDE.md file.

      1 reply →

  • It is solved in his org. He never promised quality software, though.

    You get a buggy electron app and they get billions in valuation.

    Clearly no one values quality anymore. 1000% yolo

  • He is trolling to increase the stock price before IPO

    • OK, but seriously... if Anthropic is on the "best" path, aside from somehow nuking all AI research labs, an IPO would be the most socially responsible thing that they could do. Right?

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

  • No there is a wide gap between good and bad testers. Great testers are worth their weight in gold and delight in ruining programmer's days all day long. IMO not a good place to skimp and a GREAT place to spend for talent.

    • > Great testers are worth their weight in gold and delight in ruining programmer's days all day long.

      Site note: all the great testers I've know when my employers had separate QA departments all ended up becoming programmers, either by studying on the side or through in-house mentorship. By all second hand accounts they've become great programmers too.

  • Thats not true. Even for testing things, you need to do thoroughly now because standards are high.

    • I don't think you need any qualifications to run the app and realize that it doesn't run.

      This is the bar we're at now.

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.

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.

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

Not just the mobile app, but also Claude Code Web is super unreliable.

Frequently chews through lots of expensive Opus tokens, then it just stops with no communication about why or what's next.

No way to tell what it's done, what's remaining to complete.

Only choice is to re-run everything and eat the cost of the wasted time and tokens.

Sounds like something that was vibe coded :)

  • I'm willing to bet most of their libraries are definitely vibe coded. I'm using the claude-agent-sdk and there are quite a few bugs and some weird design decisions. And looking through the actual python code it's definitely not what I would classify 'best practice'. Bunch of imports in functions, switching on strings instead of enums, etc.

    I had to downgrade to an earlier release because an update introduced a regression where they weren't handling all of their own event types.

    • I think they are betting that any of this code is transient and not worth too much effort because once Opus 5 is traimed, they can just ask it to refactor and fix everything and improve code quality enough so that things don't fall apart while adding more features, and when opus 5.5 comes out it will be able to clean up after opus 5. And so on. They don't expect these codebase to be long lived and worth the time investment.

    • A few weeks ago the github integration was completely broken on the claude website for multiple days. It's very clear they vibe code everything and while it's laudable that they eat their own dogfood, it really projects a very amateurish image about their infrastructure and implementation quality.

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

> - 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.

  • If its running a background process then one escape is not enough, need two for message in que to be picked up and adressed.

  • Latency is like what, 50ms? You can’t explain these with latency. It’s just slop work from Claude.

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

Omnara founder here.

We’ve been building in this space for a while, and the issues listed here are exactly the hard parts: session connectivity, reconnection logic, multi-session UX, and keeping state in-sync across devices. Especially when it comes to long running tasks and the edge cases that show up in real use.