stbtrax 3 days ago

I assume so to make sure that they're rendering at 60FPS

  • conception 3 days ago

    You joke but having CC open in the terminal hits 10% on my gpu to render the spinning thinking animation for some reason. Switch out of the terminal tab and gpu drops back to zero.

  • reissbaker 3 days ago

    Surely you mean 6fps

    • easygenes 3 days ago
      • selcuka 2 days ago

        For those who don't want to visit X:

            Most people's mental model of Claude Code is that "it's just a TUI" but it should really be closer to "a small game engine".
            
            For each frame our pipeline constructs a scene graph with React then
            -> layouts elements
            -> rasterizes them to a 2d screen
            -> diffs that against the previous screen
            -> finally uses the diff to generate ANSI sequences to draw
            
            We have a ~16ms frame budget so we have roughly ~5ms to go from the React scene graph to ANSI written.
      • stavros 2 days ago

        What? Technology has stopped making sense to me. Drawing a UI with React and rasterizing it to ANSI? Are we competing to see what the least appropriate use of React is? Are they really using React to draw a few boxes of text on screen?

        I'm just flabbergasted.

      • Ey7NFZ3P0nzAe 2 days ago

        And that's why it's taking so much CPU and is a pain to use with tmux.

trq_ 2 days ago

Yes, we do but harnesses are hard to eval, people use them across a huge variety of tasks and sometimes different behaviors tradeoff against each other. We have added some evals to catch this one in particular.

  • amelius 2 days ago

    Can't you keep the model the same, until the user chooses to use a different model?

    • rovr138 2 days ago

      He said it was the harness, not the model though.

bushbaba 2 days ago

I’d wager probably not. It’s not like reliability is what will get them marketshare. And the fast pace of industry makes such foundational tech hard to fund