Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

What I really want from Codex is checkpoints ala Copilot. There are a couple of issues [0][1] opened about on GitHub, but it doesn't seem a priority for the team.

[0] https://github.com/openai/codex/issues/2788

[1] https://github.com/openai/codex/issues/3585





They routinely mention in GitHub that they heavily prioritize based on "upvotes" (emoji reacts) in GitHub issues, and they close issues that don't receive many. So if you want this, please "upvote" those issues.

Gemini CLI has this

I’ve never understood checkpoints / forks. When do you use them?

Usually, I tell the agent to try out an idea and if I don't like the implementation or approach I want to undo the code changes. Then I start again, feeding it more information so it can execute a different idea or the same one with a better plan. This also helps the context window small.

Can’t you use git for that? I do that often and just revert changes. It does require me to commit often but that’s probably good anyways.

It's about not polluting the context. AI doesn't need information about things that didn't work in the new requests' context.

That's interesting. I use those moments to show it what not to do. Does it not just repeat the mistakes?



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: