# solutionhacker

> Hands-on AI and dev guides.

## Guides

- [How to Put a Residential Proxy Behind Cloudflare Tunnel for a Worker](https://solutionhacker.com/cloudflare-worker-vps-proxy-relay): Put a small VPS relay behind Cloudflare Tunnel: Worker → HTTPS relay → randomized residential proxy → target website. The Worker stays serverless and simple, and the VPS does the network plumbing.
- [From Telegram to demo.contextforce.com — wiring an AI agent to ship HTML on demand](https://solutionhacker.com/from-telegram-to-demo-contextforce): Pre-wire the hosting once (a persistent http.server behind a Cloudflare Tunnel) and reduce the agent's job to picking a folder name. The reply URL becomes https://demo.contextforce.com/<name>/, so the agent cannot return a wrong one.
- [How to Set Up Hermes Agent on a VPS — No Docker, Just Root](https://solutionhacker.com/hermes-agent-vps-setup-guide): Run Hermes directly as root on a bare Ubuntu VPS, with the gateway as a systemd service, Telegram, Cloudflare Tunnel and Claude Code. Your .env at /root/.hermes/.env is then a plain file on disk that nothing overwrites.
- [I asked my AI agent to document its own debugging — and accidentally built a blog](https://solutionhacker.com/i-asked-my-agent-to-document-itself): Reuse the pipeline that already ships HTML previews as a blog: one Telegram message asks the agent for a recap, it writes the post into posts/ and rebuilds the index. From "let's recap" to a draft at a real URL takes under a minute.
- [Extending Browserless to Capture Initial XHRs with Listener-First Scripts](https://solutionhacker.com/listener-first-browserless-xhr-capture): Split Browserless into two modes: with no script the relay navigates and returns HTML as before; with a script it leaves the page at about:blank and the script calls page.goto itself. That lets the script install its listeners before the first byte of the real page load.
- [How I Set Up Private and Residential Proxies Behind One Relay](https://solutionhacker.com/private-residential-proxy-relay-sticky-sessions): One authenticated HTTPS relay on a VPS with three egress levels, optional Browserless rendering, and sticky session keys when a workflow needs the same IP across requests. Clients get a clean API while proxy credentials, retries and provider quirks stay inside one controlled box.
- [Build a Secure VPS Crawl Engine with Proxy Levels and Browserless](https://solutionhacker.com/vps-crawl-engine-proxy-levels-browserless): Run a private, authenticated relay on a VPS with three proxy levels (direct, private, residential) and Browserless for JavaScript rendering, exposed only through Cloudflare Tunnel. Callers choose a URL, a level and whether to render; the crawl engine handles the rest.