Extension agent panels cannot be docked in the secondary sidebar (reserved for Cursor Agent), leaving them stacked under the Explorer

Support Bug Reports
,
6

Hi @Jeremy.Chambers Thanks for the post! I double-checked this against Cursor 3.20.10 and Claude Code 2.1.266.

There are three separate behaviors here:

  1. Claude Code cannot register its own container directly inside Cursor’s Agent tab group. That restriction is intentional and is the behavior discussed in this thread.
  2. With the default horizontal Activity Bar, dragging the Claude Code panel toward the Secondary Side Bar does not initiate a cross-sidebar move. The lack of any feedback when that drag is rejected is a separate issue.
  3. View: Move View is different from dragging. It can move the individual Claude Code view into its own Secondary Side Bar entry, separate from Cursor’s Agent tab group.

For the Claude Code panel currently under Explorer, the exact path is:

  1. Run View: Move View.
  2. Select Claude Code under Side Bar / Explorer.
  3. Select New Secondary Side Bar Entry.

A completed move should open Claude Code on the right immediately and preserve that location across restarts. It will be a separate Secondary Side Bar entry, not a tab inside Cursor’s Agent group. Cursor may also switch its Agent area out of chat editor-tab mode while the extension view occupies that sidebar. That is expected compatibility behavior.

One useful clue is that your views.customizations snapshot is empty. A completed move would record both the moved view and its generated Secondary Side Bar container there. That means the snapshot does not show a successfully moved but hidden view. It shows that no custom move was persisted at the time of capture.

If the exact steps above still produce no visible change and views.customizations remains empty, please run Capture and Send Debugging Data immediately afterward and let me know when it completes. That would confirm a separate issue with the move command rather than the intentional Agent-tab restriction.

Your editor-group workaround is also valid and remains a good alternative when you want Claude Code beside your code without changing the Agent pane layout.