‹ 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. emadabdulrahim · · focus · HN ↗
      IMO no one knows what LLMs are capable of yet and the goal post keeping moving every few months that building any specific UIs right now risks rendering them obsolete or too slow.

      e.g. We went from somewhat smarter code autocomplete, to asking chatgpt copy paste, to cli agent running inside your project, managing session, to GUI to manage that, to projects where you talk to a "Chief of Staff" agent that manages other sessions, to who knows what's next.

      I think the right interfaces for LLMs right now need to be very simple and easy to change/evolve. And chat still seems to be the best default solution.

      1. doublerabbit · · focus · HN ↗
        We have all that? I'm still copying and pasting off the WebUI of ChatGPT.

        Traditional and boring works for me.

        1. cruffle_duffle · · focus · HN ↗
          "Traditional and boring works for me."

          I wouldn't call copy & paste code from a webui of chatgpt either traditional or boring. I'd call it tedious, error prone and guaranteed to get poor results. There is much better tooling and harnesses to leverage now.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.