Failed Vision bricks session
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
Attempting to use Vision when it's not enabled (both by the model and my org) bricks my conversation causing me to lose the session history. All subsequent prompts after a failed vision attempt produce the below.
As this was in the desktop, there does not appear to be a rewind (escape-escape) feature available here. That could reset the session to before image files were added.
Execution failed: CAPIError: 400 {"error":{"code":"bad_request","type":"websocket_error","message":"vision is not enabled for this user or integration (model \"gpt-5.5\")"}} (Request ID: 00000-d13499b6-dfcf-484e-a57f-8cd77e4ebf72)
---
| Field | Value |
| --- | --- |
| App version | 1.0.10 |
| OS | Windows 10.0.26200 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Day 7 (Week 1) |
Contributor guide
Research direction
Start in the desktop app's /chat flow and reproduce the failure by attempting Vision when it is disabled for the model and organization. Check how the CAPIError websocket error affects subsequent prompts and session history; done means the conversation remains usable after the failed attempt without losing its history.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100