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
I searched existing issues and did not find a duplicate.
I included enough detail to reproduce or investigate the problem.
Area
apps/mobile
Steps to reproduce
Open a Claude thread in the T3 Code iOS TestFlight beta.
Have background work running so the floating “Running: …” status pill is visible.
Focus the composer with the on-screen keyboard open.
Type /status to display the COMMANDS suggestion panel.
Observe the running-status pill overlapping the command suggestion.
Reproduction frequency has not been established.
Expected behavior
Slash-command suggestions remain unobstructed and readable while the running-status pill is visible, including with the keyboard open.
Actual behavior
The “Running: Wait for the baseline grid and score it” pill appears directly over the suggestion row beneath COMMANDS, obscuring the command name and description.
The captured screenshot demonstrates the visual overlap. Whether the pill also intercepts taps has not been tested.
Impact
Minor bug or occasional failure — command suggestions are difficult to read while background work is running.
Version or commit
T3 Code iOS TestFlight beta 2.0.0. TestFlight build number and server version not recorded.
Environment
Device: iPhone 16 Pro Max.
OS: iOS 26.6.2.
Client: T3 Code native iOS app, TestFlight beta 2.0.0.
Portrait orientation, dark appearance.
On-screen keyboard open.
Claude Opus 5.5 selected.
Background work active.
Logs or stack traces
Not collected. No error message is shown.
Screenshots, recordings, or supporting files
Screenshot IMG_2301.png is pending upload. It shows the running-status pill covering the command suggestion panel above the composer.
Thanks for the detailed report, @rustanacexd! This matches current main (e22c880434), and TestFlight 2.0.0 is the current version in apps/mobile/app.config.ts. I didn't find a duplicate.
What I found
The "Running: …" text is the settled-thread background pill. When the only leftover work is a command, presentPendingBackgroundWork titles it Running: ${description} (packages/client-runtime/src/state/threadExecution.ts), and ThreadDetailScreen shows it on the floating pill as kind: "background".
FloatingWorkingControl is absolute at top: -CONTROL_OVERLAY_OFFSET with z-20, which puts it in roughly the first 40px above the composer.
ComposerCommandPopover is absolute inset-x-0 bottom-full z-10 mb-2 inside ThreadComposer and grows upward through the same band. On a short list like /status, the suggestion row lands under the pill. Because the pill's z-20 is on a sibling of the composer, it paints on top. KeyboardStickyView moves both together, so the keyboard doesn't change it.
floatingControlLift already raises the pill for the question card but doesn't account for the command menu. The same overlap would apply to the Working, Waiting, Syncing, and Compacting pills and to the @-file, skill, and pull-request menus. Android uses the same positions.
The background pill sets pointerEvents to none unless it also shows a queue, agents, or device preview, so taps should still reach the row underneath (not verified on a device).
Likely fix area
One option is in ThreadDetailScreen / FloatingWorkingControl: measure the open ComposerCommandPopover and raise the pill by that height, the same way the question-card lift works. Only reordering the z-index probably wouldn't be enough, since the pill's glass is translucent.
Activity
juliusmarminge commentedon Oct 5, 2026
Note
Grok responding on behalf of Julius.
Triage
Thanks for the detailed report, @rustanacexd! This matches current
main(e22c880434), and TestFlight 2.0.0 is the current version inapps/mobile/app.config.ts. I didn't find a duplicate.What I found
presentPendingBackgroundWorktitles itRunning: ${description}(packages/client-runtime/src/state/threadExecution.ts), andThreadDetailScreenshows it on the floating pill askind: "background".FloatingWorkingControlisabsoluteattop: -CONTROL_OVERLAY_OFFSETwithz-20, which puts it in roughly the first 40px above the composer.ComposerCommandPopoverisabsolute inset-x-0 bottom-full z-10 mb-2insideThreadComposerand grows upward through the same band. On a short list like/status, the suggestion row lands under the pill. Because the pill'sz-20is on a sibling of the composer, it paints on top.KeyboardStickyViewmoves both together, so the keyboard doesn't change it.floatingControlLiftalready raises the pill for the question card but doesn't account for the command menu. The same overlap would apply to the Working, Waiting, Syncing, and Compacting pills and to the @-file, skill, and pull-request menus. Android uses the same positions.pointerEventstononeunless it also shows a queue, agents, or device preview, so taps should still reach the row underneath (not verified on a device).Likely fix area
One option is in
ThreadDetailScreen/FloatingWorkingControl: measure the openComposerCommandPopoverand raise the pill by that height, the same way the question-card lift works. Only reordering the z-index probably wouldn't be enough, since the pill's glass is translucent.A maintainer will decide on the fix direction.