Typing a second slash command went dead whenever the message started with one: `/work /cle` offered nothing while `do /work then /cle` completed fine, which reads as an intermittent glitch rather than a rule. Only the first slash can be an invocation, so detect the inline shape first. The leading-command branch claimed the whole line and handed it to the backend's completer, which has nothing to say about a slash sitting in a command's argument tail. The inline trigger requires a whitespace-preceded slash at the caret, so ordinary argument completion (`/cron ad`, `/personality alic`) is untouched — it fires only where completion was already dead. |
||
|---|---|---|
| .. | ||
| __tests__ | ||
| app | ||
| components | ||
| config | ||
| content | ||
| domain | ||
| hooks | ||
| lib | ||
| protocol | ||
| sdk | ||
| types | ||
| app.tsx | ||
| banner.ts | ||
| entry.tsx | ||
| gatewayClient.ts | ||
| gatewayTypes.ts | ||
| theme.ts | ||
| types.ts | ||