Support slash commands mid-sentence and multiple slash commands per prompt

Feature Description

Please support invoking skills/commands when / is typed anywhere in the prompt composer, not only when the prompt starts with /, and allow multiple slash-command invocations in a single prompt.

Current behavior

In the Command Code desktop app, slash suggestions appear when the slash is at the beginning of the input. If I first write prose and then type /, or include a second / later in the same prompt, the command/skill picker does not appear. This makes it difficult to write natural instructions and compose several skills in one request.

Desired behavior

• Typing / after existing text opens the same asynchronously loaded slash menu at the caret.
• Selecting a command inserts or activates it at that position without discarding the surrounding prompt.
• Each slash occurrence can be resolved independently, so one prompt can contain multiple commands/skills.
• Keep the current start-of-prompt behavior and keyboard navigation.
• Preserve ordinary text such as URLs, filesystem paths, and escaped slashes.

Example

Audit this interface with /impeccable, check keyboard access with /accessibility, then browse the docs with /browser.

This would match the inline slash workflow I use in Codex today.

Use Case

Natural-language requests often introduce a skill after the goal is stated. Requiring the user to move every command to the first character breaks the flow of the request, makes multi-step work awkward, and can make skills appear unavailable.

Inline invocation would reduce prompt restructuring, let users compose workflows naturally, and make Command Code a smoother replacement for Codex-style slash skill calls.

Additional Context

Observed on Command Code desktop v0.1.8 on macOS. In a Discord discussion, the Command Code team/community clarified that the current slash menu is surfaced at the start of input and recommended filing a GitHub feature request for mid-prompt skill invocation.

This request covers both related behaviors: (1) invoking a slash command after existing text and (2) using multiple slash commands in one prompt. It is a usability/feature request and does not require changing the existing command catalog.

How important is this to you?

Important for my workflow

Start by tracing the desktop prompt composer and the existing start-of-prompt slash-menu behavior. Check how asynchronously loaded suggestions, caret insertion, keyboard navigation, URLs, paths, and escaped slashes are handled; done means inline and multiple commands work without losing surrounding text while existing behavior remains intact.