Need help with sublime_debugger?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

237 Stars 26 Forks MIT License 561 Commits 24 Opened issues


Graphical Debugger for Sublime Text using the debug adapter protocol

Services available


Need anything else?

Contributors list

Sublime Debugger

Graphical Debugger for sublime text for debuggers that support the debug adapter protocol.

See Debug Adapter Protocol

Image of GUI


Using package control run

Package Control: Install Package
and select

or clone into your sublime Packages directory (If you are on Sublime Text 3 use the st3 branch)

Getting Started

This project attempts to match Visual Studio Code's Debugger fairly closely so their documentation can be pretty helpful. See


This project comes with some pre-configured debuggers (They can be installed using

Debugger: Install adapter
  • See
  • See
  • See
  • For an overview see
  • See
  • For an overview see
  • See
  • For an overview see
  • See
  • See


  • Open the debug panel

    • from the command palette
      Debugger: Open
  • Install a debug adapter by running:

    Debugger: Install adapter
    from the command palette.
  • Add a configuration

    Debugger: Add Configuration
    from the command palette (or add one manually, see below).
    • Configurations are added to
      to your sublime-project and use the same configuration format as Visual Studio Code
    • Consult the debugger specific documentation links above for creating a configuration for your debugger. Most debuggers come with some configuration snippets to choose from but I highly recommend looking at the documentation for the debugger.
    • Variable substitution: variables like
      are supported but the list of supported variables differs from VSCode. The supported values are those listed at plus the VSCode-specific
      that resolves to the path of the first workspace folder.
  • Your configuration will look something like the following but with some debugger specific fields.

    "debugger_configurations" : [
        "name" : "Name of your configuration",
        "request" : "launch"|"attach",
        "type" : "debugger name",
  • Start debugging

    • click the gear icon to select a configuration to use
    • click the play icon to start the debugger or run
      Debugger: Start
      (if no configuration is selected it will ask you to select or create one)


Tasks are based on sublime buildsystems with more integration so they can be used more seamlessly while debugging. When errors occur while running a task they are reported in the debugger ui (problem detection is the same as sublime, you must add `fileregex` to your task)


Tasks are basically the same as sublime builds but there are a few additional parameters.

which will show up in the debugger ui and the be the name of the panel
"debugger_tasks" : [
        "name" : "Name of your configuration",
        "request" : "launch"|"attach",
        "type" : "debugger name",
  • Tasks can be run with
    Debugger: Run Tasks
  • You can run tasks before and after debugging by adding
    to your configuration specifiying the name of the task to run.


Settings can either be set at the project level or globally. Project settings can be changed by appending

to the setting name.

Within a

file -
Open the debugger automatically when a project that is set up for debugging has been opened -
scales the entire debugger UI

Within a

file settings object -

for a full list of settings see debugger.sublime-settings


  • Look in the debug console for errors (usually red)
  • Look in the sublime console for errors
  • Try the same configuration/adapter in Visual Studio Code (There is a good chance your issue is with the adapter so check out the outstanding issues for it)

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.