Documentation

Where your data is kept

Everything Debugt saves is on your machine, outside your repositories. Nothing about your services is uploaded.

One folder

Debugt keeps everything under ~/.debugt in your home folder. Set the DEBUGT_HOME environment variable to move it.

~/.debugt/
  settings.json                 your settings
  projects/
    <project>/                  one folder per project
      project.json              which repository it belongs to
      requests/                 saved requests, a folder per service
      history/                  Request History: one <id>.json per send — its request,
                                response, hops and recordings — and the list and trash
      console/                  the canvas console's log, one file a day, kept a week
      overrides.json            the project's override library
      broker.json               the message broker's address, if you set one

A project’s folder is named after the repository’s folder and a hash of its path. Moving or renaming a checkout therefore makes it a new project; rename the stored folder to carry its data across.

Nothing is written into the repositories you are debugging. No config file, no ignore entry, no generated code.

What is in a trace

A trace holds real payloads: the request and response of every hop, and the values your code handled while it ran. That is why it lives outside your repository, where it cannot be committed by accident.

Credentials are removed before a hop is even recorded: Authorization, Cookie, X-Api-Key and similar headers, and query parameters that carry a key or token. You can add your own header names per project. Bodies are kept up to a size limit and cut short past it.

What leaves your machine

  • On the Free plan: nothing. No account, no activation, no usage data, no crash reports.
  • With a license: a daily check that sends the license token, a hash of your machine’s id and the extension’s version. The full list is on the privacy page.

Requests you send from the runner go only to addresses on your own machine: localhost and 127.0.0.1. Debugt will not send one anywhere else, so it cannot be used as a way to reach whatever your computer can.

The page in your browser

Debugt’s interface is a page served from your own machine, at http://127.0.0.1:4400 by default. It is not on the internet: the server listens only on the loopback address, and it checks where each request comes from, so another website open in your browser cannot call it.

Removing everything

Uninstall the extension and delete ~/.debugt. Nothing else was created.