AI generated
Sorry for the incoming AI slop, but this might be helpful for anyone else wondering what the issue is. For context, at the top of each session/chat you could click the name and then click open in and it had options for file explorer and your IDEs. It was removed and the only way to get the behavior back I could find was this complicated hack: Title: Codex on Windows: opening a worktree in VS Code or Explorer is buried now—here’s a workaround I’m using the Codex/ChatGPT Windows desktop app, version 26.1111.21308, and the chat-title dropdown no longer offers the option I used to open the current worktree in VS Code or File Explorer. I initially thought the functionality had been removed completely. It’s still accessible through a folder’s breadcrumb menu in the file viewer, but getting there is unnecessarily cumbersome for something I use regularly. Here’s the workaround I confirmed: Open the chat associated with the worktree you want to inspect. Press Ctrl+Shift+E to open the Files tree. Open a file at the root of the worktree, such as README.md or AGENTS.md. In the file viewer’s header, right-click the folder name immediately before the filename. For example, in my-project > AGENTS.md, right-click my-project. Choose Open in VS Code, Open in Explorer, or Open with to select another application. The folder breadcrumb is the important part: its menu opens the directory represented there. Choose a root-level file so that the parent folder is the worktree you want. In my installation, right-clicking All files in the Files tree only produced a generic Select All menu. The breadcrumb menu was the route that worked. I’m glad there’s a workaround, but a three-key shortcut followed by several clicks is a lot of friction for “open the checkout I’m working in.” Opening the exact worktree in your own editor or file manager is a basic development workflow, especially when inspecting an agent’s changes. Please restore a direct Open worktree action in the chat header, or provide a dedicated configurable shortcut. There’s also an existing GitHub report about the missing working-directory opener. Has anyone found a shorter route in the current Windows interface?