Hey, thanks for the detailed report with the version and request ID. That helped us narrow it down quickly.
Based on the symptoms, this looks like a known bug. If the local agent gets interrupted, in your case by a system reboot, the saved state for that specific conversation can get corrupted. After that, any attempt to continue the same session, like clicking Try again or sending a new prompt in it, will hit the same error again. Your account is fine. The issue is tied to that one conversation, not all requests.
Workaround: start a new conversation using New Agent instead of continuing Dev server setup. The corruption is per conversation, so a fresh session should work. You can bring the context over by referencing the relevant files or plan, for example docs/EMBROIDERY-DR-PLAN-AMENDED.md.
We are already tracking the bug, but I can’t share an exact ETA for a fix yet. If you still see the error after starting a new conversation, message me with the new Request ID and we will dig deeper.
@Muhammad_Raza_Kanji I couldn’t find a way to send you a PM, so attached is a redacted version of your screenshot which you may wish to use to replace the screenshot in your original post (which contains some personal information).
