Skip to main content

The web-based editor

Use the web-based editor from your repository or pull request to create and commit changes.

Note: The web-based editor is currently in beta preview. You can provide feedback in our Discussions.

About the web-based editor

The web-based editor introduces a lightweight editing experience that runs entirely in your browser. With the web-based editor, you can navigate files and source code repositories from GitHub, and make and commit code changes. You can open any repository, fork, or pull request in the editor.

The web-based editor is available to everyone for free on

The web-based editor provides many of the benefits of Visual Studio Code, such as search, syntax highlighting, and a source control view. You can also use Settings Sync to share your own VS Code settings with the editor. For more information, see "Settings Sync" in the VS Code documentation.

The web-based editor runs entirely in your browser’s sandbox. The editor doesn’t clone the repository, but instead uses the GitHub Repositories extension to carry out most of the functionality that you will use. Your work is saved in the browser’s local storage until you commit it. You should commit your changes regularly to ensure that they're always accessible.

You must be signed in to use the web-based editor.

Opening the web-based editor

You can open any GitHub repository in the web-based editor in either of the following ways:

  • To open the repository in the same browser tab, press . while browsing any repository or pull request on GitHub.

    To open the repository in a new browser tab, press >.

  • Change the URL from "" to "".

  • When viewing a file, use the dropdown menu next to and select Open in

    Edit file button dropdown menu

Codespaces and the web-based editor

Both the web-based editor and GitHub Codespaces allow you to edit your code straight from your repository. However, both have slightly different benefits, depending on your use case.

web-based editorGitHub Codespaces
CostFree.Costs for compute and storage. For information on pricing, see "About billing for GitHub Codespaces."
AvailabilityAvailable to everyone on for organizations using GitHub Team or GitHub Enterprise Cloud.
Start upThe web-based editor opens instantly with a key-press and you can start using it right away, without having to wait for additional configuration or installation.When you create or resume a codespace, the codespace is assigned a VM and the container is configured based on the contents of a devcontainer.json file. This set up may take a few minutes to create the environment. For more information, see "Creating a Codespace."
ComputeThere is no associated compute, so you won’t be able to build and run your code or use the integrated terminal.With GitHub Codespaces, you get the power of dedicated VM on which you can run and debug your application.
Terminal accessNone.GitHub Codespaces provides a common set of tools by default, meaning that you can use the Terminal exactly as you would in your local environment.
ExtensionsOnly a subset of extensions that can run in the web will appear in the Extensions View and can be installed. For more information, see "Using extensions."With GitHub Codespaces, you can use most extensions from the Visual Studio Code Marketplace.

Continue working on Codespaces

You can start your workflow in the web-based editor and continue working on a codespace, provided you have access to GitHub Codespaces. If you try to access the Run and Debug View or the Terminal, you'll be notified that they are not available in the web-based editor.

To continue your work in a codespace, click Continue Working on… and select Create New Codespace to create a codespace on your current branch. Before you choose this option, you must commit any changes.

A screenshot that shows the "Continue Working on" button in the UI

Using source control

When you use the web-based editor, all actions are managed through the Source Control View, which is located in the Activity Bar on the left hand side. For more information on the Source Control View, see "Version Control" in the VS Code documentation.

Because the web-based editor uses the GitHub Repositories extension to power its functionality, you can switch branches without needing to stash changes. For more information, see "GitHub Repositories" in the VS Code documentation.

Create a new branch

  1. Si la rama actual no se muestra en la barra de estado, en la parte inferior de tu codespace, haga clic derecho en la barra de estado y seleccione Source control (Control de código fuente).
  2. Haz clic en el nombre de rama en la barra de estado. La rama en la barra de estado
  3. En el menú desplegable, haga clic en la rama a la que quiera cambiar o indique el nombre de una rama nueva y haga clic en Create nre branch (Crear rama). Elección en el menú de la rama Any uncommitted changes you have made in your old branch will be available on your new branch.

Commit your changes

  1. En la barra de actividad, haga clic en la vista Control de código fuente. Vista de control de código fuente
  2. Para agregar los cambios al "stage", haga clic en + junto al archivo que ha cambiado, o junto a Cambios si ha cambiado varios archivos y quiere agregarlos todos. Barra lateral de control de código fuente con el botón de almacenamiento provisional resaltado
  3. Teclea un mensaje de confirmación que describa el cambio que hiciste. Barra de control de código fuente con un mensaje de confirmación
  4. Para confirmar tus cambios planeados, haz clic en la marca de verificación en la parte superior de la barra lateral del control de código fuente. Clic en el icono de marca de verificación
  5. Once you have committed your changes, they will automatically be pushed to your branch on GitHub.

Create a pull request

  1. Después de haber confirmado los cambios en la copia local del repositorio, haga clic en el icono Create Pull Request. Barra lateral de control de código fuente con el botón de almacenamiento provisional resaltado
  2. Verifica que el repositorio y la rama local desde la que estás haciendo la fusión y la rama y repositorio remotos hacia los que estés haciendo la fusión sean correctos. Después, asigna un nombre y descripción a la solicitud de cambios. Barra lateral de control de código fuente con el botón de almacenamiento provisional resaltado
  3. Haga clic en Crear.

Working with an existing pull request

You can use the web-based editor to work with an existing pull request.

  1. Browse to the pull request you'd like to open in the web-based editor.
  2. Press . to open the pull request in the web-based editor.
  3. Once you have made any changes, commit them using the steps in Commit your changes. Your changes will be committed directly to the branch, it's not necessary to push the changes.

Using extensions

The web-based editor supports VS Code extensions that have been specifically created or updated to run in the web. These extensions are known as "web extensions". To learn how you can create a web extension or update your existing extension to work for the web, see "Web extensions" in the VS Code documentation.

Extensions that can run in the web-based editor will appear in the Extensions View and can be installed. If you use Settings Sync, any compatible extensions are also installed automatically. For information, see "Settings Sync" in the VS Code documentation.


If you have issues opening the web-based editor, try the following:

  • Make sure you are signed in to GitHub.
  • Disable any ad blockers.
  • Use a non-incognito window in your browser to open the web-based editor.

Known limitations

  • The web-based editor is currently supported in Chrome (and various other Chromium-based browsers), Edge, Firefox, and Safari. We recommend that you use the latest versions of these browsers.
  • Some keybindings may not work, depending on the browser you are using. These keybinding limitations are documented in the "Known limitations and adaptations" section of the VS Code documentation.
  • . may not work to open the web-based editor according to your local keyboard layout. In that case, you can open any GitHub repository in the web-based editor by changing the URL from to