‹ 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. yieldcrv · · focus · HN ↗
      Before OpenAI dropped ChatGPT, nobody knew chat would be such a hit. Several labs had versions of these things, Google engineers were getting finessed by a rudimentary model just like in the movie Ex Machina that came out 10 years prior which was satirizing Google

      But I don't agree that they aren't product-ized. There are many applications doing calls to LLMs behind the scenes and are hits, leveraging structured data very heavily and not having conversations with users at all. I would say that there is a predictable scope creep from executives to surface a conversational aspect though. We need to bring representation to that so we can point to some other best practice to push back

      1. drivebyhooting · · focus · HN ↗
        Can you give examples of wrapped LLM logic?

        API calls are expensive and slow, so I’ve shied away from integrating them into my personal projects. And of course there’s always the risk of hallucination.

        1. disgruntledphd2 · · focus · HN ↗
          For converting unstructured data into (more) structured data, they're phenomenal.

          Yes, they are expensive, but flexibility has a lot of value.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.