Debugt
Documentation

Sharing a send

Share one send by link — its hops, and what each service's code did — for someone to open in a browser or in Debugt.

A send is often easier shown than described: the request, every hop it made, and what the code did at each. Share it by link, and whoever you send the link to opens the same trace — in a browser, with nothing installed, or in Debugt. Free and Pro can both share.

Sharing one

Choose Share… from a send’s menu: on its row in Request History (right-click, or ⋯), in the history table, or the ⋯ on its trace. Share send shows what would go before anything does:

Shown What it says
Trace How many hops, and in which services.
Taken out The headers and body fields that will be redacted. Redact more… opens Settings → Redact to add to them.
Size How large it is, sealed. A shared send can be up to 25 MB.
Include recorded values What each hop’s code did, line by line, with its variables. Untick to share the hops alone — smaller, and with none of the values your code handled.
Link lasts 1, 3, 7 or 14 days, as far as your plan allows.

Create link seals it, uploads it and gives you the link to Copy. A shared send’s row in Request History carries a link mark, and its menu says Shared link…, which opens the same link again — sharing a send twice gives the same link, not a second one.

What is shared, and what is not

  • Redacted again, as your rules are now. Before it leaves your machine the send is redacted with your project’s current headers, body fields and recorded variables — including headers you typed into the request, which history keeps as they were. A rule added since the send was made still applies.
  • Nothing that only means something on your machine: the project’s id, the send’s name and bookmark, and the folder its recording came from are left out.
  • Encrypted on your machine, with a key made for this send alone. The key is in the link, after the #, which a browser never sends to a server. Debugt’s server holds the encrypted bytes and when they expire — it cannot read the URL, the services or the status, let alone the bodies.

Anyone with the whole link can open the send until it ends. Treat it as you would the send itself.

  • In a browser. A link opens at debugt.dev, a domain apart from Debugt’s website, which downloads the send and decrypts it in the page. The trace reads as it does in Debugt — hops, bodies, execution — and Open in VS Code hands it to Debugt if it is installed.
  • In Debugt. The link icon in Request History’s header — Open a shared link — takes a pasted link. So does the command Debugt: Open Shared Send. It opens over the history list, read-only, and is not added to any project’s history.

How long, and how many

Free Pro Team
A link lasts up to 3 days 7 days 14 days
Links open at once 3, on each machine 50, across your machines 100 for each member

Past the number open at once, a new share is refused until one expires or is revoked.

Revoking

Revoke link, in a shared send’s Shared link…, ends it at once, for everyone: the encrypted send is deleted from storage, and the link says it was revoked from then on. An expired link is deleted the same way, within a quarter of an hour of its end.

To change how long a link lasts, revoke it and share the send again.