It is hands down the most user hostile UX I put up with. The fact that I put up with it speaks volumes about the value proposition that the underlying models bring to the table.

I’m in the process of dumping codex for more open harnesses that don’t add problematic new features every week. Because Anthropic insists that I have to use their harness with the subscription, eventually I’m either going to wrap `claude -p` to get away from the crappy TUI or else I’ll just unsubscribe and use other models. Their bad UX has alienated me as a paying customer.

▲

ctxc 5 hours ago | parent [-]

Can you give me examples of things you don't like? Because I unironically admire how they improve UX. It's subtle, minimal, yet insanely useful.

Listed a few in my other comment

	▲	apsurd 4 hours ago \| parent \| next [-]
		I'm not who you're asking but for me I am right now going through the insanity of providing plugin/mcp/tool access across environments. This is in codex which as I mentioned is intentionally trying to provide mass-market ergonomics. But with that comes incomprehensible configuration that's also a moving target. chat/work/codex/remote/cloud are all different things. And each client exposes different abilities and hides others. And looks like only the web-ui is the most up to date because other targets need releases. As a developer I understand why it's in its current state, but that in no way excuses it as acceptable ux. Like of course codex is the most powerful and "just" run `npx blah blah` but no, I'm not running randomly piped code on my personal computer and even if I didn't care about privacy it means I can only run this locally with my laptop on. "leave your laptop on and access from your phone" is not a good idea. It only adds to the surface area of confusion. Ux no good.
	▲	arcanemachiner 4 hours ago \| parent \| prev [-]
		Try using the "rewind" feature to go back to a previous message. Went too far? Oops, it's not accessible from the Claude Code UI anymore! You can get the agent to dredge up the info from the session logs, but you'd better hope they put the pieces together correctly. Also, you can't rewind to a steering message. Want to make sure you can rewind to it? Wait for the agent to settle, or stop them, enter your message, and hope you don't throw them off their current train of thought. To see a proper rewind UI, see how Pi does it: Every message is available, forked conversation history is preserved. It has its own issues, but is miles ahead of Claude Code in this regard.