[Desktop] Session info panel (Environment card) can't be hidden and wastes width in split view (2.37337.1)

Status Open
Maintainer reply None cached
Activity 1 comment · opened Oct 15, 2026

Environment

  • Claude Desktop 2.37337.1 (Microsoft Store / MSIX), Windows 11 Pro
  • Code tab, split view with two local sessions

What changed

After the 2.37337.1 update (2026-10-13), each Code session shows a new side panel with an "Environment" card (plus Context and Connectors cards). The 2.37337.1 changelog doesn't mention this layout change.

Problem

  1. The Environment card can't be removed. The Context and Connectors cards can be removed, but the Environment card stays.
  2. The panel can't be collapsed. Clicking the panel's toolbar toggle doesn't hide it, and there's no setting for it.
  3. Split view loses usable width. In split view, each session's panel takes roughly a third of its pane. Most of that space is empty, because the panel holds only one small card. The conversation column gets squeezed into a narrow strip.
  4. Mods can't fix it. RenderComponent covers transcript components, AbovePrompt and Pane, but not the session info panel or the desktop layout. Users have no way to customize this area.

Steps to reproduce

  1. Update to 2.37337.1.
  2. Open two Code sessions in split view.
  3. Remove the Context and Connectors cards from the side panel.
  4. Try to hide the remaining Environment card or collapse the panel.

Expected: The panel can be collapsed or hidden, or it gives its width back to the conversation when it holds nothing useful.
Actual: The panel stays open with one card and a large blank area in each split pane.

Requests (any of these would solve it)

  • A setting to hide the session info panel by default
  • A working collapse toggle that the app remembers per session or globally
  • Allow removing the Environment card like the other cards
  • Expose the panel to mods via ui.render

Screenshot

(Screenshot will be added in a comment below.)

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗