{"version":"2.1.281","anchor":"pane-placement-explains-when-no-attached-surface-can-place-p","canonical_anchor":"pane-placement-explains-when-no-attached-surface-can-place-p","heading":"Pane placement explains when no attached surface can place panes","tier":"internal","area":"Terminal UI","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/pane-placement-explains-when-no-attached-surface-can-place-p","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Pane placement explains when no attached surface can place panes\n\nClaude Code can now report that panes aren't placed because no attached client is fullscreen, naming those clients\n\n**Unclear.** The finding does not say what panes and attached surfaces are here or where the reason is shown.\n\n**What**\n\nNew logic reports whether panes are placed. If the attached clients have views but none of them reports being fullscreen, it says panes are not placed and gives a reason naming those clients.\n\n**Why**\n\nIt gives an explanation for why panes did not appear, instead of leaving you to guess.\n\n- Area: Terminal UI\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}