gh-codespace

You can manage GitHub Codespaces from the terminal by using the `gh codespace` command to securely connect to, create, edit, and delete development environments without leaving your local CLI.

To transfer files between a GitHub Codespace and your local machine, use the `gh codespace cp` command, which allows you to move artifacts directly without setting up manual SCP configurations.

Your GitHub Codespace CLI connection hangs during automation because interactive commands are being attempted in non-interactive sessions, or you are connecting to stopped environments; use status checks and avoid interactive flags.

Yes, you can forward ports for local testing using GitHub Codespaces CLI, which manages port forwarding to route remote development environment traffic directly to your local machine.

The best way to troubleshoot a failing GitHub Codespace is to use the `gh codespace logs` command, which retrieves remote environment logs directly to your terminal for basic issue diagnosis.

Yes, you need to check codespace status before rebuilding via GitHub CLI to prevent connection attempts against stopped or rebuilding environments, ensuring safe automation and avoiding lifecycle failures.