# Cursor not loading source control, terminal, extensions

**URL:** <https://forum.cursor.com/t/cursor-not-loading-source-control-terminal-extensions/159177>\
**Category:** Bug Reports\
**Tags:** terminal, extensions\
**Created:** [April 27, 2026, 8:24pm UTC](https://forum.cursor.com/t/cursor-not-loading-source-control-terminal-extensions/159177 "2026-04-27T20:24:03Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\
**Post date:** [April 28, 2026, 12:29pm UTC](https://forum.cursor.com/t/cursor-not-loading-source-control-terminal-extensions/159177/7 "2026-04-28T12:29:58Z")

</div>

Hi @something_something

This is a known issue. The Extension Host sometimes fails to finish initializing on startup, which causes source control, terminal, and extensions to all fail to load. Our team is actively investigating it.

A workaround that has helped others is deleting the `workspaceStorage` folder – Cursor will regenerate it automatically. On macOS, the path is:

`~/Library/Application Support/Cursor/User/workspaceStorage`

You may also find this related thread helpful: [Nothing initialises include source control providers, output, extensions etc](https://forum.cursor.com/t/nothing-initialises-include-source-control-providers-output-extensions-etc/158970)

---

_[View the full topic](https://forum.cursor.com/t/cursor-not-loading-source-control-terminal-extensions/159177)._