Fuzzy matching for # Slack-channel autocomplete in the CLI composer

Feature request

The interactive CLI composer autocompletes Slack channel names when typing # (with the Slack integration connected). The matching is prefix-only: typing #pr lists #preview-checks, #product-ai, #product-asset-discovery, … but typing #flag finds nothing, even though #product-feature-flag exists.

In workspaces with naming conventions like product-*, team-*, or use-case-*, the distinctive part of a channel name is almost never the prefix — every channel shares the same first characters, so prefix matching forces you to type the boilerplate before the part you actually remember.

Requests

1. Fuzzy/substring matching — #flag should match #product-feature-flag; ideally subsequence matching (#pff → #product-feature-flag) like the file @-mention autocomplete and most fuzzy finders.
2. Rank by recency/frequency — channels I recently drafted to or mentioned should sort above alphabetical strangers.
3. Highlight matched characters in the suggestion list so it's clear why an item matched.
4. (Nice to have) Match against channel topic/description as a fallback when the name has no hit.

Environment

• Claude Code v2.1.222 (macOS, arm64)
• Slack via the official slack@claude-plugins-official plugin + Slack MCP connector

As far as I can tell the matcher is native to the CLI (no setting, plugin hook, or MCP-resource path controls it), so this can only be fixed upstream. Happy to provide more detail.