‹ BackHN Continuity

Thread

An empirical study of harness design for coding agents

225 points · 59 comments · wek

  1. rahulmax · · focus · HN ↗
    Quite inline with what I had found with my Claude code sessions over the last year. I wrote about this a few months ago.

    <a href="https:&#x2F;&#x2F;rahulmax.com&#x2F;notes&#x2F;how-i-keep-the-ai-bill-down&#x2F;" rel="nofollow">https:&#x2F;&#x2F;rahulmax.com&#x2F;notes&#x2F;how-i-keep-the-ai-bill-down&#x2F;

    In their case, context management pays off more the tighter your window. Their gap between managing and not managing is 35.7 points of success rate at 32k and 2.7 points at 128k. My version of that was a rule I stick to, as much as I can. I checkpoint a session at about 25-30% of the window, write the state out to a PROGRESS.md and a JSON file of the requirements, and start fresh. This restart costs me 30 seconds, since a bloated session doesn&#x27;t get any cheaper the longer you stay in it.

    Also worth knowing that the models are Nemotron-3 and Mistral-Medium, not the frontier models most people here are paying for.

    1. bunderbunder · · focus · HN ↗
      And what you describe doing is also very in line with Cursor&#x27;s published recommendations.

      Though of course every single element of their application&#x27;s actual UX is pushing hard in the opposite direction. The cynical part of me can&#x27;t help but notice that there&#x27;s a bit of a conundrum here: using coding agents more effectively seems to involve working pretty hard at giving the agent vendor less money.

      1. slfnflctd · · focus · HN ↗
        This could potentially be an important part of price discovery, though. The market is constantly seeking that balance point between &#x27;chasing whales&#x27; and &#x27;making it up on volume&#x27;.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.