kerlenton

Ha, fair. tshark in a shell works fine, the only reason to wrap it is typed output and not handing the agent a raw shell.

Thanks, that means a lot. Would love to hear how it goes once you try it

There's nothing redacted because the header isn't collected in the first place. Under http mode, the proxy intercepts the JSON-RPC messages, but not their headers, so there's no way for the log to contain the Authorization header and the bearer passes through unlogged. The contents of the messages themselves aren't redacted, which means if the secret is in the payload, it'll end up in the trace. The trace stays on your machine, and if you don't want anything to go to the disk at all, use --no-trace.

Maybe, but I didn't do it. Perhaps people are boosting their karma?

Thanks a lot!

Thank you! Showing the data in a web page should definitely be possible. But I’m not sure if this matches the original idea I had, where the tool would run in the terminal only. Why do you feel the need to show the data in a web page? Is there anything missing in the CLI?