Repository navigation
[BUG]: Dollar Skill invocation in question tool UI glitches out #7805
Description
Activity
- changed the title
[-]Dollar Skill invocation in question tool UI glitches out[/-][+][BUG]: Dollar Skill invocation in question tool UI glitches out[/+]on Aug 21, 2026 Found an easier solution, therefore the new PR. I guess "fixing" the skill invocation etc in the composer itself would be better, but this would increase scope & impact a lot.
Video of the working version:
t3code_issue_fixed.mov
Related report #8128 covers the same problem and adds useful evidence.
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 linking the report here before I close it as a duplicate during an automated pass. The source report and its attachments will remain available at #8128.
Still reproduces on T3 Code 0.0.36 (8fc7f22).
Typing $ to reference a skill inside the native question form wedges the composer. Text cannot be deleted, and switching threads does not restore input. The affected thread remains unusable until the full desktop app is restarted.
Still reproduces on macOS in T3 Code (Nightly) 0.0.41-nightly.20260911.1533, using Codex / GPT-6-Astra.
With an agent question open, typing
$heliumand selecting the skill leaves the picker stuck. It won't dismiss, Backspace stops working, and further interaction eventually reaches “Something went wrong.” Selecting the same skill in another chat without an open question works.Crash time: 2026-09-11T12:13:30.046Z. Lexical error #20 is
Point.getNode: node not found.Crash stack
Error: Minified Lexical error #20 at k (t3code://app/assets/ComposerPromptEditor-DB9JutLB.js:3:1390) at Di.getNode (t3code://app/assets/ComposerPromptEditor-DB9JutLB.js:10:2834) at t3code://app/assets/ComposerPromptEditor-DB9JutLB.js:16:3703 at va (t3code://app/assets/ComposerPromptEditor-DB9JutLB.js:13:21920) at e.read (t3code://app/assets/ComposerPromptEditor-DB9JutLB.js:13:38615) at t3code://app/assets/ComposerPromptEditor-DB9JutLB.js:16:3634 at ba (t3code://app/assets/ComposerPromptEditor-DB9JutLB.js:13:25011) at ya (t3code://app/assets/ComposerPromptEditor-DB9JutLB.js:13:24517) at Ua.setRootElement (t3code://app/assets/ComposerPromptEditor-DB9JutLB.js:13:47252) at t3code://app/assets/ComposerPromptEditor-DB9JutLB.js:13:75079I have a recording, but it contains unrelated private content, so I'm not attaching it.
Reacted by CulpableStill reproduces in T3 Code (Nightly) 0.0.41-nightly.20260915.1766.
- Have the agent ask a question with options.
- Start typing a custom answer, type
$and part of a skill name. - Move through the picker with the arrow keys and press Enter.
The skill is not inserted, the picker stays open, and the answer field no longer accepts any edits (typing, deleting).
Reconfirmed on T3 Code Nightly
0.0.43-nightly.20260923.2150in the macOS desktop app with the Codex provider (GPT-6 Sol). The fuller report, #13291, was closed as a duplicate of this issue.With an agent question card open, I typed
$write-to-in the answer composer. The matching personal skill appeared in the$picker. Clicking that suggestion closed the picker, but left$write-to-in the composer instead of inserting the complete skill name. The selection was inert. Since question responses are plain-text answers, this field should not offer a skill suggestion that cannot be used. This adds a mouse-click result on the newer nightly build to the keyboard-selection reports above.I did not verify whether the field became locked, whether other threads were affected, or whether the same result occurs without a pending question on this build. The reporter-provided screenshots show the suggestion before the click and the unchanged prefix afterward. They were not attached to the public report; unrelated question content and thread identity were omitted.
Still reproduces on macOS, Codex provider, 2026-10-10. Version: T3 Code (Nightly) 0.0.46-nightly.20261009.2886.
The agent's question had no options, only a free-text answer field. Typing
$or/plus part of a skill name opens the suggestions. Neither clicking a suggestion nor pressing Tab completes it. The partial text stays in the field.This adds Tab to the click result reported above on 0.0.43. It also confirms the problem for a question with no options.
I have a short screen recording (19 s) and can share it if it helps.
Would love to work on this, If I would only know what style/ scope of solution is prefered here..
What happened
When a provider asks the user a question, the custom-answer composer still supports
$skillsuggestions and renders selections as skill tokens.Submitting this composer responds to the pending question with plain answer strings. It does not start a provider turn or explicitly invoke the selected skill. The picker can remain visible after submission, the previous answer can leak into the next question, and the editor enters recursive update failures.
This affects web and desktop. Mobile uses a plain text input for question answers.
Steps to reproduce
$find-skillsinto the custom answer.Expected behavior
Question answers should treat
$skillsyntax as plain text. They should not show skill suggestions or create skill tokens.Submitting should send the answer once and reset the composer state.
Actual behavior
The custom-answer editor shows the skill picker even though pending question responses only support answer strings. After submission, the picker can remain visible and the previous
$find-skillsvalue can leak into the next question. The provider may infer the skill from the text, but T3 did not explicitly invoke it.Impact
Major degradation or frequent failure.
Version and environment
mainat549201fcfLogs
Recording
t3code_issue_trimmed.mov
Workaround
Avoid
$skillsyntax in custom question answers. Select a predefined answer or enter plain text without$.