I close a tab and want it straight back, but I have to find the file and my place in it again

[a-team-app]

Opportunity

I close a tab by mistake, or close one and realise a moment later I still needed it, and getting it back means finding the file again (Explorer or quick open) and then finding my place in it again: it usually reopens at line 1, with the scroll, cursor and any undo history gone. When I'm reading unfamiliar code or reviewing a PR I open and close a lot of tabs, so this happens several times a day, and each time it costs me my train of thought, not just the keystrokes.

Evidence

• TuiCode has no command for it. The nearest route is Previous cursor position (Ctrl+G P, gp), which reopens a closed file if a jump there was recorded, but only by walking back through every position in between, only to a recorded jump rather than where I left the cursor, and not at all once the last tab is closed (GoToHistory needs an open tab). Opening the file any other way starts at line 1.
• VS Code (Ctrl+Shift+T, Reopen Closed Editor) and JetBrains (Reopen Closed Tab) both treat this as basic, and it's the browser habit everyone already has.
• Zed users keep hitting its edges: discussion #38324 asks for Firefox-style reopen, and #45198, #52695 and #64191 are bugs where reopen closed item did nothing for some tabs — people notice when it's missing.
• Related but different: Reopening a folder drops me at line 1 of every file, so I lose my place #217 is losing my place across a folder reopen; this is within one session, seconds after closing.

Why it fits

• Familiar: a VS Code and JetBrains staple, and the browser shortcut people reach for without thinking.
• Daily-driver gaps (theme 1): a small rough edge that makes you slower all day.
• The vision's user spends most of their time navigating and reviewing code, which is exactly the open-close-open churn where this bites.
• Zed isn't named in the vision's products to learn from; it's a fair comparison here as a fast, keyboard-first editor.