No monthly tunnel request quota
Direct HTTPS connects an AI client to your own running RepoTunnel HTTPS endpoint. It provides unlimited connection usage without RepoTunnel adding a monthly tunnel request quota or connection-credit allowance.
Keep the service and HTTPS endpoint running to use the connection for successive project tasks, fixes, reviews and improvements. Workspace permissions and OAuth stay in force.
Verified Linux path
The documented Linux Mint setup uses Route64 + WireGuard for a public IPv6 path, DuckDNS for a stable hostname, Let's Encrypt for TLS, and an IPv4-to-IPv6 frontend when required by IPv4-only clients.
- Public TCP 443 → RepoTunnel Direct HTTPS listener
- Public TCP 80 → ACME challenge listener
- Loopback MCP origin remains private
- OAuth/MCP/health routes are allowlisted
Who should use it
Use Direct HTTPS when you want to manage your own public connection and work without a tunnel provider’s monthly request allowance. It requires control of the network route, hostname and certificate lifecycle.
The documented path is validated on Linux. A managed provider such as ngrok offers a simpler setup when you prefer a hosted relay.
Follow HTTPS Setup in the app
The guided screen checks local requirements, Internet connectivity, the selected hostname/DNS and the final Direct HTTPS endpoint. Complete each stage using its reported evidence.
The current verified topology is Linux-specific and requires a reachable public network path and trusted TLS. Keep the raw MCP gateway bound to loopback.
Keep the connection available
Keep RepoTunnel and its HTTPS listener running on a computer that stays connected to the internet. After a reboot or network change, check the public route and trusted HTTPS response before continuing.
Maintain DNS records and certificate renewal for the hostname your AI client uses. Use the connection diagnostics to investigate a failed health check or OAuth discovery response.