I suddenly understood what Claude Code and Comet are all about, and why agents appear in both the CLI and the browser, becoming the mainstream choice. The location of the agent is very important! Developers like to use Claude Code because their code can be controlled through the CLI; the code is essentially the context for communicating with the large model. With code, I can say less, and the agent's work directly rewrites the files on my computer. However, after messing around today, I found that people in the media industry can't use it because they have nothing on their computers; the core content is all in apps and browsers. But Claude Code is difficult to access the content in browsers and apps, so the core issue isn't whether I use Sonnet or Opus, but rather that this agent shouldn't appear in the command line. This agent should appear in the browser! For example, the Coze workflow that Douyin has been promoting for scraping data from Xiaohongshu can be done directly with Comet. For people in the media industry, Comet is the real Claude Code because the agent for media creators must appear in the browser. Compared to the previous Dia browser, it seems quite foolish; that wasn't an agent, it was an LLM. If you just insert an LLM into the browser, I think it’s almost meaningless.