[DOCS] Conflicting guidance on slash command placement in Interactive Mode vs. Slash Commands documentation

Resolved 💬 3 comments Opened Jan 20, 2026 by coygeek Closed Feb 27, 2026

Documentation Type

Missing documentation (feature not documented)

Documentation Location

Section/Topic

The "Quick commands" table in the Interactive Mode documentation and the "Custom slash commands" intro in the Slash Commands documentation.

Current Documentation

From Interactive mode:
Under the "Quick commands" table:

/ at start | Slash command | See slash commands

From Slash commands:
Under "Custom slash commands":

"Slash command autocomplete works anywhere in your input, not just at the beginning. Type / at any position to see available commands."

What's Wrong or Missing?

The documentation is contradictory. The Interactive Mode page explicitly states that the / must be "at start" to function as a slash command, while the Slash Commands page states that it works at "any position." This creates confusion for users regarding whether commands can be embedded within a natural language prompt or if they must occupy their own line/start of the string to be parsed correctly by the agent.

Suggested Improvement

Update the Interactive Mode documentation to align with the more flexible behavior described in the Slash Commands section.

Suggested change for the "Quick commands" table in Interactive mode:
| Shortcut | Description | Notes |
| :--- | :--- | :--- |
| / | Slash command | Trigger autocomplete and execute commands at any position |

Impact

High - Prevents users from using a feature

Additional Context

Consistency between these two pages is important because "Interactive mode" serves as a quick-reference cheat sheet for new users, while "Slash commands" provides the technical detail. If the tool indeed supports global placement (which matches the behavior of the Skill tool described elsewhere), the "at start" constraint should be removed to avoid misleading users.

Related documentation links:

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗