Partway through a component you begin calling a date-formatting helper that lives in another module and has never been imported into this file. Tab offers a suggestion covering the call. What can that single accepted suggestion reasonably do?

The principle — A Tab suggestion is not bounded by the line the cursor sits on. Cursor documents that Tab can modify multiple lines, add missing import statements, and suggest coordinated edits across related code. The unit of work is the edit you appear to be making, not the line you happen to be typing.

Why the key is correct — The situation has exactly the two features Tab handles in one go: a call that will occupy more than one line, and a symbol that is not yet imported. Accepting once can produce both the call and the import at the top of the file. That is worth knowing because the alternative — describing the same change in the chat panel — is slower for a change this small, and because the import is the part people most often write by hand without noticing it was already on offer.

Why the others are wrong — Stopping at the end of the current line describes older editor autocomplete, not Tab, and treating every multi-line change as chat work means abandoning the cheapest tool available. Restricting suggestions to the file header invents a boundary that does not exist; the import and the code that needs it come from the same suggestion precisely because they belong to the same edit. A separate approval panel belongs to other editing flows in Cursor; a Tab suggestion is displayed inline and accepted with the Tab key, with nothing written until you accept.

Remember this — If the next few lines and a missing import are both obvious from what you are typing, try Tab before opening anything else.

Sources — Cursor's Tab completion documentation.