[Bug]: Mobile composer loses focus after selecting skill via $ / / — requires re-tapping textbox

[screen-gd]

[Bug]: Mobile composer loses focus after selecting skill via $ / / — requires re-tapping textbox

Description

On T3 Code Mobile (native Android app, not t3.chat web), after invoking the skill picker with $ or / and selecting a skill, the composer textbox loses focus. The user must tap the textbox again to continue typing.

Reporter device:

• App: T3 Code Mobile (Android) — apps/mobile (ThreadComposer / ComposerCommandPopover)
• Model: Xiaomi Redmi 12 5G (sky / 23076RN8DY) — Snapdragon 4 Gen 2 variant (also sold as Redmi Note 12R / POCO M6 Pro 5G)
• SoC: Qualcomm SM4450 Snapdragon 4 Gen 2 — 4 nm, Octa-core (2×2.2 GHz Cortex-A78 + 6×1.95 GHz Cortex-A55), Adreno 613
• OS: Sakura OS custom ROM (AOSP/Lineage-based, Android 13 base — device shipped Android 13 / MIUI 14)

This issue was filed by an LLM — Muse Spark (opencode/muse-spark-1.2-contributor-free) — on behalf of the reporter. Device chipset details sourced from public specs (GSMArena, Xiaomi, Sakura-Devices device_xiaomi_sky).

Steps to Reproduce

1. Open T3 Code Mobile on Android — e.g., Redmi 12 5G + Sakura OS.
2. Start a new thread / open any thread composer.
3. Type $ or / to open the skill picker.
4. Select any skill from the list (tap).
5. Observe composer textbox state — it is deselected/blurred.

Expected Behavior

After selecting a skill, the skill token is inserted and the composer retains focus with the keyboard still open and cursor after the token, so typing can continue immediately.

Actual Behavior

After selection, the textbox is deselected/blurred — keyboard dismisses or input is unfocused. User must tap the textbox again before typing.

Additional Finding

• Also reproduces when using / for skills (same focus loss as $).
• Workaround that works: Delete the inserted text entirely and then re-add the skill using any command trigger ($ or /) — on the second insertion, focus is retained correctly and typing can continue without re-tapping. This suggests the first insertion blurs the editor, but a clean re-insertion restores the expected focus path.

Environment

• App: T3 Code Mobile (Android, apps/mobile)
• Device: Redmi 12 5G (sky) — Snapdragon 4 Gen 2 (SM4450)
• OS: Sakura OS custom ROM (Android 13 base)
• Reproducible: Yes, consistent on reporter device — not t3.chat web, strictly T3 Code Mobile

Suggested Fix

After skill insertion via $//, re-focus the editor and preserve selection (e.g., editor.focus() / composerRef.current?.focus()), preventing default blur on the menu item's tap or calling requestAnimationFrame(() => editor.focus()) to keep the keyboard open on Android.

Reporter Notes

Original report: "After I select a skill using the $ sign the text box is deselect like I have to click on the box again to type anything" — Redmi 12 5G, Sakura OS, Snapdragon 4 Gen 2. Updated: also happens with / for skills; deleting text and re-adding the skill works fine. Clarified: T3 Code Mobile, not t3.chat.

[juliusmarminge]

Triage

Confirmed as a real mobile composer focus bug. After picking a skill from the $ menu, the token is inserted but the editor loses focus, so the keyboard drops and you have to tap the textbox again. Same insert path is used for / skill rows (#7737) and @ file picks, so those taps are likely affected too.

This is not a duplicate of #7498 (picker missing on new-task), #5792 (browser-automation focus steal), #7440 (iOS keyboard position), or #10153 (screen-reader suggestions). No open PR fixes this.

What’s going on

Web (t3.chat / Android Chrome — reported surface)

• Suggestion rows in apps/web/src/components/chat/ComposerCommandMenu.tsx only preventDefault on mousedown.
• Other composer chrome already uses onPointerDown preventDefault so a tap doesn’t steal the editor (ComposerPrimaryActions, expand/send, stash).
• The menu is portaled to document.body. On a mobile viewport, losing editor focus collapses the composer (scheduleComposerCollapseCheck / isComposerCollapsedMobile).
• Skill insert already does a rAF focusAt(). On Android Chrome that often does not bring the IME back once a touch has blurred the field. The reliable fix in this codebase is to stop the blur on pointerdown, not only re-focus afterward.

Native (apps/mobile — same class of gap)

• ComposerCommandPopover is a Pressable list with keyboardShouldPersistTaps="always".
• useComposerCommandMenu onSelect writes the $name token and cursor but never calls editor.focus().
• ThreadComposer / NewTaskDraftScreen treat editor blur as “collapse the card”. T3ComposerEditor already exposes focus().

Suggested fix

1. Web: add onPointerDown={(e) => e.preventDefault()} on ComposerCommandMenuItem (keep the existing mousedown guard and rAF focusAt).
2. Native: after a picker select, focus() the composer so blur doesn’t collapse it.
3. Check $, / skill rows, and @ on Android Chrome (and native if that path is touched).

Severity: medium (extra tap + keyboard bounce on a core mobile prompt flow).

Accepting this. A small, localized focus-preservation change on the shared picker select path.