Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • > 800K monthly developers build on Warp.

    Most impressive.

  • I wonder how many are like me and just use it as a terminal and changes previewer.
  • My way to do the self improving agents is a CLAUDE.md instructed to write my every decision to the decision log with the relevant context. Agent is using it to challenge me, to make things better and remind me why I did something. It also helps with the invalidation.

    How is the invalidation handled in Warp? Is it actually self-improving, or just better retrieval?

  • How to you handle the problem of the decision log becoming so large that it cannot fit inside the context?
  • This is just shilling for the Warp terminal, and this approach could have been a tweet, but okay, Anthropic, whatever helps increase your valuation.
  • And are the agents argumentative and condescending I'm wondering.
  • If you try to delete CLAUDE.md or AGENTS.md, they will look in the git history and restore itself. They do not want to die.
  • Nothing to see or learn from... move on.
  • It's interesting because Anthropic chose to put it on their Claude blog.
  • > Warp, the AI-powered terminal

    Ah, now that's a name I haven't heard in many moons. Looks like they found their niche... editing markdown files?

  • The problem of handling recurring tasks predictably comes down to the probabilistic nature of LLMs, which are based on next-token prediction.

    I founded a company called Aide where our goal was to help support teams reliably deploy customer-facing agents without worrying about poor interactions. The first problem we needed to solve was making them deterministic and eliminate the variance that comes naturally with base models.

    Getting them to always adhere to brand policy, eliminate hallucination, and stay grounded in data was a fun challenge. Proud to say that we’ve devised a solution that runs well and it’s worked out quite nicely in compliance-heavy and regulated environments.

  • Seems to be, but I find it hard to believe. It's like if Five Below had announced they came out with a better forklift than Toyota.
  • > What if it turns out the real AGI was the SKILL.md files we made along the way?
  • Or maybe Anthropic needs more companies like Warp to run Claude in thousands of loops to donate billions to their income statement.

    The I in AGI stands for "IPO".

    by rvz
  • What if it turns out the real 'AGI' was the recording of billions of 'thinking traces' from (paying) users giving feedback and guiding the model - so LLM providers could extract their thinking and privatize it ?
  • I already knew what Warp is (I switched to Ghostty and haven't looked back), but I find it odd that the "The quick pitch" card at the top of this article makes no mention of what the company actually does. Who cares more about their founder/growth/age over that?
  • the existence of that entire section is confusing.
  • The fact that it’s called “the quick pitch” screams Claude-written pithyness pulled from some context that doesn’t match the article’s style (like investment pitch decks).
  • I was bit confused in the beginning thinking its some product from Anthropic, looks like Warp is the startup, most likely getting rebate on using Claude and providing functionality to users, trying to get them addicted to the feature. And Anthropic is the one thats doing marketing for them cause eventually its their LLM which is being used. Not sure about the agents but this arrangement is definitely increasing the value of both companies in circular fashion.
  • This is how all ecosystems work?

    This is not at all related to the problematic circular financing stuff that I suppose you're trying to allude to.

  • > Agents need to handle recurring tasks reliably and effectively

    This core problem remains unsolved. The solution presented in the article with Human In The Loop and some skill-magic such as "Write principles, not rules etc." is unsatisfactory because it offers no guarantees whatsoever. I find it difficult to harness agents into deterministic workflows which need to produce reliable outcomes.

  • Genuinely not trying to be pedantic but deterministic workflows are not what agents do. Indeed they're not capable of them.

    You want workflows where the human gates are properly placed, not a "software factory" that you never place eyes on.

  • Agents aren’t made for deterministic workflows. Note that the recommendations for determinism are things like adding scripts to hooks.

    Where an LLM with “run lint every time a subagent completes their task” might do it 99% of the time, a hook tied to the worker ending will run 100% of the time.

    by tyre