So basically, "watch jj"
Claude Code Checkpoints
61–70 of 136 posts
Re: Claude Code Checkpoints
#62This is fantastic, but a very spicy business. All Claude needs to do is add one feature and you've got your whole business nuked from orbit.
Kind of like Cursor? Just a couple more features (now)
The main benefit of Cursor is avoiding model lock-in. So a solution made only for Claude code seems to be on a much shakier footing.
Re: Claude Code Checkpoints
#63I don't know what this is but isn't git enough? Incidentally I'm not convinced in my day-to-day for "jujitsu" (jj) but from what I understand about how it works, I've been wanting to give it a try for agent-based coding, based on the way it defaults to saving everything and letting you sort it out after. I do like how Aider commits everything so you can easily roll back, although it ends up with a few too many commit…
I recently started using Aider and had that thought about too many commits. What I realized though was: (1) if I'm going to contribute to a project, I should be working in a local branch and interactively rebasing to clean up my history anyway (and of course carefully reviewing Aider's work first) and (2) if I'm working on my own thing WITHOUT LLM, I tend to prefer to commit every dang little change anyway, I just do…
> I tend to prefer to commit every dang little change anyway, I just don't remember to do it because I'm in the zone and then inevitably wish I had at some point.
That’s what I do too until I developed a practice to break up into thematic commits as I realize I need them. And if I don’t, then I just git reset to the beginning and use git gui to commit lines and chunks that are relevant for a given piece of work. But with experience, I barely do the break down completely - I generally don’t even bother creating commits until I have a starting sense of what the desired commit history should be.
Re: Claude Code Checkpoints
#64Earlier quoted context omitted.
Kind of like Cursor? Just a couple more features (now)
The main benefit of Cursor is avoiding model lock-in. So a solution made only for Claude code seems to be on a much shakier footing.
MCP is widely adopted. This will work with anything that talks it.
Re: Claude Code Checkpoints
#65Earlier quoted context omitted.
It's also very easy to throw away unstaged changes, and to stage exactly what you want. I treat the staging process ("git add") as a code review.
It's also very easy to throw away actual commits, as long as you don't push them (and even then not so difficult if you're in a context where force-pushing is tolerable).
True, but it's harder to reject changes in one file, make a quick fix, etc. I like to keep control over my git repo as it's a very useful tool for supervising the AI.
Re: Claude Code Checkpoints
#66Earlier quoted context omitted.
My experience with AI tooling is that while it's really useful and great - I don't think i've ever seen a LLM complete an epic long feature well full stop. Don't get me wrong, it's definitely improved my workflow and efficiency, but you must be winning at roulette if the model is performing well on anything that can't be googled and implemented witihn a similar amount of time. unless it's claude, where even simple st…
If you go back and forth with chatgpt/gemini on architectural details first, then get chatgpt to produce a hyper detailed spec (like, almost a program claude can execute), you can get claude to run for 2-3 hours at a shot (particularly with a hook to prevent early stopping). Require >85% test coverage, and bake very clear e2e test paths into the spec, and Claude can come surprisingly close to one shotting big things.
I found a boost adding LikeC4 to the spec.
Re: Claude Code Checkpoints
#67Or you could use something like NILFS2 [0]. It would be nice to be able to just turn such a function on and off per folder.
Re: Claude Code Checkpoints
#68Earlier quoted context omitted.
This is a funny comment because it's just made up
While disaster is strong language, Claude Code isn't really a well engineered product, they're just kinda trying shit, they don't have a clear long term vision. The core prompts and agent loop are good though, it's too bad it's not open source so someone could implement them in a client with good UX/engineering (at least without disassembling claude code and being legally questionable).
> not opensource
You can extract prompts with mitmproxy/netcat, and AFAIK there isn't much more to it (bash and todo list are all you need in terms of tools), there's already a lot of simpler tools with better ux:
- sst/opencode and charmbracelet/crush -- related "cc clones" with top tier UX; opencode has near feature parity with cc, crush is more barebones
- block/goose -- a lot of multi-model features and extensions (it's practically a framework), but UI is pretty basic
- antinomyhq/forge -- similar to goose, but last week they merged some PRs with agent-agent communication, yet to see how it works out
- openai/codex, gemini-cli -- both somehow don't even have a way to resume a conversation
- avante.nvim with mcphub.nvim -- neovim plugin that emulates cursor to a degree; has a crazy good hack that makes even older models like gpt4.1 "more agentic" -- it keeps reprompting the model with "STFU and write code" until the model calls a "task_completed" tool; gets diagnostics, formatting and anything else neovim can do "for free"
For the sake of completeness, closed-source:
- amp-cli -- absolutely barebones, zero configuration (they even decide what model you're using for you); one problem -- closed source, no BYOK or subscription, pay per token only
- cursor-cli -- atm unusable, can't even set a global context file
- codebuff -- yet to try it myself, but they have some sort of an overengineered setup with 5+ different models (resoner/coder/file picker (!)/fast apply/...), curious to see how it works in practice (I'm assuming this setup is strictly worse than a single sonnet4/gpt5, but much cheaper)
Claude does have a lot of unique/rare (for now) features -- hooks, sub-agents, background jobs, planning mode, per-prompt reasoning effort controls, executable bash in slash commands.
Only half of them are really useful IMHO, but I wouldn't know that if they didn't have them.
Re: Claude Code Checkpoints
#69This is something I really wish was just built-in to Claude Code. I want it built in because I don't want to have to think about it beforehand. I should be able to jump back in conversation history and have the state of the code jump back with me, so it's restored to the same state it originally was at that point in the conversation. (There does also need to be a way to jump back in the conversation history without r…
Github Copilot in vscode can do that and also has the Claude models available
Re: Claude Code Checkpoints
#70This is something I really wish was just built-in to Claude Code. I want it built in because I don't want to have to think about it beforehand. I should be able to jump back in conversation history and have the state of the code jump back with me, so it's restored to the same state it originally was at that point in the conversation. (There does also need to be a way to jump back in the conversation history without r…
Gemini cli already got this, it's disabled by default. Ref: https://github.com/google-gemini/gemini-cli/blob/main/docs/c...
if only gemini cli could edit files without getting stuck in an infinite loop