Yeah, same – mine gives Claude a proxy to the host's Docker socket that disallows mounting anything outside the dev dirs or starting a --privileged container, so it can run tests.
And for my iPod touch! I was prepared to keep using it around the house – it's so much lighter than a phone – but I was worried about leaving it logged into iCloud Keychain if it wasn't going to get this fix.
The "funniest" thing about this is that in any other context, this administration absolutely insists that everyone should be called only by their legal name, not any other name that they prefer because they think it better suits their identity.
It's a bit more than zero, because I have substantial tooling around Claude Code – subagents, skills, containerization, &c – that I'd have to (have Opus...) reimplement.
Exactly. If Codex is really as good, it should have no problem porting any settings or config from the Claude setup. (and I do believe it wouldn't have much of a problem)
And they had it solved! 3D Touch worked perfectly – you pushed the screen hard to get a cursor, moved it to the start of the selection, and pushed hard again to drag to the end. They killed it because "not all iPhones had the hardware to support it" or something.
Space bar which is at... the bottom of the screen, so if you want to move the caret down... 3D Touch worked _anywhere_, also had no delay, and hard press a second time was much more convenient for selection.
that deserves a whole separate opera. why does moving the cursor to start/end almost always place it one character off? same when trying to use touch on text for it.
This. I feel like this is due to small shifts when lifting the finger. For the life of me, I cannot get myself to lift it like the testers at Apple do, and so I wished the product itself could go through learning phase; studying intentions and what actual touches happen.
Apple devs are probably doing something with the touch returned by the touchUpInside callback. This is an extremely, extremely common bug in iOS apps, not just with Apple developed software.
Devs love the symmetry of their touch handling code and often have the finger-down, finger-moved, and finger-up callbacks from the system all call the same handleTouch function they wrote. As you can tell, however, the touch from the finger up callback is often better discarded or handled differently otherwise you get these sort of bugs
Unfortunately, it's still bad. It's a bit better than dragging the handles of the selected area, but if I go to far and want to reduce the selected area, it doesn't work anymore.
> You just wanted to move the cursor. Now everything is selected.
> You want to position the cursor at the end of a line. You tap. It selects the last word. You try to grab the handle — it doesn't respond and deselects. You tap again, now it selects the whole sentence. You tap blank space to deselect — nothing. You tap five more times. On the fifth, it selects all. You switch apps hoping the selection disappears. You tap and hold — sometimes text selects, sometimes a menu appears, sometimes nothing. Got a Magic Keyboard? Good luck — trackpad selection just doesn't work half the time, but touching the screen does. Eventually you select all, delete everything, and retype from scratch. Apple has had 17 years to figure out touch text selection. This is where they landed.
https://github.com/nicwolff/claude-container/
reply