u/Azpect3120

Backend debugging still feels like guesswork — I built a terminal-first HTTP/S inspector to help

Backend debugging still feels like guesswork — I built a terminal-first HTTP/S inspector to help

Backend debugging often means partial logs + guesses, especially when your service is calling multiple APIs.

I built Termtap to make that loop faster:

  • wrap your command with tap run -- ...
  • see outbound HTTP/S traffic in real time
  • inspect requests/responses/failures in terminal

It’s local-first, terminal-first, and avoids code changes for basic traffic inspection. Current scope is intentionally focused (beta):

  • local debugging of outbound traffic
  • scripts/services/CLI tools
  • fast iteration over “why did this integration fail?”

Would love blunt feedback from backend engineers:

  • what workflows this misses
  • what features matter most (replay? payload edit? multi-process?)
  • what would make it production-useful vs just local-useful

GitHub Docs

u/Azpect3120 — 2 days ago