Appshot ‘Current chat’ routes to a new ChatGPT Work conversation
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Description
Appshot routes captures to a new conversation in ChatGPT Work even when the Appshot destination is explicitly set to Current chat.
Environment
- ChatGPT desktop app: 26.915.31945 (build 9922)
- macOS: 26.6.2
- Appshot shortcut: Double Command
- Screen & System Audio Recording permission: enabled
- Accessibility permission: enabled
The app was updated from build 8576 to build 9922 and fully restarted. The issue still reproduces after the update and restart.
Steps to reproduce
- Open an existing ChatGPT conversation.
- Set Appshot destination to Current chat.
- Bring another application, such as Chrome or VS Code, to the foreground.
- Press the Appshot shortcut (Double Command).
- Observe where the captured screenshot is attached.
Expected result
The Appshot should be attached to the conversation that was open before switching to the other application.
Actual result
The app opens or selects a new conversation in ChatGPT Work and attaches the Appshot there.
Relevant diagnostics
Capture and permissions succeed. The failure occurs during destination routing:
Appshot hotkey pressed hotkey=DoubleCommand
Dispatching appshot hotkey destination=last-chat target=new-chat
Appshot shortcut composer routing activeComposerId=new-conversation
Appshot capture settled hadAxText=true hadScreenshot=true status=success
This also occurred immediately after an existing /c/... conversation route became active. The app correctly reads the Current chat preference as destination=last-chat, but resolves it to target=new-chat.
Frequency
Consistently reproducible across multiple attempts and after a full application restart.
Workaround
Using the screenshot option from the existing conversation’s + menu instead of the global Appshot shortcut.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start from the Appshot hotkey dispatch and destination-routing path described in the diagnostics, reproducing the Double Command shortcut with an existing ChatGPT conversation open before switching apps. Trace why destination=last-chat resolves to target=new-chat; done means the capture attaches to the previously active conversation, with the existing reproduction steps passing consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100