[dead]
Claude Code Checkpoints
51–60 of 136 posts
Re: Claude Code Checkpoints
#52Interesting to watch the explosion of projects, even whole startups, which are just a feature addition to Claude Code. Shows how beloved it has become.
Re: Claude Code Checkpoints
#53Hi, the developer here. Its a very early version so there could be a lot of bugs, but I like to use it myself (already found several bugs and updated version soon on its way). Switching from Cursor to Claude Code this was the biggest loss. Have tried to improve on the Cursor functionality, with features I missed. I would love any feedback on what you are missing etc
Are you aware of trademark law?
Yes, tried to make it clear that this is Checkpoints for Claude Code. An addition to Claude Code.
Re: Claude Code Checkpoints
#54Earlier quoted context omitted.
Eesh, a disaster? I use it daily to do some pretty impressive things. Wouldn’t call it a disaster.
Some of the user interaction borders on "disaster" IMO. One puts up with it because it's not a show-stopper for the core value proposition of the software (an LLM agent completing tasks for you), and the core value proposition of the software is really valuable. The noticeable issues are (1) unpredictable scrolling of the terminal window and (2) a super-buggy text box for inputting the prompt. In particular if I mash…
I've built terminal applications and when not using a dedicated alternate buffer, things like multiline text input and navigation are so easy to screw up. Not to mention when you have to do all the tricks to properly detect key strokes, pastes, etc. It's a mess of printing special codes and carriage returns.
I'm guessing they're using abstraction of some sort, but imo they've done a lot of great features and definitely usable.
That being said- they could just build / use something more like a jupyter notebook and have a wildly more stable and rich experience. Or a classic tui app, but pros and cons.
Re: Claude Code Checkpoints
#55Earlier quoted context omitted.
Eesh, a disaster? I use it daily to do some pretty impressive things. Wouldn’t call it a disaster.
Some of the user interaction borders on "disaster" IMO. One puts up with it because it's not a show-stopper for the core value proposition of the software (an LLM agent completing tasks for you), and the core value proposition of the software is really valuable. The noticeable issues are (1) unpredictable scrolling of the terminal window and (2) a super-buggy text box for inputting the prompt. In particular if I mash…
I really love Claude Code but it's wild to me if
others aren't seeing this.
Is Ctrl+R usable at all? I've given up on it, the whole screen just starts scrolling madly most of the time. Not that I have to press Ctrl+R to get that bug to happen, it's just the most reliable way to do so.
And I've had the input box stuck not accepting input or not allowing me to delete past a certain point a hundred times. By now I know how to get it unstuck (although I couldn't tell you - my fingers figured it out but my brain doesn't know).
Re: Claude Code Checkpoints
#56Earlier quoted context omitted.
Some of the user interaction borders on "disaster" IMO. One puts up with it because it's not a show-stopper for the core value proposition of the software (an LLM agent completing tasks for you), and the core value proposition of the software is really valuable. The noticeable issues are (1) unpredictable scrolling of the terminal window and (2) a super-buggy text box for inputting the prompt. In particular if I mash…
I've built terminal applications and when not using a dedicated alternate buffer, things like multiline text input and navigation are so easy to screw up. Not to mention when you have to do all the tricks to properly detect key strokes, pastes, etc. It's a mess of printing special codes and carriage returns. I'm guessing they're using abstraction of some sort, but imo they've done a lot of great features and definite…
> That being said- they could just build / use something more like a jupyter notebook and have a wildly more stable and rich experience.
Right, part of the reason it stands out is that we're conditioned to much more functional text input in claude.ai (or competing web apps like ChatGPT).
I assume part of the motivation for the terminal app concept is that all the tool calls run in a deterministic environment (whatever was the environment of the shell where you launched "claude"). A Jupyter-type approach would really muddle up that whole picture (at least from a user perspective).
Re: Claude Code Checkpoints
#57This 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.
Re: Claude Code Checkpoints
#58Under the hood, is this simply checkpointing the files in the claude target folder or are you also checkpointing the claude context? One of my biggest pain points is after a few compactions/edits to claude.md and all of a sudden Claude has made a few mistakes and all the context window cruft of fixes it attempted and reverted actually seem to confuse it further and it would be nice to reset to a known happy place code & contextually and retry from there.
Re: Claude Code Checkpoints
#59This 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)
Re: Claude Code Checkpoints
#60Under the hood, is this simply checkpointing the files in the claude target folder or are you also checkpointing the claude context? One of my biggest pain points is after a few compactions/edits to claude.md and all of a sudden Claude has made a few mistakes and all the context window cruft of fixes it attempted and reverted actually seem to confuse it further and it would be nice to reset to a known happy place cod…
Now it’s the files. Have been prototyping about keeping the context also, for an upcoming version.