Before submitting
Area
apps/web and apps/desktop
Steps to reproduce
- Run T3 Code Nightly
0.0.29-nightly.20260723.882.
- Open a thread and focus the composer.
- Type
$ to open the skills picker.
- Also try
/ for commands or @ for paths.
Expected behavior
Typing a supported trigger opens the composer autocomplete menu above the composer. If no items match, its empty state should still be visible.
Actual behavior
No autocomplete overlay is visible—not even the empty state. Trigger detection and provider skill discovery still work; the menu is rendered above the composer but clipped by an ancestor.
The current layout wraps ChatComposer in:
<div className="chat-composer-glass-host mx-auto w-full max-w-3xl overflow-hidden rounded-[22px]">
ComposerCommandMenu is rendered inside ChatComposer using an absolutely positioned wrapper above the input:
<div className="absolute inset-x-0 bottom-full z-20 mb-2">
Because the glass host has overflow-hidden, everything positioned above its bounds is clipped. This affects the shared $, /, and @ composer menu, rather than skill discovery specifically.
The clipping wrapper was introduced in fix(web): unify and tune glass surfaces.
Impact
The skills, commands, and path autocomplete UI is unavailable. Users must know and type exact skill or command names manually.
Version or commit
0.0.29-nightly.20260723.882
Regression introduced by 14b6bfdf157c0ce020a5a55e1c8d3d68552931ef.
Environment
macOS desktop app; Codex provider. Provider status successfully returned a non-empty enabled skill list.
Logs or stack traces
No runtime error is emitted; this is deterministic CSS clipping.
Suggested fix
Keep clipping on an inner element that owns only the rounded glass background, or render ComposerCommandMenu outside/through a portal so it is not a descendant of an overflow-hidden container.
A regression test should assert that the menu's visible bounds extend above the composer when typing $, /, or @.
Workaround
Type the exact $skill-name manually, or use a build from before the glass-host wrapper was added.
Before submitting
Area
apps/web and apps/desktop
Steps to reproduce
0.0.29-nightly.20260723.882.$to open the skills picker./for commands or@for paths.Expected behavior
Typing a supported trigger opens the composer autocomplete menu above the composer. If no items match, its empty state should still be visible.
Actual behavior
No autocomplete overlay is visible—not even the empty state. Trigger detection and provider skill discovery still work; the menu is rendered above the composer but clipped by an ancestor.
The current layout wraps
ChatComposerin:ComposerCommandMenuis rendered insideChatComposerusing an absolutely positioned wrapper above the input:Because the glass host has
overflow-hidden, everything positioned above its bounds is clipped. This affects the shared$,/, and@composer menu, rather than skill discovery specifically.The clipping wrapper was introduced in
fix(web): unify and tune glass surfaces.Impact
The skills, commands, and path autocomplete UI is unavailable. Users must know and type exact skill or command names manually.
Version or commit
0.0.29-nightly.20260723.882Regression introduced by
14b6bfdf157c0ce020a5a55e1c8d3d68552931ef.Environment
macOS desktop app; Codex provider. Provider status successfully returned a non-empty enabled skill list.
Logs or stack traces
No runtime error is emitted; this is deterministic CSS clipping.
Suggested fix
Keep clipping on an inner element that owns only the rounded glass background, or render
ComposerCommandMenuoutside/through a portal so it is not a descendant of anoverflow-hiddencontainer.A regression test should assert that the menu's visible bounds extend above the composer when typing
$,/, or@.Workaround
Type the exact
$skill-namemanually, or use a build from before the glass-host wrapper was added.