[BUG] Desktop: Claude Code window pane layout doesn't persist between sessions

Resolved 💬 2 comments Opened Jun 11, 2026 by stevetme Closed Jun 15, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Environment

  • Claude desktop app v1.11847.5 (com.anthropic.claudefordesktop)
  • macOS 26.5.1
  • Running Claude Code inside a Claude Code window (panes: terminal, diff, preview, chat)

What happens
Every new Claude Code session/window opens with the default pane layout. The
arrangement I set (pane positions/sizes, sidebar, which panes are open) does not
carry over. I have to re-drag the panes every session.

What Should Happen?

Expected
A layout I set should persist across sessions — ideally a way to save/lock one
default layout that every new Code window opens with.

What I found (Local Storage)
The app does write layout state to persistent Local Storage keys
desktop-frame.paneStore.v1, sidePaneStore.v1, and tileLayout — but it
appears to keep only the last-used state, not a default that's reliably restored
on a new session. Window size/position also isn't persisted (no window-bounds
entry in the app's Preferences file).

Ask
Persist pane layout (and window size) across sessions, and/or add a
"save as default layout" option that applies to all new Code windows.

Error Messages/Logs

Steps to Reproduce

Repro

  1. Open a Claude Code window, rearrange/resize the panes.
  2. Start a new session (or close and reopen).
  3. Layout is back to default.

Claude Model

Not sure / Multiple models

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

v1.11847.5 — the Claude desktop app (com.anthropic.claudefordesktop) on your Mac.

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗