Retain completion command failures without noisy notifications #643

New issue

Closed

opened 2026-05-06 19:55:44 +00:00 by barrettruth · 0 comments

barrettruth commented

2026-05-06 19:55:44 +00:00

Owner

Parent: #634

Problem

Completion helpers often return empty results on command or JSON failure, so broken auth, missing CLI, or network failure looks identical to no completions. Completion should stay quiet while typing, but failure information should not be completely discarded.

Scope

Audit completion source command failures and decode failures.
Preserve diagnostic details in debug logs or a low-noise internal channel.
Avoid user-facing notification spam during command-line completion.
Add tests for completion failure behavior.

Non-goals

Do not make completions slower.
Do not show notifications on every failed completion attempt.

Parent: #634 ## Problem Completion helpers often return empty results on command or JSON failure, so broken auth, missing CLI, or network failure looks identical to `no completions`. Completion should stay quiet while typing, but failure information should not be completely discarded. ## Scope - Audit completion source command failures and decode failures. - Preserve diagnostic details in debug logs or a low-noise internal channel. - Avoid user-facing notification spam during command-line completion. - Add tests for completion failure behavior. ## Non-goals - Do not make completions slower. - Do not show notifications on every failed completion attempt.

barrettruth added the

bug

v0.2.0

labels

2026-05-06 19:55:44 +00:00

barrettruth referenced this issue

2026-05-06 19:56:06 +00:00

Tracker: error handling and edge cases #634

barrettruth referenced this issue from a pull request that will close it,

2026-05-06 22:38:40 +00:00

Retain completion failures quietly #656

barrettruth closed this issue