# Extension Host navigator.userAgent doesn't match renderer process, breaking VS Code extension compatibility

**URL:** <https://forum.cursor.com/t/extension-host-navigator-useragent-doesnt-match-renderer-process-breaking-vs-code-extension-compatibility/148095>\
**Category:** Bug Reports\
**Tags:** java\
**Created:** [January 6, 2026, 10:21am UTC](https://forum.cursor.com/t/extension-host-navigator-useragent-doesnt-match-renderer-process-breaking-vs-code-extension-compatibility/148095 "2026-01-06T10:21:17Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![jason419](https://avatars.discourse-cdn.com/v4/letter/j/f0a364/32.png) [@jason419](https://forum.cursor.com/u/jason419)\
**Post date:** [January 13, 2026, 11:23pm UTC](https://forum.cursor.com/t/extension-host-navigator-useragent-doesnt-match-renderer-process-breaking-vs-code-extension-compatibility/148095/7 "2026-01-13T23:23:42Z")

</div>

Is this any update on this? I’m the original poster of thread linked to on this thread. It has been months since the issue was reported. My workaround was to continue using an older version of cursor that didn’t have this issue. Now that old cursor version will no longer interact with AI models and forces an update. So, I have no work around.

---

_[View the full topic](https://forum.cursor.com/t/extension-host-navigator-useragent-doesnt-match-renderer-process-breaking-vs-code-extension-compatibility/148095)._