Panes (terminal windows) are super critical to a workflow.
Accidentally closing one because you pressed cmd-w one too many times is super disruptive.
That might mean spending an annoying amount of time spelunking claude --resume to find some long-running convo that is dozens of rows deep into history.
While I have only closed an important pane very rarely, I often think about the precariousness when I have a lot of important panes/tasks running. It also makes every cmd-w feel risky. Do I have the right pane selected?
A recently closed panes list might be helpful much like recently closed tabs list in a web browser and then ability to "unclose" a tab. Of course, in danterm, the closed pane wouldn't have any processed running for it anymore -- it would behave like normal session recovery where you get back the last N rows of scrollback and the last command that you ran before you closed it. Maybe even Cmd-Z would work for reviving closed panes?
Panes (terminal windows) are super critical to a workflow.
Accidentally closing one because you pressed cmd-w one too many times is super disruptive.
That might mean spending an annoying amount of time spelunking
claude --resumeto find some long-running convo that is dozens of rows deep into history.While I have only closed an important pane very rarely, I often think about the precariousness when I have a lot of important panes/tasks running. It also makes every cmd-w feel risky. Do I have the right pane selected?
A recently closed panes list might be helpful much like recently closed tabs list in a web browser and then ability to "unclose" a tab. Of course, in danterm, the closed pane wouldn't have any processed running for it anymore -- it would behave like normal session recovery where you get back the last N rows of scrollback and the last command that you ran before you closed it. Maybe even Cmd-Z would work for reviving closed panes?