We recently found that certain context sources, like @commit and @git, we’re not working correctly or as you might expect. Additionally, with the improvements to the Agent interacting with the terminal in recent Cursor and model releases, the Agent is now very effective and queries git history within the terminal on its own!
Asking the agent a specific task, such as Analyze my staged Git changes and confirm they don’t break anything elswerhere in my codebaseIt is often the best way to get the Agent to analyse your Git history, but if you find yourself often wanting to do the exact same workflow, we’ve introduced custom commands so that you can create your own shorthands for these repetitive actions.
We imagine this to be much more powerful, as they can be entirely custom to each user!
Is the intention still to be able to reference historical commits via @git? Being able to include this as context is more streamlined and consumes fewer tokens than requesting the agent to perform terminal actions
Oh no, this is a bummer!
I loved to be able to select a past commit (not the latest one! one from a week ago or so) as Context and tell the Cursor agent: “Look at the change we made in this commit to xyService.ts, xyRepository.ts and xyService.test.ts. Now apply the same change pattern to abService“.
I’m not sure what you found to not work correctly; adding a past commit as context and asking cursor “summarize what we did in this commit“, then keep working in this context worked perfectly.
In fact one reason for me to favor Cursor over Kiro or Amazon Q Developer was this feature. Please bring it back
