Basics
Cursor Tab: How Autocomplete Predicts Your Next Edit
Cursor Tab is Cursor's AI-powered autocomplete. It suggests code as you type, based on your recent edits, the surrounding code and linter errors. Suggestions appear as grayed-out text ahead of your cursor. Press Tab to accept, Esc to reject, and Tab again to jump to the next predicted editing location.

On this page
What is Cursor Tab and what does it read?
Tab is Cursor's AI-powered autocomplete, and it reads more than the line you are typing. Cursor's help page names three signals behind each suggestion:
- Your recent edits
- What you just changed, so the next suggestion follows the direction of the work.
- Surrounding code
- The code around your cursor in the current file.
- Linter errors
- Existing errors in the file, which Tab can suggest fixing.
Linter errors change what Tab can do. An autocomplete that reads only what you typed can finish the line you are on. Because Tab also reads the errors already in the file, it can propose a fix for something you broke two minutes ago.
Recent edits steer Tab, and you notice that most at the start of a session. In a file you haven't touched today, the first suggestion has little to work with beyond the code around your cursor. Make two or three edits by hand in the direction you're heading, and the suggestions narrow to that direction. Cursor's troubleshooting page gives the same advice for a new or empty file.
This is also why Tab can seem inconsistent in your first hour with it: you are trying it when it has the least to go on. Suggestions that never appear at all are a separate problem, and the troubleshooting guide lists the four usual causes.
Fix the context, not the model
0:42 · narratedRead this demo as text
- Tab wants to rewrite the return into a sort — and that drops the filtering this function exists for. Confident. Plausible. Wrong. Reject it. A miss you ignore costs nothing.
- Another miss flips the empty-query contract. One wrong ghost is noise. Two in a row? That's a signal about the spot — nothing near the cursor states your intent.
- One comment naming the goal, and the next ghost is the guard you came to write. Tab to accept. Same file, same model — the only thing that changed was the context you gave it.
Practice next: Practice this yourself in the hands-on module.
Simulated Cursor 3.12 (macOS, light) — beta educational reconstruction, not the real product.
Check yourself · one question
A Tab suggestion looks plausible. Which warning sign do you check first?
From the Lesson When to use Tab — about 1 minute, free to read. Or try it live in the simulator →
Rather do it than read about it? Run 11 interactive Cursor walkthroughs in a simulated editor. Free, no account needed.
How do I accept or reject a Tab suggestion?
Three keys cover the whole interaction: one accepts a suggestion, one rejects it, and one takes only part of it. Typing over a suggestion also rejects it.
- Action
- Accept the full suggestion
- Key
Tab
- Action
- Reject
- Key
Esc, or keep typing
- Action
- Accept word-by-word (Mac)
- Key
Cmd+Right Arrow
- Action
- Accept word-by-word (Windows/Linux)
- Key
Ctrl+Right Arrow
| Action | Key |
|---|---|
| Accept the full suggestion | Tab |
| Reject | Esc, or keep typing |
| Accept word-by-word (Mac) | Cmd + Right Arrow |
| Accept word-by-word (Windows/Linux) | Ctrl + Right Arrow |
Suggestions render as grayed-out text ahead of your cursor.
Accept what matches, drop what drifts
0:31 · narratedRead this demo as text
- Okay, watch Tab. It predicts the rename you already started. Hit Tab for the next two hits. It chains the edit points so a mechanical rename never pulls your hands off the keys.
- Next ghost wants the CSS class too. That drifts past your intent. Reject it. Then check Source Control: two changes, both inside the rename you started. Accept what matches. Drop what drifts.
Practice next: Practice this yourself in the hands-on module.
Simulated Cursor 3.12 (macOS, light) — beta educational reconstruction, not the real product.
Learn word-by-word acceptance early. A suggestion can start with exactly the right shape and drift in its second half. Accept all of it and you own a line that looks like your own code, which is the kind of line a reviewer skims instead of checking. Take it word by word with Cmd + Right Arrow instead, and start typing as soon as it stops matching what you meant.
Of the two ways to reject, typing over the suggestion is cheaper, since it is what you were about to do anyway. Esc is worth the keystroke when a suggestion is long enough to get in your way while you think.
You can remap the accept key by searching Keyboard Shortcuts for Accept Cursor Tab Suggestions, but we would make that change last. The usual reason to remap it is indentation muscle memory. Tab is the accept key in Cursor's own shortcut reference, so a remap becomes a local convention that every doc, and every colleague who pairs with you, gets wrong. Remap it if the conflict keeps costing you edits. If it only bites in two file types, turn Tab off for those types instead, as the last section shows.
Can Tab edit multiple lines at once?
Yes. A single Tab suggestion can do more than finish the line under your cursor. Cursor documents three things one suggestion can do:
- Modify multiple lines at once.
- Add missing import statements that your new code needs.
- Suggest coordinated edits across related code.
The import case is the everyday one. Type a call to something you haven't imported yet, and the import arrives with the suggestion.
Multi-line suggestions change how you review. You judge a single-line completion from the line you are already reading. When a suggestion also edits code above your cursor, part of what you accept sits outside where you were looking, so read the whole diff before you accept it, especially in code you didn't write.
Tab catches the rest of the rename
0:26 · narratedRead this demo as text
- You already renamed the parameter on the signature. Look — Tab answers with two gray lines at once. Both leftover references want to become items.
- Tab accepts the multiline rename. Read every line first — a multiline suggestion is still a suggestion, not a free pass to skip review.
Practice next: Practice this yourself in the hands-on module.
Simulated Cursor 3.12 (macOS, light) — beta educational reconstruction, not the real product.
What are jump-in-file and cross-file suggestions?
Tab also predicts where you will edit next. Once you have accepted a suggestion, the Tab key changes meaning: press it again and Cursor moves you to the next place to edit. The two kinds of prediction differ in how far the jump reaches.
- Jump-in-file
- Accept a suggestion, press
Tabagain, and Tab predicts your next editing location in the file and jumps there. It saves you from scrolling or navigating by hand. - Cross-file
- When a change in one file needs an update in another, Tab predicts that edit too. A portal window appears at the bottom of the editor when a jump to another file is available.
That change in meaning is easy to miss, and it catches you the same way each time. You accept a suggestion, press Tab again out of habit, and your cursor is now somewhere else in the file. Nothing is broken, but you have been moved, so check where you landed before your next keystroke.
The portal window at the bottom of the editor tells you Tab has found work in another file. It is easy to miss while you are focused on the line in front of you, and if you miss it, the change you think is finished is finished only in the file you were looking at.
The cost tends to arrive later, as a failing test or a reviewer asking why one call site changed and its neighbor did not. When a rename lands only halfway, search the old name across the repo before you commit. Run that search after any rename an editor helped with.
Does Cursor Tab follow my rules?
No. Cursor's rules documentation answers this directly: rules do not impact Cursor TabCursor's original autocomplete: multi-line, edit-aware suggestions you accept with the Tab key. Press Enter for the full definition. or other AI features. Rules apply to Agent and its chat, and Tab is outside their scope.
So you steer Tab differently from the agent. No rule file reaches it. Tab reads the code around your cursor and what you just did to it, so a convention reaches its suggestions by being present in the file, not by being written down somewhere.
It is tempting to write the convention into a rule anyway, so that at least the agent follows it. That helps the agent, but Tab never sees it. If you want Tab to follow a pattern, put one correct instance of it in the file and start typing the second. Keep rule files for Agent, which reads them.
If you decided your rule file was broken after watching Tab ignore it, the rules fix page covers where else that test goes wrong.
Can I restrict or audit what Tab writes?
Two hooks cover Tab specifically. beforeTabFileRead runs before Tab reads a file and returns allow or deny, which is where redaction or access control goes. afterTabFileEdit runs after Tab edits a file and receives the edit range plus the line before and after, which is enough to drive a formatter or an audit log. Both fire only for Tab, never for Agent.
On a team of five, we would not wire either one. Each hook has a setup cost, and each is one more thing that can break on somebody's machine. The answer changes in an organization where a secret sitting in a file counts as a reportable incident. There, beforeTabFileRead is worth the setup, because it runs before Tab sees the contents and can deny the read.
Scope any written policy to what these hooks cover. They fire only for Tab, and Tab completions are an IDE feature, so neither hook runs in cloud agents. A policy line such as 'every file Cursor reads passes through our redaction script' is false if the script is wired only to beforeTabFileRead, because Agent reads never reach it.
How do I turn Tab off or change its shortcut?
Click the Tab status indicator in the bottom-right corner of Cursor. It gives you three ways to turn Tab off, from a timed pause to a permanent exclusion for particular file types. The shortcut is changed elsewhere: search Keyboard Shortcuts for Accept Cursor Tab Suggestions, as described above.
- Snooze
- Turn Tab off temporarily, for a duration you choose.
- Disable globally
- Turn Tab off for all files.
- Disable for specific extensions
- Turn Tab off for certain file types, such as markdown or JSON.
The same settings are under Cursor Settings → Tab. The per-extension switch is the one most worth setting: in markdown and JSON, a code-shaped suggestion is mostly noise, and turning Tab off there costs nothing in the files where you want it. Snooze suits a screen share or a pairing session. Use the global switch last. If your complaint is that Tab keeps guessing at your YAML, turning it off everywhere fixes that by removing Tab from every other file too.
Whether Tab costs anything depends on your plan. Unlimited Tab completions are part of Cursor's legacy individual plans from Pro upward. Free users, and users on the legacy Hobby plan, have a limited Tab allowance, and suggestions pause until it resets. Cursor's pricing docs don't say how Tab completions count on the newer paid plans.
Frequently asked questions
Does Cursor Tab suggest edits in other files?
Yes. Tab predicts cross-file edits when a change in one file needs an update in another. When a jump to another file is available, a portal window appears at the bottom of the editor.
How do I accept only part of a Tab suggestion?
Accept it word by word: press ⌘→ on Mac, or Ctrl→ on Windows and Linux. Keep typing to reject whatever is left.
Can I turn Tab off for markdown or JSON files only?
Yes. Click the Tab status indicator in the bottom-right corner of Cursor and choose to disable Tab for specific extensions. You can also snooze it for a set duration or disable it globally.
Do .cursor rules apply to Cursor Tab?
No. Cursor's rules documentation states that rules do not impact Cursor Tab or other AI features; they apply to Agent and its chat. To steer Tab toward a pattern, put a correct instance of it in the file you are editing, since Tab reads your recent edits and the surrounding code.
Can I audit what Cursor Tab writes?
Yes, with two Tab-specific hooks. The beforeTabFileRead hook runs before Tab reads a file and can allow or deny access, so it is where redaction goes. The afterTabFileEdit hook runs after Tab edits a file and receives the edit range plus the line before and after, which suits a formatter or an audit log. Both fire only for Tab, not Agent, and neither runs in cloud agents, because Tab completion is an IDE feature.
Sources & last verified
- Cursor - Tab
- Cursor - Tab issues
- Cursor - Keyboard shortcuts
- Cursor - Rules
- Cursor - Hooks
- Cursor - Models and pricing
- Cursor Docs: Legacy Cursor plans
Cursor ships frequently. Last updated October 28, 2026.