Migrating a production AI agent to GPT-5.6: 2.2x faster, 27% cheaper
31–40 of 144 posts
Re: Migrating a production AI agent to GPT-5.6: 2.2x faster, 27% cheaper
#32> we’ve made GPT 5.6 Sol the default model powering every Ploy workspace I would consider Luna for parts of the workload that touch actual tools. It is surprisingly capable and it runs fast. Sol is great at talking to the human and orchestration of agent calls, but it's just too expensive to use everywhere. You can get 5 Luna runs for the cost of 1 Sol run. Statistically speaking, going from one to five samples is a…
The problem I always run into with subagents is that they are isolated. This is a double-edged sword, as it keeps context down and lets them "focus", but it often means they must do their own research to continue to do work given to them, which eats uncached tokens. So depending on how heavily agents are used on what tasks, it's entirely possible that you get worse work for more cost.
This is a feature if your goal is to obtain many samples. Independence is critical. This makes it easier to accurately model the uncertainty of a decision.
Re: Migrating a production AI agent to GPT-5.6: 2.2x faster, 27% cheaper
#33Earlier quoted context omitted.
Can we get over the detective work about if the text was written by LLM or not in 2026 already ? This is a lost cause, and we could instead focus on substance over syntax.
Not OP but my frustrations come from it being impossible to ignore and outright distracting. I've found the same thing showing with Claude-coded/designed front ends that overuse the same semi-monospaced fonts, Blue/Yellow/Red palette and rounded corner borders. It isn't that it is bad , but it often isn't fit for purpose. You're right it wont change anything, but authors shouldn't be surprised when people who care ab…
Re: Migrating a production AI agent to GPT-5.6: 2.2x faster, 27% cheaper
#34> we’ve made GPT 5.6 Sol the default model powering every Ploy workspace I would consider Luna for parts of the workload that touch actual tools. It is surprisingly capable and it runs fast. Sol is great at talking to the human and orchestration of agent calls, but it's just too expensive to use everywhere. You can get 5 Luna runs for the cost of 1 Sol run. Statistically speaking, going from one to five samples is a…
The problem I always run into with subagents is that they are isolated. This is a double-edged sword, as it keeps context down and lets them "focus", but it often means they must do their own research to continue to do work given to them, which eats uncached tokens. So depending on how heavily agents are used on what tasks, it's entirely possible that you get worse work for more cost.
Re: Migrating a production AI agent to GPT-5.6: 2.2x faster, 27% cheaper
#35Earlier quoted context omitted.
Can we get over the detective work about if the text was written by LLM or not in 2026 already ? This is a lost cause, and we could instead focus on substance over syntax.
I have a counter proposition: don't fall for this constant suggestion that LLMs are an unavoidable future would you leave the techbros alone now pretty please, relentlessly keep reminding that we still don't think it's acceptable so people don't start to think this is okay since nobody complains anymore. I appreciate these comments, they save me time for procrastinating elsewhere.
And let’s be real: I had a post this year that was #1 on HN for a while, and an LLM “wrote” the whole thing, but it was very much my writing style and NO ONE called out the post as LLM slop. If you use an LLM correctly for writing, it’s not detectable. It seems that most folks don’t go through that effort.
Re: Migrating a production AI agent to GPT-5.6: 2.2x faster, 27% cheaper
#36> Numbers like that buy a model a real migration effort. Such a silly choice of words. I wish the human directing the LLM writing the article put some effort into rewriting the worst examples of LLM style. > But it did extremely well, and the promise was immediate and specific: builds finishing in less than half the wall-clock time, at 27% lower cost, scoring at or above our incumbent on completed work. The way the L…
Can we get over the detective work about if the text was written by LLM or not in 2026 already ? This is a lost cause, and we could instead focus on substance over syntax.
Re: Migrating a production AI agent to GPT-5.6: 2.2x faster, 27% cheaper
#37Earlier quoted context omitted.
Not OP but my frustrations come from it being impossible to ignore and outright distracting. I've found the same thing showing with Claude-coded/designed front ends that overuse the same semi-monospaced fonts, Blue/Yellow/Red palette and rounded corner borders. It isn't that it is bad , but it often isn't fit for purpose. You're right it wont change anything, but authors shouldn't be surprised when people who care ab…
critique of writing style isn't made better by claiming it was authored by an LLM
I also think that people should focus on substance and not if AI was used, but AI writes like shit and I find myself retching a bit when I have to read long AI-written documents. Do they say something useful? Maybe, but when my eyes are glazing over because it's just so exhausting trying to parse what's written, I can't tell.
I certainly think less of people when they have such poor taste that they think writing like that is acceptable.
Re: Migrating a production AI agent to GPT-5.6: 2.2x faster, 27% cheaper
#38> Numbers like that buy a model a real migration effort. Such a silly choice of words. I wish the human directing the LLM writing the article put some effort into rewriting the worst examples of LLM style. > But it did extremely well, and the promise was immediate and specific: builds finishing in less than half the wall-clock time, at 27% lower cost, scoring at or above our incumbent on completed work. The way the L…
Can we get over the detective work about if the text was written by LLM or not in 2026 already ? This is a lost cause, and we could instead focus on substance over syntax.
Re: Migrating a production AI agent to GPT-5.6: 2.2x faster, 27% cheaper
#39> Numbers like that buy a model a real migration effort. Such a silly choice of words. I wish the human directing the LLM writing the article put some effort into rewriting the worst examples of LLM style. > But it did extremely well, and the promise was immediate and specific: builds finishing in less than half the wall-clock time, at 27% lower cost, scoring at or above our incumbent on completed work. The way the L…
> The way the LLMs write (Claude perhaps?) With short phrases separated by colons, commas or full stops, is so poor and frustrating. Yup llmish (from now on it's called "llmish") sucks. But I'd say: at this point it's probably trivial to write a browser extension that detects llmish and that rewrites the worst sentences: from llmish to something less irritating to read. Heck, I could spent tokens on that: an extensio…
If wokeness actually did capture a whole generation then why even bother complaining?
Re: Migrating a production AI agent to GPT-5.6: 2.2x faster, 27% cheaper
#40> Numbers like that buy a model a real migration effort. Such a silly choice of words. I wish the human directing the LLM writing the article put some effort into rewriting the worst examples of LLM style. > But it did extremely well, and the promise was immediate and specific: builds finishing in less than half the wall-clock time, at 27% lower cost, scoring at or above our incumbent on completed work. The way the L…
Can we get over the detective work about if the text was written by LLM or not in 2026 already ? This is a lost cause, and we could instead focus on substance over syntax.