nettune

The server component (written in Go) requires root/sudo privileges to apply system-level network optimizations (sysctl, qdisc, systemd changes). The API key for authentication is passed via command-line arguments, which carries a risk of exposure in shell history; users are explicitly warned to secure their history. All communication between the client (JS wrapper) and the server uses HTTP with Bearer token authentication, meaning it is unencrypted by default. The project README recommends using TLS termination (e.g., an Nginx reverse proxy) for production deployments, but this is not enforced or built-in. The client-side (JS wrapper) automatically downloads the Go binary from GitHub releases and verifies it using SHA256 checksums, which is a good security practice. Request size limits are implemented for probe endpoints to mitigate resource exhaustion. The server itself does not consume or generate LLM tokens; the 'AI-assisted' aspect refers to external Chat GUIs interacting with the server via the MCP protocol.