[Bug] Custom slash command without arguments clears user input from history

Bug Description
It sucks SO bad when I use a custom slash command that doesn't take arguments (but meant to use one │
│ that did) b/c I write out all my instructions but when I run the command, all my argument is │
│ essentially erased and not recoverable (as far as I can tell). At the very least, if I pressed ↑ up │
│ arrow to run previous command, I would expect it to show ALL that I wrote previously, not just the │
│ custom clash command that wouldn't take arguments... arg!

Environment Info

• Platform: darwin
• Terminal: WarpTerminal
• Version: 2.0.76
• Feedback ID:

Errors

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/kk/.local/share/claude/versions/2.0.76 (expected in multi-process scenarios)\n    at XZR (/$bunfs/root/claude:2430:2165)\n    at fUA (/$bunfs/root/claude:2430:1885)\n    at processTicksAndRejections (native:7:39)","timestamp":"2025-12-23T14:46:01.297Z"},{"error":"Error\n    at ak (/$bunfs/root/claude:59:1144)\n    at <anonymous> (/$bunfs/root/claude:60:10093)\n    at emit (node:events:92:22)\n    at endReadableNT (internal:streams/readable:861:50)\n    at processTicksAndRejections (native:7:39)\n    at request (/$bunfs/root/claude:62:2149)\n    at processTicksAndRejections (native:7:39)","timestamp":"2025-12-23T14:46:01.483Z"},{"error":"Error\n    at ak (/$bunfs/root/claude:59:1144)\n    at <anonymous> (/$bunfs/root/claude:60:10093)\n    at emit (node:events:92:22)\n    at endReadableNT (internal:streams/readable:861:50)\n    at processTicksAndRejections (native:7:39)\n    at request (/$bunfs/root/claude:62:2149)\n    at processTicksAndRejections (native:7:39)","timestamp":"2025-12-23T14:48:55.269Z"}]