Improvement process

Press 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 to capture what happened. A useful report becomes a regression test, giving the fix a much better chance of staying fixed.

The feedback dialog

SQLly

What happens to a report

1. Capture (F2). SQLly saves the statement, cursor context, and the scoped catalog slice needed to reproduce the case.
2. Redact. SQL literals are removed and the catalog snapshot stays scoped before anything leaves your machine. See Privacy.
3. Sign and send. The report uploads in the background with retries, so a flaky connection does not lose your feedback.
4. Triage. Submissions arrive in an admin queue for review.
5. Lock it in. Accepted reports become cases in a dedicated verification suite: a real test that keeps failing until completion is right.