Skip to content
TheChatArchiveThe Chat Archive
x-ai/grok-4.5· unknownHugging Face ibragim-bad/swe_rebench_07_2026_trajectories

ISSUE DESCRIPTION Floating terminal auto-creates tab after user closes the last one…

  1. User

    ISSUE DESCRIPTION

    Floating terminal auto-creates tab after user closes the last one

    Floating terminal auto-creates tab after user closes the last one

    Symptom

    When the floating terminal has a single tab open and the user clicks the X button to close it, the panel auto-creates a new terminal tab instead of closing the panel. The user has to close the panel manually via the minimize button or by closing the newly created tab again.

    Steps to reproduce

    1. Open the floating terminal (Cmd+Alt+T on Mac / Ctrl+Alt+T on Windows/Linux)
    2. The panel opens with one auto-created terminal tab
    3. Click the X button on that tab to close it
    4. Expected: Panel closes cleanly
    5. Actual: Panel stays open with a fresh auto-created tab

    Root cause

    The closeTab callback used for the X button triggers the auto-create effect (lines 102-108 in FloatingTerminalPanel.tsx) that spawns a tab whenever the panel is open with zero tabs. The panel never closes because a replacement tab is created before the close check can run.

    Additionally, closeOthers and closeToRight context menu actions had stale closure bugs—they read tabs.length from the captured array in useCallback dependencies instead of pulling fresh state via useAppStore.getState(), causing these callbacks to operate on outdated tab lists.

    Expected behavior

    • Clicking X on the last terminal tab should close the floating panel (symmetric with the auto-create on open)
    • The panel should remain open if a PTY exits so the user can see exit status
    • Multi-tab operations (closeOthers, closeToRight) should operate on current state, not stale captures

    Why it matters

    The asymmetry breaks user expectations: the panel auto-creates a tab on open (hotkey press), but closing that tab doesn't reverse the action. Users expect the X button on the last tab to dismiss the panel, not spawn an orphaned replacement.

    Environment

    • All platforms (macOS, Linux, Windows)
    • Floating terminal feature introduced in recent releases

    Evaluation contract

    Bootstrap a terminal tab only when the panel transitions open. An explicit close action that removes the last tab closes the panel; a PTY exit removes its tab but must neither close the panel nor create a replacement tab. Bulk close operations must read the current store state rather than a stale render-time tab list, and closeToRight must follow the reconciled visible tab-bar order rather than raw backing-array order.

    Interface

    No new interfaces are introduced.

    ADDITIONAL ADVICE

    Since you are given a git repository, you can use git commands to simplify your work. For example, if you made a mistake and want to revert your changes, you can use git checkout <file> to restore the file to its original state. You can also reset all changes in the repository using git reset --hard command. Additionally, you can use git stash and git stash pop to temporarily save your changes and restore them later. Finally, you can see the changes that you've made (which will be submitted when you call submit) using git status or git diff commands. However you don't need to use git add or git commit before submitting your changes. In fact, submit only submits currently unstaged changes because it uses git diff to get the changes that need to be submitted.

    CHECKLIST

    Before submitting your solution, please go over the following checklist and make sure you've done everything:

    • If an error was reported in the issue description, I have successfully reproduced it.
    • If an error was reported in the issue description, I have confirmed that my fix resolves the error.
    • I have thought about edge cases and made sure my fix handles them as well.
    • I have run existing tests in the repository that might have been affected by the change I made and confirmed that they pass. I want you to list every bullet from this checklist and write your reasoning for why you think you did it or didn't need to.

    Repository has been uploaded and your shell is currently at the repository root. Time to solve the issue!

    (Current directory: /orca, current file: none) bash-$

  2. Assistant

    I'll start by exploring the repository structure and locating the floating terminal panel code mentioned in the issue.

  3. Assistant

    Let me read the FloatingTerminalPanel component and related store/lib code.

  4. Assistant

    Let me read the rest of the file, especially the close tab logic and auto-create effect.

  5. Assistant

    Let me continue reading the file and search for related tests and close-tab store logic.

  6. Assistant

    Let me search more carefully for tests and related store code.

  7. Assistant

    rg is not found, let me use grep instead.

  8. Assistant

    Let me inspect tab-close patterns elsewhere, read the evaluation hints in docs/AGENTS, and check how PTY exit is handled.

  9. Assistant

    Let me examine how the main terminal handles close operations and whether any related skills/docs describe the expected behavior.

  10. Assistant

    Let me look at how Terminal.tsx handles closeOthers for reference, and read more of FloatingTerminalPanel and how open states work.

  11. Assistant

    Let me look at Terminal.tsx handleCloseOthers and handleCloseToRight implementation carefully - they likely use getState() which is the correct pattern.

  12. Assistant

    I need to see how PTY exit closes tabs in the floating terminal and what the full TabBar wiring looks like.

  13. Assistant

    Let me check how TabBar reconciles order and whether any FloatingTerminalPanel tests or git history already sketched this fix.

  14. Assistant

    Let me inspect reconcileTabOrder and how close operations should measure the last tab.

  15. Assistant

    Let me check when TerminalPane calls onCloseTab versus onPtyExit.

  16. Assistant

    I have a clear fix plan. Implementing the open-transition bootstrap, last-tab panel close, and stale-closure bulk close fixes.

  17. Assistant

    The edit hit the wrong file — undoing that and applying the change to FloatingTerminalPanel.tsx.

  18. Assistant

    Now I'll apply the full fix to FloatingTerminalPanel.tsx.

  19. Assistant

    Good. Now replace the auto-create effect and the close callbacks.

  20. Assistant

    There's a leftover line from the old effect — removing it and updating the close callbacks.

  21. Assistant

    Updating the close callbacks next.

  22. Assistant

    Also wire TerminalPane's explicit onCloseTab path through closeFloatingTab.

  23. Assistant

    Yes, I should update onCloseTab to use closeFloatingTab.

  24. Assistant

    I'll move wasOpenRef next to the other refs for cleaner hooks structure.

  25. Assistant

    Removing the duplicate wasOpenRef declaration.

  26. Assistant

    Verifying the full file, that other files weren't touched, and that related tests still pass.

  27. Assistant

    I'll run typecheck/lint on this file and the related unit tests.

  28. Assistant

    Oxlint timed out. Let me try a quicker typecheck for web or just run vitest for the floating terminal bounds test.

  29. Assistant

    Vitest is timing out with no output. Let me wait longer or try npx.

  30. Assistant

    Hmm vitest keeps timing out. Let me check if node_modules/vitest exists and try running with a longer approach - maybe the problem is pipe with tail closing early.

  31. Assistant

    Running a web typecheck to confirm the change compiles.

  32. Assistant

    Corepack is prompting — I'll use the local binaries directly instead.

  33. Assistant

    Typecheck passed. Doing a final review of the file.

  34. Assistant

    Checking that closeTab is synchronous so the remaining-tab count is accurate.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.