I just don’t think they have anything to worry about. I personally think it’s good what they’re doing here, but I guess I’m too cynical to believe they are doing it out of the goodness of their hearts, and I don’t think the real reason is that they’re worried about bad publicity.
I would love any feedback on what you are missing etc
- The Apple icon is a literal apple and not the Apple logo.
- You've got 2 Mac download buttons that do the same thing right at the top, surely one of those is a mistake.
- "Watch it in action" is positioned poorly and fails to be a header for the video. Too close to the button above it.
- "Automatic version control" is not what a checkpoint is? "Version control" means git to almost everyone.
- Privacy link is a fake placeholder.
- "See It In Action" looks like you meant to add images and just forgot?
- You named this like 5 things. The website title is "Checkpoints for Claude Code", the domain is "Claude Checkpoints", the UI website title is just "Checkpoints" as if its a standalone brand, the contact email link uses "checkpoints-app.com", and finally you call it "Claude Diff" in the App Store description. Oh and the HN submission is a 6th one, "Claude Code Checkpoints".
Cool project though, sorry to be so critical.
> * Accessing your accounts or files
> * Sharing your private information
> * Making purchases on your behalf
> * Taking actions you never intended
This should really be at the top of the page and not one full screen below the "Try" button.
I would also imagine that it warns you again when you run it for the first time.
I don't disagree with you given how uniquely important these security concerns are, but they seem to be doing at least an okay job at warning people, hard to say without knowing how their in-app warnings look.
What about the bio is satirical? I'm pretty sure that's sincere too.
Either way consider just posting the text or using a platform other than X, because without logging in I can't read it (without using the xcancel.com version someone else posted).
> I focus on the high-level code, and let the model focus on the lower level code.
Tbh the reason I don't use LLM assistants is because they suck at the "low level". They are okay at mid level and better at high level. I find it's actual coding very mediocre and fraught with errors.I've yet to see any model understand nuance or detail.
This is especially apparent in image models. Sure, it can do hands but they still don't get 3D space nor temporal movements. It's great for scrolling through Twitter but the longer you look the more surreal they get. This even includes the new ByteDance model also on the front page. But with coding models they ignore context of the codebase and the results feel more like patchwork. They feel like what you'd be annoyed at with a junior dev for writing because not only do you have to go through 10 PRs to make it pass the test cases but the lack of context just builds a lot of tech debt. How they'll build unit tests that technically work but don't capture the actual issues and usually can be highly condensed while having greater coverage. It feels very gluey, like copy pasting from stack overflow when hyper focused on the immediate outcome instead of understanding the goal. It is too "solution" oriented, not understanding the underlying heuristics and is more frustrating than dealing with the human equivalent who says something "works" as evidenced by the output. This is like trying to say a math proof is correct by looking at just the last line.
Ironically, I think in part this is why chat interface sucks too. A lot of our job is to do a lot of inference in figuring out what our managers are even asking us to make. And you can't even know the answer until you're part way in.
Have you tried Cursor? It has a great feature that grabs context from the codebase, I use it all the time.