Error message when switiching to deleted session

[tstorch]

Describe the bug

💡 Before filing, please check common issues:
https://block.github.io/goose/docs/troubleshooting

📦 To help us debug faster, attach your diagnostics zip if possible.
👉 How to capture it: https://block.github.io/goose/docs/troubleshooting/diagnostics-and-reporting/

A clear and concise description of what the bug is.

---

To Reproduce
Steps to reproduce the behavior:

1. Create a new Chat by clicking on 'Chat' in the sidemenu, enter some prompt/query and send it
2. Switch to History by clicking on 'History' in the sidemenu
3. Delete the latest session by clicking the red trash bin icon on the tile corresponding to the latest session and confirming in the model window/pop up
4. Switch back to Chat by clicking on 'Chat' in the sidemenu
5. See error

---

Expected behavior
A clear and concise description of what you expected to happen.

• Not crashing
• Probably a fresh session?

---

Screenshots
If applicable, add screenshots to help explain your problem.

---

Please provide the following information

• OS & Arch: MacOS 15.7.2 (24G325)
• Interface: UI
• Version: v1.13.1
• Extensions enabled: Chatrecall, Developer, Extension Manager, Knowledge Graph Memory, Memeory, Todo
• Provider & Model: [e.g. Google – gemini-1.5-pro]

---

Additional context

[sheikhlimon]

can confirm

[DOsinga]

yeah, that seems likely. as a workaround, you can just go to home and start a new session from the bottom there

[sheikhlimon]

i've been prompting for hours trying to fix it. so far i have found this happens because after deleting the session clicking on chat calls resumeSession looks for sessionId which go deleted

[DOsinga]

thanks for looking into it. we have a new version of this all coming up, that might make this moot. one way to fix this would be to change delete session in the server to not delete the session, but change the type to hidden. or even better, introduce a new type of session, deleted. that way we can make it possible to undelete a session. but it would mean that going back to the deleted session would just show you the same

if you call setChat with sessionId: '' after deleting the session it should work. You'd have to pass in the sessionId and setChat into the history though

[sheikhlimon]

thanks for looking into it. we have a new version of this all coming up, that might make this moot. one way to fix this would be to change delete session in the server to not delete the session, but change the type to hidden. or even better, introduce a new type of session, deleted. that way we can make it possible to undelete a session. but it would mean that going back to the deleted session would just show you the same

if you call setChat with sessionId: '' after deleting the session it should work. You'd have to pass in the sessionId and setChat into the history though

i have been trying various ways to fix it nothing seemed to work. but currently the error is gone but it still showing the deleted session in the chat. Let me look into what you suggested

[sheikhlimon]

@DOsinga When a session was deleted, multiple sources still contained the deleted session ID:

• chat.sessionId in chat state
• activeSessionId in App state
• sessionId in useAgent hook
• URL parameters

Fix:

• Added callback mechanism from SessionsList -> App -> Pair
• When session is deleted, clear ALL state sources:
  • Clear chat state
  • Clear App's activeSessionId
  • Clear useAgent's sessionId (via resetChat()`)
  • Clear URL parameters
  • Use localStorage as backup to prevent reuse during navigation

The frontend is now working perfectly - when you delete a session and return to Chat, the app correctly:

• Clears all old session state
• Asks for a new session with resume SessionId: undefined
• Prevents using deleted session IDs

Note: I'm still getting the same session ID after deletion, but this is now a backend issue - the backend is reusing deleted session IDs instead of creating completely new ones. The frontend is working correctly.

Edit: This was the first fix which wasn't working as it should. So after looking into it more deeply I have fixed it using a different approach. I'm gonna make a PR. But if you don't like the implementation feel free to close it.

[DOsinga]

thanks @sheikhlimon for fixing this!