Live data from Hacker News

You only need the frontier model for one single edit

stencil.so

61–70 of 107 posts

Re: You only need the frontier model for one single edit

#61

> We upstreamed it to omp For those not sufficiently cracked... what is omp? Is there a way I can have this command or workflow in Cursor / Claude Code? I tried going to the homepage ( https://stencil.so/ ). It didn't really help.

Oh my Pi - batteries included pi harness

Re: You only need the frontier model for one single edit

#62
post #57
post #35

This is really smart, like the author said, old idea but cleverly applied. In case anyone wants a summary: don’t one shot, don’t use plan mode and hand off the plan to cheap executors, ask the frontier model to explore, create a todo list, and then start when it feels confident; stop it after first code edit, then prefill the context to cheap executor to continue.

How is that different than just having the frontier model write a build plan and store it, then have a cheaper model execute? That’s pretty normal practice. The build plan should be better than the context that generated it since it strips out wrong turns and other noise. I think?

The article actually explains it better than I can but essentially you do not want the agent to get desperate which causes it to burn extra tokens. Planning phase doesn't test assumptions by going straight in the code and testing out parts of the ideas to execute so it has to consider way more in planning than it would if it could go quicker into the coding phase.

Re: You only need the frontier model for one single edit

#63
post #35

This is really smart, like the author said, old idea but cleverly applied. In case anyone wants a summary: don’t one shot, don’t use plan mode and hand off the plan to cheap executors, ask the frontier model to explore, create a todo list, and then start when it feels confident; stop it after first code edit, then prefill the context to cheap executor to continue.

So its basically (a plan + a bunch of file reads + a first edit) injected into the context of a cheap model so the cheap model does not feel like it has to re-read the files and just continues executing and editing?

Re: You only need the frontier model for one single edit

#65
post #57
post #35

This is really smart, like the author said, old idea but cleverly applied. In case anyone wants a summary: don’t one shot, don’t use plan mode and hand off the plan to cheap executors, ask the frontier model to explore, create a todo list, and then start when it feels confident; stop it after first code edit, then prefill the context to cheap executor to continue.

How is that different than just having the frontier model write a build plan and store it, then have a cheaper model execute? That’s pretty normal practice. The build plan should be better than the context that generated it since it strips out wrong turns and other noise. I think?

The article isn't about plan vs no plan but rather that instead of a weak hand-off of "here's a plan describing what I hope works" you can do a much stronger hand-off with "here's an approach that survived first contact with the code".

Re: You only need the frontier model for one single edit

#67
Can someone explain to me the difference between this approach and using planning with a larger model, then just switching to a small model for implementation without clearing the context? I understand that it specifically does the first edit as well either way the larger model. Is there some other difference I am missing here?

Re: You only need the frontier model for one single edit

#68

Can someone explain to me the difference between this approach and using planning with a larger model, then just switching to a small model for implementation without clearing the context? I understand that it specifically does the first edit as well either way the larger model. Is there some other difference I am missing here?

If I understand correctly, switching to a small model makes the small model read the context again.

Re: You only need the frontier model for one single edit

#69
post #62
post #57

Earlier quoted context omitted.

How is that different than just having the frontier model write a build plan and store it, then have a cheaper model execute? That’s pretty normal practice. The build plan should be better than the context that generated it since it strips out wrong turns and other noise. I think?

The article actually explains it better than I can but essentially you do not want the agent to get desperate which causes it to burn extra tokens. Planning phase doesn't test assumptions by going straight in the code and testing out parts of the ideas to execute so it has to consider way more in planning than it would if it could go quicker into the coding phase.

Hmm. When I have Opus or Fable write build plans, then invariably invariably read code extensively, but it’s true they don’t make changes and run tests.

I guess the way to formalize this would be to add a “make minimal change to confirm approach” instruction to the build planning prompt. Probably can even parallelize that so as the build planning prompt iterates subagents get launched to validate, similar to what research modes do.

I’m a little skeptical, but will give it a try.

Re: You only need the frontier model for one single edit

#70

Good stats but how does this work with models like Claude where a lot of the context or relevant information is stored in its "memory", other coding agents can't use it.

Memory is a harness feature, not a model feature.

The author is probably only evaluating their own harness with different models, so Claude-Code-specifics like memory aren't part of their evaluation.

Post reply on HN