Hacker News Reader

After hitting the session limit on my company's plan so many times with Claude when I was using it, I mostly keep Codex on "high" rather than "xhigh" as a way to leave the tokens for my more ambitious coworkers. It's possible that having it higher might end up with better output, but so far at least I've yet to see a way to get any model to do 100% of what I need up front without any need for me to make changes that end up being more tedious to do via interaction than by hand, and it doesn't feel worth spending a bunch more tokens trying to figure out how to better communicate to it up front how the dominoes get set up so they fall in place properly the next time.

To be fair, I actually do run xhigh as my default. However, for the first time in my experience of trying and using LLMs, with Sol.. sometimes I feel confident enough to set the effort level to "Low". I just had Sol prototype some AWS stuff on low earlier. Great result, did exactly what I wanted.

How do you handle context limits? With more thinking tokens you fill it up earlier. Compaction degrades performance too. What's your strategy?

Initially I was planning heavily around context limits, but I've learned to just ignore it completely. Compaction is seamless for me. If details are lost in compaction, the model just re-reads what's needed. My conclusion is that at least for Sol, the summaries (which I've never seen) must be amazing. Every now and then a detail gets lost and I have to repeat it. I don't think there is performance degration, because the model is smart enough to re-read relevant files as needed.