Repository navigation
[Bug]: First typed /skill in the composer stays plain text while a second one becomes a skill badge #25821
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
apps/web
Summary
In the chat composer, typed /skill invocations aren't converted to skill badges consistently. Often the first /skill I type stays plain text, while a second /skill typed later in the same message does turn into a skill badge/chip.
Possibly related: #14656 (composer styled any $word as a skill chip, closed) and #17655 (second slash-command skill on the same line).
Steps to reproduce
This is intermittent and I haven't found exact repro steps yet. Roughly:
- Focus the chat composer.
- Type
/followed by a skill name, e.g./caveman, as plain text. - It often stays plain text and does not become a badge.
- Further on in the same message, type a second
/skill. - The second one is converted into a skill badge.
Expected behavior
Every typed /skill is handled the same way, whether it's the first one in the message or a later one.
Actual behavior
The first typed /skill often stays plain text, and a second /skill in the same message becomes a badge.
Impact
Minor bug or occasional failure
Version or commit
T3 Code (Nightly) 0.1.3-nightly.20261024.3630
Environment
macOS 26 (Darwin 25.6.0), desktop app
Workaround
None known.
Activity
[-][Bug]: Typed /skill text in the composer sometimes turns into a skill badge on its own[/-][+][Bug]: First typed /skill in the composer stays plain text while a second one becomes a skill badge[/+]NotAnNvidiaFan commentedon Oct 31, 2026
@Baqiwaqi
A few questions to help narrow it down:
.claude/skillsfolder, your personal skills file, or a plugin?/cavemanstayed plain text, did the skill show up in the/menu at all? Or was it missing, then there for the second one?kay-g2 commentedon Nov 9, 2026
Same problem here.
muse-spark-1.3in T3 Code chat.~/.agents/skills/triage/SKILL.md(shows fine in Muse CLI's/menu asuser · default skill)./menu in T3: [pendiente — ¿/triagete aparecía en el menú al teclear/, o ni siquiera salía?]/triageand$triageconsistently arrive at the agent as plain chat text, never dispatching the skill. Other models dispatch the same skill fine.juliusmarminge commentedon Nov 13, 2026
@Baqiwaqi Which provider was the thread using? And when the first
/cavemanstayed plain text: did the/menu show/skill:cavemanat that moment, and did you press Enter or Tab on it, or keep typing a space after the name?