GitHub Codespaces logs - GitHub Docs Skip to main content GitHub Docs Version: Free, Pro, & Team Search or ask Copilot Search or ask Copilot Select language: current language is English Search or ask Copilot Search or ask Copilot Open menu Collapse sidebar Expand sidebar Scroll breadcrumbs left * Home * Codespaces * Troubleshooting * Codespaces logs Scroll breadcrumbs right Codespaces * * * Quickstart * Getting started * What are Codespaces? * Codespaces features * The codespace lifecycle * Deep dive into Codespaces * Developing in a codespace * Develop in a codespace * Create a codespace for a repo * Create a codespace from a template * Delete a codespace * Open an existing codespace * Work collaboratively * Source control * Pull requests * Stop a codespace * Forward ports * Rebuilding a container * Default environment variables * Persist variables and files * Connecting to a private network * Machine learning * Visual Studio Code * GitHub CLI * Customizing your codespace * Rename a codespace * Change your shell * Change the machine type * Setting your user preferences * Personalize your codespaces * Set the default editor * Set the default region * Set the timeout * Configure automatic deletion * Choose the host image * Setting up your project * Adding a dev container configuration * Introduction to dev containers * Setting up a Node.js project * Setting up a C# (.NET) project * Setting up a Java project * Setting up a PHP project * Setting up a Python project * Configuring dev containers * Set a minimum machine spec * Adding features * Automatically opening files * Specifying recommended secrets * Setting up your repository * Facilitating codespace creation * Set up a template repo * Prebuilding your codespaces * About prebuilds * Configure prebuilds * Allow external repo access * Manage prebuilds * Test dev container changes * Managing your codespaces * Codespaces secrets * Repository access * Security logs * GPG verification * Managing your organization * Enable or disable Codespaces * Billing and ownership * List organization codespaces * Manage Codespaces costs * Manage secrets * Audit logs * Restrict machine types * Restrict codespace creation * Restrict base image * Restrict port visibility * Restrict timeout periods * Restrict the retention period * Reference * Access a private registry * Copilot in Codespaces * VS Code Command Palette * Security in Codespaces * Disaster recovery * Troubleshooting * Codespaces logs * Codespaces clients * Included usage * Exporting changes * Creation and deletion * Authenticating to repositories * Connection * Codespaces prebuilds * Personalization * Port forwarding * GPG verification * Working with support * github.dev editor GitHub Codespaces logs Overview of the logs used by GitHub Codespaces. Tool navigation * Visual Studio Code * GitHub CLI * Web browser Copy as Markdown In this article * Codespace logs * Codespace logs * Codespace logs * Creation logs * Extension logs * Browser console logs * Further reading Information on GitHub Codespaces is output to various logs: * Codespace logs * Creation logs * Browser console logs (for the VS Code web client) Extension logs are available if you are using GitHub Codespaces in VS Code. Click the "Visual Studio Code" tab above for details. * Codespace logs * Creation logs * Extension logs (for the VS Code desktop application) Browser logs are available if you are using GitHub Codespaces in your browser. Click the "Web browser" tab above for details. * Codespace logs * Creation logs Other logs are available if you are using GitHub Codespaces in VS Code or in your web browser. Click the tabs above for details. Codespace logs These logs contain detailed information about the codespace, the container, the session, and the VS Code environment. They are useful for diagnosing connection issues and other unexpected behavior. For example, the codespace freezes but the "Reload Windows" option unfreezes it for a few minutes, or you are randomly disconnected from the codespace but able to reconnect immediately. * If you are using GitHub Codespaces in the browser, ensure that you are connected to the codespace you want to debug. * Open the VS Code Command Palette ( Shift + Command + P (Mac) / Ctrl + Shift + P (Windows/Linux)) and type export logs . Select Codespaces: Export Logs from the list to download the logs. * Define where to save the zip archive of logs then click Save (desktop) or click OK (web). * If you are using GitHub Codespaces in the browser, right-click on the zip archive of logs from the Explorer view and select Download… to download them to your local machine. Codespace logs These logs contain detailed information about the codespace, the container, the session, and the VS Code environment. They are useful for diagnosing connection issues and other unexpected behavior. For example, the codespace freezes but the "Reload Windows" option unfreezes it for a few minutes, or you are randomly disconnected from the codespace but able to reconnect immediately. * Open the VS Code Command Palette ( Shift + Command + P (Mac) / Ctrl + Shift + P (Windows/Linux)) and type export log . Select Codespaces: Export Logs from the list to download the logs. * Define where to save the zip archive of logs then click Save (desktop) or click OK (web). Codespace logs These logs contain detailed information about the codespace, the container, the session, and the VS Code environment. They are useful for diagnosing connection issues and other unexpected behavior. For example, the codespace freezes but the "Reload Windows" option unfreezes it for a few minutes, or you are randomly disconnected from the codespace but able to reconnect immediately. Currently you can't use GitHub CLI to access these logs. To access them, open your codespace in VS Code or in a browser. Creation logs These logs contain information about the container, dev container, and their configuration. They are useful for debugging configuration and setup problems. * Connect to the codespace you want to debug. * Open the VS Code Command Palette ( Shift + Command + P (Mac) / Ctrl + Shift + P (Windows/Linux)) and type creation log . Select Codespaces: View Creation Log from the list to open the creation.log file. If you want to share the log with support, you can copy the text from the creation log into a text editor and save the file locally. Open the VS Code Command Palette ( Shift + Command + P (Mac) / Ctrl + Shift + P (Windows/Linux)) and type creation log . Select Codespaces: View Creation Log from the list to open the creation.log file. If you want to share the log with support, you can copy the text from the creation log into a text editor and save the file locally. Note To learn more about GitHub CLI, see About GitHub CLI . To see the creation log use the gh codespace logs subcommand. After entering the command choose from the list of codespaces that's displayed. gh codespace logs For more information about this command, see the GitHub CLI manual . If you want to share the log with support, you can save the output to a file: gh codespace logs -c <CODESPACE-NAME> > /path/to/logs.txt Extension logs These logs are available for VS Code desktop users only. They are useful if it seems like the GitHub Codespaces extension or VS Code editor are having issues that prevent creation or connection. * In VS Code, open the Command Palette. * Type logs and select Developer: Open Extension Logs Folder . * Your system's file explorer is displayed showing various log files and folders. Open the folder output_logging_DATETIME . From this view, you can access logs generated by extensions you use in VS Code, including GitHub Codespaces. Browser console logs These logs are useful only if you want to debug problems with using GitHub Codespaces in the browser. They are useful for debugging problems creating and connecting to GitHub Codespaces. The following instructions are for Chrome. The steps for other browsers are similar. * In the browser window for the codespace you want to debug, open the developer tools window. * Click the Console tab. * Show the console sidebar, if it is not already displayed. For more information, see Console features reference in the Chrome for Developers documentation. * In the sidebar, click NUMBER errors to show only the errors. * In the log area on the right, right-click and select Save as to save a copy of the errors to your local machine. Further reading * Reviewing your organization's audit logs for GitHub Codespaces * Reviewing your security logs for GitHub Codespaces Back to top Help and support Was this Doc helpful? Yes No Help us make GitHub Docs great! All Docs are open source. See something that's wrong or unclear? Submit a pull request. Make a contribution Still need help? Provide GitHub Feedback Contact support Expert services Blog GitHub Inc. © 2026 Terms Privacy Status Pricing