‹ BackHN Continuity

Thread

Claude Cowork and chat are now one Claude

234 points · 225 comments · vertigoruntime

  1. petcat · · focus · HN ↗
    Nobody really knows how to product-ize any of these LLM interfaces beyond just chat.

    They don't want a traditional UI with buttons and forms and labels because they want the interface to be "chat". The problem is that "chat" is tedious. And the turn-based, linear nature of the chat interaction model makes it even more tedious and unproductive.

    1. clumsysmurf · · focus · HN ↗
      One thing I would like is a tree-like chat structure like reddit / HN. Many times I abandon the direction things have gone but would like to resume at some ancestor or sibling response.
      1. BikiniPrince · · focus · HN ↗
        I solved this with task management and got work trees.

        The downside of course is branching in got, but I usually don’t go of course more then a handful of tasks.

        I had to engineer my own ticket management to keep opus on target. It’s been great for managing work, history, audit trails and commits are tagged with the task id.

        I implemented subtasks to deal with the way Claude likes to stage its own objectives.

        Then I made enforcement logic in the task manager so tasks can’t be closed out until reviewers have consensus on the same sha.

        The adhd that is Anthropic demanded I build it and now I’m knocking out issues faster than Batman.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.