Desktop /goal and slash command session targeting issues
Cluster 63352 · apps/desktop. Data as of
Nothing open on GitHub. Fix merged in #71632 on 25 Jul 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #71632. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #71605. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These members all concern the desktop app's handling of slash commands, especially /goal, with topics including which chat or session receives the command, a submit that reportedly doesn't reach the backend after /goal, and kickoff behavior when busy. One is a bug report and the others are fix-titled changes; their outcomes are not established by the titles.
Open issues0
Open PRs0
Fixes on record
-
#71605 fix(desktop): slash commands target the user's chat, not a new session
files:
apps/desktop/src/app/session/hooks/use-prompt-actions/index.test.tsx,apps/desktop/src/app/session/hooks/use-prompt-actions/index.ts,apps/desktop/src/app/session/hooks/use-prompt-actions/resolve-target-session.test.ts,apps/desktop/src/app/session/hooks/use-prompt-actions/resolve-target-session.ts,apps/desktop/src/app/session/hooks/use-prompt-actions/slash.ts -
#71632 fix(desktop): /goal kickoff queues when busy instead of vanishing
files:
apps/desktop/src/app/session/hooks/use-prompt-actions/index.test.tsx,apps/desktop/src/app/session/hooks/use-prompt-actions/slash.ts,apps/desktop/src/lib/desktop-slash-commands.test.ts,apps/desktop/src/lib/desktop-slash-commands.ts
1 PR closed without merging
From the close comments: done elsewhere 1
-
#63376 fix(desktop): reuse slash-created runtime session after /goal · done elsewhere →
584b274,#71605,#63352,#68776
Closed issues · 1
- Closed#63352[Bug]: Desktop submit fails after /goal; local session row created but message never reaches backend
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the Lab