You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
1.0.94
Feat: Ghostty switches to the right tab when several sessions share a directory (#63). Ghostty's tip builds expose each terminal's tty (ghostty-org/ghostty#11922), so switching now works the way it does in iTerm2 and Terminal.app: by tty and by /rename title, in the order the session's process provenance calls for, and only then by working directory. Before, a session without a custom title went to the first tab in its directory — measured on one machine with 16 sessions sharing ~/git, every one of them landed on the same tab. Detection's fallback cross-reference uses the tty the same way. Stable Ghostty (1.3.1 and earlier) has no tty, so there CodeV behaves exactly as before — title, then directory — until a release ships it
Fix: detection's fallback cross-reference no longer gives a running process to the wrong session when one /rename title contains another (Fix inside Fix backend). Every terminal (iTerm2, cmux, Terminal.app, Ghostty) took the first title its tab matched, from every transcript in the directory; it now takes the longest match among the sessions actually queued for that process. One function for all four, where there used to be four copies
Fix: closing Settings puts the cursor back in the search box. Opening Settings moves focus into its panel, as before; but closing it with the same button left focus on that button, so typing searched nothing until you clicked a row or switched apps and back. The Settings button counts as part of the panel, which the switcher deliberately never steals focus from, so its click-to-refocus skipped it. Closing the panel now hands focus back to the current tab's search box
Feat: Claude Desktop's Code sessions show up in the Sessions tab (#111), running and closed, with a ✳ DESKTOP badge on every one of them — unlike the terminal badges, which appear only on running sessions, because it says where a click goes rather than where a process was found. Selecting one opens it in Desktop through Desktop's own link for that session, so two sessions in one directory cannot be confused; for a closed one, Desktop starts the process itself, as its own sidebar does. The link needs Desktop's id for the session, which differs from Claude Code's and is read from Desktop's session records. Desktop never writes history.jsonl, so these are read from their transcripts, the way VS Code sessions already were. A Desktop session counts as running only while Desktop has a process for it — after you open it there, not merely because it is in Desktop's sidebar
Fix: VS Code and Desktop rows no longer vanish for a moment each time the window comes back. Every refetch rebuilt the list from history.jsonl and added those rows only when background detection finished, so they dropped out and reappeared further up, shifting the list
Fix: a running Desktop session no longer lights up an unrelated session. Its id was not in history.jsonl, so detection guessed by directory and gave Desktop's process to a closed CLI session in the same folder whenever that folder had one (found by reading the code; Desktop's process sits under no terminal, so the title cross-reference could not catch it)
Fix: a VS Code or Desktop session whose transcript has a pasted image near its start or end could show no prompts and a time of 0, which sorted it out of the list. The two reads exceeded a 1 MiB output limit and came back empty; they are now capped below it. A transcript whose first line hides its entrypoint past the first 4 KB (the same image) is now still recognised