Detailed Analysis
A Reddit user posting to r/Anthropic surfaces a pointed critique of Anthropic's Designer tool, identifying a critical gap in its practical utility: while the tool successfully ingests a GitHub repository's frontend code and facilitates interactive UX improvement sessions, it fails at the final and arguably most essential step — delivering the revised files back to the user. The inability to push changes to GitHub or even download files locally renders the tool's output effectively inaccessible, trapping improved work inside the application with no clear export path.
The frustration articulated in the post is not merely about a missing feature but about a broken product loop. A design tool that can analyze, suggest, and interactively iterate but cannot hand off its output functions more like a consultant who delivers recommendations verbally and then shreds the written report. The user explicitly invokes the concept of a customer journey audit, suggesting that Anthropic's internal teams may not have stress-tested the end-to-end workflow before shipping. The observation that it "feels like a tool from another company" is particularly telling — it implies that Designer and Claude Code, despite sharing the same brand, do not appear to have been designed with each other in mind.
This tension between siloed capability and integrated workflow is one of the defining challenges of the current AI tooling landscape. As AI companies race to ship vertical-specific tools — coding assistants, design assistants, research assistants — the connective tissue between them frequently lags. The user's vision of iterating on frontend UX in Designer while simultaneously developing a backend in Claude Code represents a genuinely compelling developer experience, but it requires deep integration that most AI platforms have not yet achieved. The token cost concern the user raises also hints at a broader efficiency question: high-token workflows are only justifiable if they produce durable, exportable artifacts.
The post's closing question — "Anybody running smooth pipeline?" — received no confirmed affirmative answer, which itself signals a gap between Anthropic's product ambitions and current user reality. For Anthropic to position Claude-based tooling as a coherent development platform rather than a collection of individual experiments, interoperability between Designer and Claude Code will likely need to become a near-term priority. Until file export, GitHub integration, or at minimum a local download path is added to Designer, the tool's practical audience remains limited to users who find value in the ideation and analysis phases alone, without needing to act on the results.
Read original article →