Earlier quoted context omitted.
That's what LLMs enabled. Faster prototyping. Also lots of exposed servers and apps. It's never been more fun to be a cyber security researcher.
I think it just has been more fun being into computers overall!
Show HN: A MitM proxy to see what your LLM tools are sending
21–30 of 128 posts
Re: Show HN: A MitM proxy to see what your LLM tools are sending
#22Earlier quoted context omitted.
I think it just has been more fun being into computers overall!
It's interesting because if you're into computers it's more accessible than ever and there are more things you can mess with more cheaply than ever. I mean we have some real science fiction stuff going on. At the same time it's probably different for the newer generations. Computers were magical to me and a lot of that was because they were rare. Now they are everywhere, they are just a backdrop to everything else go…
Re: Show HN: A MitM proxy to see what your LLM tools are sending
#23You don't need to mess with certificates - you can point CC at a HTTP endpoint and it'll happily play along. If you build a DIY proxy you can also mess with the prompt on the wire. Cut out portions of the system prompt etc. Or redirect it to a different endpoint based on specific conditions etc.
Re: Show HN: A MitM proxy to see what your LLM tools are sending
#24Earlier quoted context omitted.
> So is it just a wrapper around MitM Proxy? Yes. I created something similar months ago [*] but using Envoy Proxy [1], mkcert [2], my own Go (golang) server, and Little Snitch [3]. It works quite well. I was the first person to notice that Codex CLI now sends telemetry to ab.chatgpt.com and other curiosities like that, but I never bothered to open-source my implementation because I know that anyone genuinely interes…
Curious to see how you can get Gemini fully intercepted. I've been intercepting its HTTP requests by running it inside a docker container with: -e HTTP_PROXY= http://127.0.0.1:8080 -e HTTPS_PROXY= http://host.docker.internal:8080 -e NO_PROXY=localhost,127.0.0.1 It was working with mitmproxy for a very brief period, then the TLS handshake started failing and it kept requesting for re-authentication when proxied. You c…
Re: Show HN: A MitM proxy to see what your LLM tools are sending
#25Re: Show HN: A MitM proxy to see what your LLM tools are sending
#26This is fantastic. Claude doesn't make it easy to inspect what it's sending - which would actually be really useful for refining the project-specific prompts.
Re: Show HN: A MitM proxy to see what your LLM tools are sending
#27This is great. When I work with AI on large, tricky code bases I try to do a collaboration where it hands off things to me that may result in large number of tokens (excess tool calls, unprecise searches, verbose output, reading large files without a range specified, etc.). This will help narrow down exactly which to still handle manually to best keep within token budgets. Note: "yourusername" in install git clone in…
Re: Show HN: A MitM proxy to see what your LLM tools are sending
#28What about SSL/certificates ?
Re: Show HN: A MitM proxy to see what your LLM tools are sending
#29You don't need to mess with certificates - you can point CC at a HTTP endpoint and it'll happily play along. If you build a DIY proxy you can also mess with the prompt on the wire. Cut out portions of the system prompt etc. Or redirect it to a different endpoint based on specific conditions etc.
Have you tried this with Gemini? or Codex?