I use Claude because the model quality is genuinely hard to beat. For agentic coding, Opus still feels like the model I trust most when the task is complex and I need the agent to keep the whole codebase in its head. The frustrating part is not the model. It is the workflow around Claude Code. If I start a local coding session on my Mac, I want to be able to control it from my phone or iPad the same way I would control a real remote worker/session: resume it, inspect progress, redirect it, recover from errors, and keep going without the session feeling disconnected. Right now Claude’s product feels split across too many ideas: Chat, Code, Cowork, Dispatch. I get the intent, but for technical users it creates more friction than clarity. Cowork especially feels like a halfway concept. Dispatch is useful in some cases, but it feels old-fashioned if the goal is fully controllable live local sessions. Other coding-agent products are moving quickly toward direct remote control, and that is the UX Claude Code should own. Claude already has the model strength. What it needs is the product loop around local work: start a local Claude Code session from mobile reconnect reliably after failures or limits see exactly what the agent is doing steer it without losing state keep the mental model simple: one live working session, controlled from anywhere That would fit Claude Code much better than making users think about which surface — Chat, Code, Cowork, Dispatch — they are supposed to use. Claude Opus feels like the strongest coding partner. I just want the app experience to feel as strong as the model. submitted by /u/Many_Region8176
Originally posted by u/Many_Region8176 on r/ClaudeCode
You must log in or # to comment.