Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Mobile: slash-command typeahead parity with CLI [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#56204•Fetched 2026-05-06 06:34:24
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Author
Clean-ColeClean-Cole
Participants
Clean-ColeClean-Cole
Timeline (top)
labeled ×4

Code Example

> /pla█
/plan
/flow:plan
/flow:plan
/ultraplan
/plugin
/batch
RAW_BUFFERClick to expand / collapse

Feature request

On mobile, typing / doesn't show a typeahead list of available slash commands. The desktop CLI does this — see screenshot below from CLI:

> /pla█
/plan
/flow:plan
/flow:plan
/ultraplan
/plugin
/batch

Mobile (claude.ai/code via phone browser) just submits whatever I type after / as if it were prose. No autocomplete, no list of available skills.

Why it matters

Heavy users on the road accumulate dozens of skills (especially with plugins). Discovering / typo-correcting slash commands without a typeahead is rough on a phone keyboard. Parity with the desktop CLI's behavior would close the gap.

Suggested behavior

Match the CLI exactly: as soon as the input starts with /, drop a dropdown listing matching skills filtered by what's typed. Tap to select. Existing CLI surface — mobile should reuse the same backend.

Environment

  • Surface: claude.ai/code on iOS Safari (also seen on the official mobile app if it exists)
  • Versus: desktop Claude Code CLI on macOS, where typeahead works as shown

extent analysis

TL;DR

Implementing a typeahead feature for slash commands on mobile devices, similar to the desktop CLI, would likely resolve the issue.

Guidance

  • Verify that the mobile application is sending the correct input events to the backend when the user types a slash command, and that the backend is processing these events correctly.
  • Check if the desktop CLI's typeahead functionality is handled client-side or server-side, and determine if the same approach can be applied to the mobile application.
  • Consider implementing a dropdown list of available skills that filters as the user types, similar to the suggested behavior.
  • Investigate if there are any existing APIs or endpoints that can be reused to provide the list of available skills on mobile devices.

Example

No code example is provided as the issue does not contain sufficient technical details.

Notes

The solution may require modifications to both the mobile application's frontend and backend, as well as potential changes to the existing API or endpoint that handles slash commands.

Recommendation

Apply workaround: Implement a typeahead feature for slash commands on mobile devices, reusing the existing backend API or endpoint if possible, to provide a similar user experience to the desktop CLI.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#integration issue#index setup#retrieval issue#search optimization#API routing

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Mobile: slash-command typeahead parity with CLI [1 participants]