3 ms·
I always find it wild that none of these tools use VCS - completed logical unit of work, make a commit, drop entire context related to that commit, while refere
by 0x457 1y ago
I always find it wild that none of these tools use VCS - completed logical unit of work, make a commit, drop entire context related to that commit, while referencing said commit, continue onto the next stage, rinse and repeat.
Claud always misunderstands how API exported by my service works and every compaction it forgets all over and commits "oh api has changed since last time I've used, let me use different query parameters", my brother Christ nothing has changed, and you are the one who made this API.
- bastawhiz 1y agoYou can use cursor rules to tell cursor to update the project cursor rules with details about the API.
- bdangubic 1y agothat would mean someone actually tried to learn how to use it :)
- 0x457 1y agoYes, I can, and I do, I'm pointing out that compressing an entire conversation history into a single message is so lossy that I might as well start a new session. Yes, I can also tell any agent to commit more often, but that's again not what I'm saying. I'm saying version control can be integrated way deeper into agent workflow.
- bahmboo 1y agoRoo Code does this
- bdangubic 1y agoI do exactly this - except I want control to define logical units of work
- 0x457 1y agoThat's how Kiro works and how the agent that I'm working on works. Kiro creates tasks from spec document, and you can revise tasks either by prompting or editing tasks.md file. My thing works a bit differently, but essentially the same.
- jondwillis 1y agoIdk I had cursor/claude untangle and commit to two separate logical branches yesterday from a bunch of random working copy changes that I had made. You can prompt it to use git commands and it works well enough in my experience.
- 0x457 1y agoYes, you can prompt, I find it confusing why that + worktrees (i.e. agent working on its own working copy of the repo) is the standard/