GitHub's Clone button had grown into a menu of ways to open code in other tools. This proposal turns it into a configurable "Open with" launcher for the tools each developer actually uses.
0:00 / 4:37
Summary
Every repository on GitHub has a Clone button for getting the code onto your computer. "Clone" stopped describing the menu once it began opening code in desktop apps, workspaces, and editors. This proposal gives those destinations room to grow without turning the dropdown into a list of every integration GitHub supports.
Name the action for the outcome. “Open with” covers cloning, launching a local app, and opening the repository in a hosted workspace without forcing those behaviors into one misleading label.
Let developers choose their tools. An edit state controls which destinations appear in the menu, so someone who never downloads a ZIP can replace it with Visual Studio Code.
Support custom editors. Developers can name an app and provide its deep-link scheme, then edit or remove that integration later.
Keep clone transport as a preference. HTTPS, SSH, and GitHub CLI remain grouped in the familiar clone section rather than competing with destinations in the main menu.
Handle multi-step destinations in place. Options such as workspaces can take over the popover for their next step, then return to the main launcher without opening a separate flow.