Improvement process
functionalPress F2 when completion misses the mark; your report can become the test that keeps the fix in place.
Completion gets better when it meets real work. If a suggestion is wrong, missing, or noisy, press F2 while the list is open to capture what happened. A useful report becomes a regression test, giving the fix a much better chance of staying fixed.
When to press F2
Whenever the suggestion list is on screen, a small hint under it reads to improve this, press F2. You can also click the hint itself. Good moments to use it:
- The right item is missing - for example a column you know exists, or a table that should follow
JOIN. - The order is wrong - with the obvious choice buried under less likely ones.
- The list is noise - such as tables offered where only columns make sense.
- Nothing was offered. An empty list reads No suggestions — press F2 to help improve this. That is often the most useful report. Press Ctrl+Space to open the list by hand, then F2.
F2 is the default. You can rebind it in keybindings, where the action is Improve IntelliSense (Capture Feedback).
The feedback dialog


The dialog shows your query with the caret position, the suggestions you were
offered, and a tree of your data model. Your query sits in a read-only text box, so
you can select and copy any part of it. Its cursor starts where your editor caret
was, and the header shows that position as line:column. Only one thing is required: a
note saying what it should have offered. The What should it have offered?
box shows a blinking caret as soon as the dialog opens, so you can start typing
straight away. A good note names the item you expected and where you
expected it, for example after FROM dbo.Orders o JOIN I expected
dbo.Customers first.
- Data model names. The objects your statement refers to start ticked. Tick or untick tables, views, and procedures as you like, or search the tree. Objects that back a suggestion you were shown stay ticked, because the test built from your report needs them. Names only are sent, never data.
- Include all. Sends the whole connection's data model (names only). It is off unless you turn on Include full data model in IntelliSense feedback by default in Settings › Editor › General.
- Relationship chains. Optional. Adds multi-hop foreign-key chains, such as Orders → Customers → Regions, for the tables you include.
- Mask literals. Off by default, so the query is sent as typed. Turn it on to replace string literals and comments with
<redacted>first. See Privacy.
What happens to a report
- Capture (F2). SQLly saves your query, the caret position, the suggestions as shown (with the highlighted one), how the list was opened, your IntelliSense rules, and your app configuration settings. When the list had suggestions, a picture of it goes along too. None of your connection credentials or API keys are included.
- Review. You choose which data model names go along and whether to mask literals. The dialog shows what will be sent.
- Sign and send. On submit, the report is saved to a local file first and then uploaded. If the upload fails, SQLly tries again at the next launch and every five minutes after that, and it never gives up. Each report carries its own ID, so a retry can't post it twice.
- Triage. Submissions arrive in an admin queue for review.
- Lock it in. Accepted reports become cases in a dedicated verification suite: a real test that keeps failing until completion is right.
- Shipped. Once a fix is released, your report on the website's Feedback page shows Implemented in vX.Y.Z with the release that fixed it. Reports are marked automatically when that release is tagged.
Want to see what an IntelliSense feedback report looks like to the dev team? Click here for a real, read-only example, with its ids redacted.