Tab support for Cursor in git-ai

[franklhs]

For Cursor, we only run git-ai checkpoint on beforeSubmitPrompt and afterFileEdit, which are agent edit hooks.

Tab edits have specific hooks beforeTabFileRead and afterTabFileEdit. Is there a reason why these are not included in agent_presets.rs here?

[svarlamov]

Great question. The hooks for tabs just came out a few days ago and they're missing some of the data that we need for checkpoints still, so we haven't migrated to them yet. We do have tab support behind a feature flag already in both our Cursor and VS Code Github Copilot: https://github.com/acunniffe/git-ai/blob/main/agent-support/vscode/README.md#ai-tab-tracking-experimental

Would love to meet if you're open to it https://calendly.com/acunniffe/meeting-with-git-ai-authors We're always looking to make git-ai better!

[svarlamov]

Hi @franklhs just wanted to check in if you had a chance to try the Cursor tab support via the extension?

[franklhs]

I have not. My preferred set up is to have these instrumented purely via git instead of extensions. Out of curiosity, what metadata are missing from the new Tab hooks that is needed?

…

On Mon, Dec 8, 2025 at 7:27 AM Sasha Varlamov ***@***.***> wrote: *svarlamov* left a comment (git-ai-project/git-ai#265) <#265 (comment)> Hi @franklhs <https://github.com/franklhs> just wanted to check in if you had a chance to try the Cursor tab support via the extension? — Reply to this email directly, view it on GitHub <#265 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BH3G2GWQNXMHZBPOY5CCVBL4AWKHVAVCNFSM6AAAAACOAAIJOCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMRXGQ4DMMJTGE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[svarlamov]

@franklhs Thanks -- totally understand! We're currently missing the state of the file is being edited. The new Cursor hook is notifying us that the event happened and the content of the change, but since the human may have unsaved edits in the file AND the file isn't saved after the hook runs either, there's no way for Git AI to accurately attribute the change. The extension gets around this by passing the full content of the file to the checkpoint command.

We're currently working with the Cursor team to figure out the best path forward for this. I'll keep you updated

[svarlamov]

Whooops -- I should've checked the docs before firing off my last note. I think it's already been added. Will check it out today and ship this in the next release if it's sufficient

[svarlamov]

We'll have it in the upcoming release: #278

I'll drop a note here when it's out. Excited to have your feedback on it

[svarlamov]

Hey @franklhs, sorry for the whiplash on this... I discovered a bug with the Cursor hooks and am speaking with their team about it now. The native hooks didn't make it into the latest release, but the PR is ready to go once the issues are resolved. Thanks for your patience