Wrong error message when remote AH is not available
Open
agent-host
- Dominant language
- TypeScript
- Stars
- 193k
- Forks
- 42.4k
- PR merge metrics
- PR metrics pending
Description
1. open window on a remote machine (dev box) and allow remote connections)
2. start a chat from your local machine with that remote
3. update the remote machine (remote access turns off, sometimes)
4. reopen the remote chat from your local machine
:bug: error about legacy chat not being compatible
turning remote access back on fixes it, but this looks like the update broke my session.
Contributor guide
Assessment
This issue has not been assessed yet.