[FEATURE] Bring the CLI session recap (/recap and the away summary) to the desktop app
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Searched recap, away summary, and desktop recap. The three live recap issues (#85519, #85922, #86159) all ask for changes to the CLI recap. None asks for the feature in the desktop app.
Problem Statement
I come back to a desktop session and cannot tell where it stands without reading the scrollback.
I run many Claude Code desktop sessions at once, one per git worktree, and I switch between them all day. Every switch costs the same tax: scroll up, find the last few tool calls, work out what the session was doing and what it was about to do next.
The CLI already solves this. Version 2.1.258 shows a session recap when you return after being idle, and /recap generates one on demand. The desktop app has neither, so the app where I keep the most sessions is the one with the least help returning to them.
The gap is larger in the desktop app than in the terminal. A terminal user blurs one window and comes back to it. A desktop user picks one session out of a sidebar of a dozen, so the "where was I" cost is paid on every switch, not just after a break.
Proposed Solution
Bring both halves of the CLI feature to the desktop app.
- On-demand recap. A
/recapcommand in the desktop app, matching the CLI's "Generate a one-line session recap now". - Return recap. When I open a session I have not looked at for a while, show the same short recap line the CLI shows: the goal, the current task, and the one next action.
- A setting to turn it off. The CLI has a
Session recaptoggle in/config, backed byawaySummaryEnabled. The desktop app needs the equivalent in its own settings UI, because/configopens a terminal dialog that desktop sessions cannot show.
Two desktop-specific details worth deciding on:
- Trigger on session switch, not just on window blur. The CLI reads terminal focus (
msSinceFocus,blurDurationMs). In the desktop app the useful signal is per-session: how long since I last viewed this session, not since I last looked at the app. - Show it in the sidebar too. A one-line recap on each session row would let me pick the right session without opening three of them first. This is the same need behind #85519, which asks the CLI recap to name its repo.
Reusing the CLI's existing skip rules would be good: it already declines to recap when background work is pending or a loop wakeup is queued.
Alternative Solutions
- Session titles. They tell me the topic, never the state. A title set an hour ago does not say what the session is doing now.
- Scrolling the transcript. What I do today. It works and it is slow, and it is worst on long sessions where the answer is furthest from the bottom.
- Asking the session. Typing "where are we" works, but it costs a full turn on the session model and lands in the transcript as real conversation. The CLI recap runs outside the turn, which is the better shape.
- The
/standupstyle skill. I have a project skill that reports session state. It is a workaround for the same gap, and it needs me to remember to invoke it, per session.
Priority
High - Significant impact on productivity
Feature Category
Other (Claude Code desktop app)
Use Case Example
- I have twelve desktop sessions open, one per worktree, each on its own branch.
- I spend forty minutes in one session reviewing a PR.
- I switch back to a session I last touched two hours ago. It has run maybe sixty tool calls since.
- Today: I scroll up, read tool calls backwards, and reconstruct what it was doing.
- With this feature: the session shows one line at the top saying the goal, the current task, and the next action, the same way the CLI does.
- I pick up in seconds instead of a minute or two, times a dozen switches a day.
Additional Context
What I observed in the CLI, version 2.1.258 on Windows:
- The
/configmenu has aSession recaptoggle, alongsidePrompt suggestionsandRewind code (checkpoints). - The setting is
awaySummaryEnabled, documented as: "When false, the session recap (shown when you return after being away for 5+ minutes) is disabled. When absent or true, recap is enabled." - The recap prompt asks for "under 40 words, 1-2 plain sentences, no markdown. Lead with the overall goal and current task, then the one next action."
/recapexists as a command, described as "Generate a one-line session recap now", and answers "Nothing to recap yet" on an empty session.- There is a
DISABLE_AWAY_SUMMARYescape hatch and aCLAUDE_CODE_ENABLE_REMOTE_RECAPflag.
Desktop app version 1.40609.1. I could not find a /recap command in a desktop session's command list, and could not find a session recap setting in the app.
Related, all CLI-scoped: #85519 (recap should name the repo, which matters more with many sessions), #86159 (make the idle threshold configurable), #85922 (recap billing), and closed #48084 (docs for /recap and the away-summary controls).
3 Comments
Still open. To place it against the existing recap issues: I searched
recap,away summaryanddesktop recap, and the three live ones, #85519, #85922 and #86159, all ask for changes to the CLI recap. None asks for the feature in the desktop app.The ask is parity, both halves. An on-demand
/recapin the desktop app matching the CLI's, and the idle-return summary the CLI shows when you come back after a break.The reason the gap is larger in the app than in the terminal is switching cost. A terminal user blurs one window and comes back to it, so the summary is a convenience. A desktop user picks one session out of a sidebar of a dozen, so the "where was I" tax is paid on every switch rather than after a break. The app where I keep the most sessions is the one with the least help returning to them.
Still open. The idle-return summary in the CLI is the half that would help most in the desktop app. The app's sidebar makes switching between sessions cheap, but each switch still means scrolling back to find where the session stood.
An on-demand
/recapwould be a good first step even without the automatic summary. The existing recap issues, #85519, #85922 and #86159, are all about the CLI version. None of them asks for this in the desktop app.Still open. One possible home for the return recap in the desktop app is the sidebar itself. Each session already has a title there. A one-line recap under the title, or on hover, would answer "where does this session stand" without opening the session at all.
The two halves are independent. An on-demand
/recaphelps a user who is already inside a session. The return summary helps a user choosing which session to open. Either one shipped alone would be useful.