You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Skill/slash picker inside a question's custom-answer field cannot be dismissed and wedges input in every thread #8128
I searched existing issues and did not find a duplicate.
I included enough detail to reproduce or investigate the problem.
Area
apps/desktop
Steps to reproduce
Desktop app 0.0.33 (Alpha), Claude provider, macOS.
Create a thread and let the agent ask a question via its question tool (AskUserQuestion), so the option card renders.
Click into the custom answer / "Other" free-text field of that card and type / or $ so the skill / slash-command picker opens, then pick a skill.
Try to dismiss the picker (Esc, click outside), answer the question, or type — here and in other threads.
Expected behavior
The picker closes on Esc or an outside click, the question card stays reachable, and the field keeps accepting input — the same way @ mentions in this field were fixed in #2635.
Actual behavior
The skill list renders on top of the question card and cannot be dismissed: Esc and outside clicks do not close it, and the options underneath are unreachable, so the question can no longer be answered. The custom-answer field keeps the partially typed skill name and refuses all further input. The wedge is not scoped to the thread — composers in other threads are dead too, so nothing can be sent anywhere in the app.
Note: this looks like the / + $ counterpart of #2635 (@ mentions in the custom-answer field), which was closed as fixed by the pending-user-input composer work (commits 3ff2e3d and 6ae5aee). The mention path was routed into custom-answer state; the skill/slash path appears not to have been.
Impact
Blocks work completely
Version or commit
0.0.33 (desktop Alpha)
Environment
macOS 26.3.1 (25D2128), Apple Silicon, T3 Code Desktop 0.0.33 Alpha, Claude provider
Workaround
Restart the app (per #2569, a hard reload of the Electron window may also clear it).
Could you try this on the Nightly build too? And check if it also happens with different providers (if you have access to those, don't get a sub just to test this).
Thanks for the detailed report. This looks like the same issue tracked in issue #7805.
The earlier issue #7805 describes the same Claude custom-answer skill picker, skill-token selection, stuck picker, and recursive editor updates on desktop 0.0.33. Both reports use the same pending-answer editor path. The slash trigger and app-wide input lock in this report are useful extra conditions, so they must remain with the canonical report. The proposed repair is still open.
I'm closing this as a duplicate as part of an automated pass on all open issues. I linked this report from issue #7805 so its extra details remain available. This does not mean the underlying bug is fixed.
Activity
lnieuwenhuis commentedon Aug 25, 2026
Could you try this on the Nightly build too? And check if it also happens with different providers (if you have access to those, don't get a sub just to test this).
t3dotgg commentedon Aug 27, 2026
Thanks for the detailed report. This looks like the same issue tracked in issue #7805.
The earlier issue #7805 describes the same Claude custom-answer skill picker, skill-token selection, stuck picker, and recursive editor updates on desktop 0.0.33. Both reports use the same pending-answer editor path. The slash trigger and app-wide input lock in this report are useful extra conditions, so they must remain with the canonical report. The proposed repair is still open.
I'm closing this as a duplicate as part of an automated pass on all open issues. I linked this report from issue #7805 so its extra details remain available. This does not mean the underlying bug is fixed.