# TAB not working for autocomplete on commits

**URL:** <https://forum.cursor.com/t/tab-not-working-for-autocomplete-on-commits/160323>\
**Category:** Bug Reports\
**Tags:** tab, keybindings\
**Created:** [May 11, 2026, 5:57pm UTC](https://forum.cursor.com/t/tab-not-working-for-autocomplete-on-commits/160323 "2026-05-11T17:57:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![fusiondev](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/fusiondev/32/19122_2.png) [@fusiondev](https://forum.cursor.com/u/fusiondev)\
**Post date:** [May 11, 2026, 5:57pm UTC](https://forum.cursor.com/t/tab-not-working-for-autocomplete-on-commits/160323/1 "2026-05-11T17:57:18Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

With the commit message, I used to be able to press tab and it would auto-complete the commit message. Now it tabs to something lower in the interface.

### Steps to Reproduce

Try to do a push to main using commit. And where it has the autocomplete, like AI intelligence basically for a new commit message. Pressing tab doesn’t work for me. It just starts tabbing around the interface, like onto the node, terminal ports, all the other stuff.

### Expected Behavior

When you press tab, it should go to the end of the sentence and also fill in the commit message.

### Operating System

MacOS

### Version Information

Version: 3.3.27  
VSCode Version: 1.105.1  
Commit: 80b138a7a0a948e1a798e9ed7867d76a1ba9a310  
Date: 2026-05-08T02:26:22.498Z (3 days ago)  
Layout: editor  
Build Type: Stable  
Release Track: Default  
Electron: 39.8.1  
Chromium: 142.0.7444.265  
Node.js: 22.22.1  
V8: 14.2.231.22-electron.0  
OS: Darwin arm64 25.4.0

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [May 11, 2026, 6:20pm UTC](https://forum.cursor.com/t/tab-not-working-for-autocomplete-on-commits/160323/5 "2026-05-11T18:20:14Z")

</div>

Hey, there’s a small UX misunderstanding here. In Cursor, commit message generation doesn’t work via an inline suggestion that you accept with Tab. It works via the sparkle button in the Source Control panel next to the message field. Click it and the generated text is inserted into the field directly. We don’t support ghost text that you accept with Tab in the commit input.

Cycling through the UI is standard VS Code behavior when no inline suggestion is active.

Two things to check:

1. If you previously had GitHub Copilot or another extension that provided inline completions in the commit input, Tab-to-accept may have been coming from that. After disabling it, the behavior would change.
2. You might have accidentally enabled Tab Moves Focus mode. Toggle it with `Cmd+Shift+M` or via the Command Palette: `Toggle Tab Key Moves Focus`. If it’s on, Tab navigates instead of editing.

If you want generation, use the sparkle button in the SCM panel. Let me know if you expected something else.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [June 10, 2026, 6:21pm UTC](https://forum.cursor.com/t/tab-not-working-for-autocomplete-on-commits/160323/6 "2026-06-10T18:21:13Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.