Desktop app doesn't render argument-hint for custom slash commands (CLI does)

Resolved 💬 0 comments Opened Jun 20, 2026 by sekhar-88 Closed Jun 21, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report
  • [x] I am using the latest version of Claude Code

What's Wrong?

Custom slash commands defined in .claude/commands/*.md can declare an argument-hint frontmatter field. The Claude Code CLI renders this as greyed-out placeholder text after the command name, but the Claude desktop app (macOS) does not — it only shows the description. The desktop app ignores argument-hint, so users lose the inline reminder of what arguments a command accepts.

What Should Happen?

The desktop app should render argument-hint (as placeholder text, or otherwise surface it) when a custom slash command is selected, matching the CLI's behavior — so command-argument hints are consistent across surfaces.

Error Messages/Logs

None — there is no error. argument-hint is silently not rendered in the desktop app.

Steps to Reproduce

  1. Create .claude/commands/greet.md:

``yaml
---
description: Say hello to someone.
argument-hint: "[name]"
---
Greet $ARGUMENTS.
``

  1. In the CLI, type /greet → the [name] hint appears as placeholder text. ✅
  2. In the desktop app, type /greet → only the description is shown; no argument hint. ❌

Claude Model

Not applicable — this is a client-side UI rendering issue, model-independent.

Is this a regression?

I don't know.

Claude Code Version

CLI: 2.1.183 (Claude Code) — renders the hint correctly. Desktop app (macOS): version unknown — does not render the hint.

Platform

Anthropic API

Operating System

macOS

Related

  • #62127 — TUI-side argument-hint truncation (related but distinct: that's the CLI failing to display it fully; this is the desktop app not rendering it at all).

View original on GitHub ↗