# Debug with Cloud Shell Editor

> [!NOTE]
> **Note:** Debugging support is available for Go, Node.js, Python, Java, and Ruby applications.

Cloud Shell Editor lets you debug your application. With the editor's
debugging support, you skip manual setup such as configuring port forwarding or
injecting language-specific debug arguments. You can create launch
configurations, set breakpoints, and inspect variables, all in the editor.

## Debug actions

To access the Cloud Shell Editor's debugging support, click
![Debug View icon](https://docs.cloud.google.com/static/shell/docs/images/debug-icon-cs.png) **Debug** in the
Activity bar. Sample applications come with a `launch.json` file needed to run
and debug your application. If your application doesn't have one, you're
prompted in the Debug View to create one.

In the Debug View, start a debugging session by clicking
![Start Debugging icon](https://docs.cloud.google.com/static/code/docs/vscode/images/debugdropdown.png) **Start**.
When prompted, choose the context to run your app in and, if applicable, the
image registry to use.

After your debugging session starts, you can manage it with the Debugging action
icons: Pause, Step over, Step in, Step out, Restart, Stop.

![Debugging start icon along with pause, step over, step in, step out, restart, and stop icons](https://docs.cloud.google.com/static/shell/docs/images/debug-actions.png)

## Set breakpoints

To set or toggle breakpoints, click in the editor margin next to the line you
want to break at. Red circles are active breakpoints and gray circles
are inactive breakpoints. If a breakpoint can't be registered with
the debugger when a session starts, it changes to a gray-outlined hollow circle.

![Setting a breakpoint at line 45](https://docs.cloud.google.com/static/shell/docs/images/setting-breakpoints.png)

When running a debugging session, the app stops at the breakpoint and you can
inspect the Variables panel in the Debug View to inspect variable values as the
app is paused.

![Debugging session showing app paused at breakpoint and variable values in scope](https://docs.cloud.google.com/static/code/docs/vscode/images/quickstart-debug-breakpoints.png)

## Additional Kubernetes debugging support

With the Cloud Shell Editor, you can debug Kubernetes applications on
a local cluster (like minikube or Docker Desktop) or a remote cluster on
GKE or any other Cloud provider. You can also attach a
debugger to a Kubernetes pod.

Refer to the [Debugging Kubernetes applications](https://docs.cloud.google.com/code/docs/shell/debug.md.txt)
using the Cloud Shell Editor guide for more details.