3 ms·
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 tea
by coffeeaddict1 9mo ago
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 https://github.com/openai/codex/issues/2788
[1] https://github.com/openai/codex/issues/3585 https://github.com/openai/codex/issues/3585
- wahnfrieden 9mo agoThey 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.
- deleted 9mo ago[deleted]
- toephu2 9mo agoGemini CLI has this
- adam_patarino 9mo agoI’ve never understood checkpoints / forks. When do you use them?
- coffeeaddict1 9mo agoUsually, 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.
- adam_patarino 9mo agoCan’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.
- Sateeshm 9mo agoIt's about not polluting the context. AI doesn't need information about things that didn't work in the new requests' context.
- adam_patarino 9mo agoThat's interesting. I use those moments to show it what not to do. Does it not just repeat the mistakes?