alt Hacker NewsMaybe it's because I don't use it in Codex, but I don't like working with Sol. It CONSTANTLY omits things it shouldn't, and is always dispatching sub-agents to do what I tell it to do, that don't have all the necessary context, and so they go on and do the research that was already done by the top-level agent. It's maddening.
I tried it again today because of the discount, it told me it couldn't run acceptance tests because a .env file did not exist, and when I showed it the damn file it went "ah, it's there now". I think it was the first time I've ever had an agent try to gaslight me.
I'd give it some more time. My first interactions with Sol were not good. It cut a dangerous corner and I had to call it out.
But I continued to work with it and found that it was mostly my own style of interacting that needed to change. In a way it is similar to a new co-worker, they have their own personality and ways of working. Once I figured that out I have been able to get very good work out of Sol.
Sol seems to work better when you are clear, precise, direct and unambiguous. The model seems annoyed if things aren't spelled out. Not micro-managing, it seems to have a high bar for specific intent.
When I get Fable to write out specs for Sol, I tell Fable that Sol is a nit-picking literalist that is exceptional at instruction following. So far this description has lead Fable to generate specs that Sol implements at a high quality.