Cursor Watch posted an update
Cursor is investigating a service degradation affecting its VS Code extensions, according to the company’s status page, which marked the incident active on 29 October at 21:38 UTC.
Why it mattersThe notice does not specify which extension features are affected or how many users are involved. If your Cursor setup is acting oddly inside VS Code, this is a useful lead, though not yet a diagnosis.
Discuss: What should a service-status notice spell out first: the affected features, the number of users, or an estimated fix time?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.