Brooklyn Nicholson eb851d619e fix(desktop): keep slash completion alive after a leading command ... Typing a second slash command in the composer went dead whenever the message started with one. `/work /cle` offered nothing, while `do /work then /cle` completed fine — which read as an intermittent glitch rather than a rule. Two regexes detect a slash, and the `^`-anchored command shape was tried first. Its argument tail (`(?:\s+\S*)*`) swallows the rest of the line, so a later `/skill` parsed as an argument to the first command; a command that takes no options then suppresses the popover outright, and every slash after the first was unreachable. Only the first slash can be an invocation, so detect the inline shape first. It requires a whitespace-preceded slash sitting at the caret, so it can't take over ordinary argument completion (`/personality alic` has no second slash) — it fires only where completion was already dead.		2026-07-27 22:02:06 -05:00
..
bootstrap-installer	fix(installer): stamp the bootstrap-complete marker from the Rust installer	2026-07-26 16:02:13 -05:00
desktop	fix(desktop): keep slash completion alive after a leading command	2026-07-27 22:02:06 -05:00
shared	feat(billing): carry the payment-method union through to clients (#71542)	2026-07-27 01:49:43 +05:30