I was using Perplexity API for synthesis and spent around $10 every few days just based on the volume of research runs my agents were doing. This is a fairly cheap alternative way to do bulk research. The only difference is it can take a little longer. The synthesis layer that offloads tool results to a reasoning model for gating not only improves the results but also saves on tokens for the frontier model-driven main agent. Two branches on the repo; you can synthesize in the cloud (cheap OpenRouter default model) or locally.
Where it comes to AI generated output, that mostly depends on the input. If you prompt with specifics of what you want and go into detail, you are much more in control of the output.
Its done, but too late to edit the title of this submission. One of the unfortunate things about churning out AI slop is that the AI doesn't always catch all of its turds in one go.
I mean if you want to be anal about it, its just semantics, right? You know, how something is one way relative to something else, but relative to the other thing its not. Certainly not something to get bothered about.
If you start countering geolocation blocking with vps rental and VLESS vray etc then its still good to obfuscate at the endpoint. Passing VPN traffic off as something else is good policy wherever your tunnel goes.
You're right that iptables rules execute in kernel space, not dedicated hardware. "Hardware kill switch" in VPN contexts typically means the protection is implemented at the network appliance level (router) rather than a software client on each device. The distinction matters because a) client-side kill switch: App crashes → traffic leaks until you notice, and b) router-level kill switch :Default DROP policy persists regardless of client state. Also, the project is for non-techies and vibe coders, so simple explanations help. For their agents, there's the juice in other docs.
That's where VPN obfuscation is the play, imo. A lot of people nowadays are leaving streaming platforms or watch YT on smart TVs, so it does have a place. You can always exclude a device from the VPN coverage too.
It prompts the user's agent to audit their network devices and topology first, and research online if it gets stuck. The configs need to be agnostic and contain placeholders. The whole idea is that the agent helps the user vibe code this, which is very doable, and probably the norm when there are so many people looking for solutions like this given the current climate. And netns is for single-host isolation. This is a router forwarding LAN→WAN. Different problem.