<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>solutionhacker</title><description>Hands-on AI and dev guides.</description><link>https://solutionhacker.com/</link><item><title>How to Put a Residential Proxy Behind Cloudflare Tunnel for a Worker</title><link>https://solutionhacker.com/cloudflare-worker-vps-proxy-relay/</link><guid isPermaLink="true">https://solutionhacker.com/cloudflare-worker-vps-proxy-relay/</guid><description>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.</description><pubDate>Fri, 15 May 2026 00:00:00 GMT</pubDate></item><item><title>From Telegram to demo.contextforce.com — wiring an AI agent to ship HTML on demand</title><link>https://solutionhacker.com/from-telegram-to-demo-contextforce/</link><guid isPermaLink="true">https://solutionhacker.com/from-telegram-to-demo-contextforce/</guid><description>Pre-wire the hosting once (a persistent http.server behind a Cloudflare Tunnel) and reduce the agent&apos;s job to picking a folder name. The reply URL becomes https://demo.contextforce.com/&lt;name&gt;/, so the agent cannot return a wrong one.</description><pubDate>Sun, 10 May 2026 00:00:00 GMT</pubDate></item><item><title>How to Set Up Hermes Agent on a VPS — No Docker, Just Root</title><link>https://solutionhacker.com/hermes-agent-vps-setup-guide/</link><guid isPermaLink="true">https://solutionhacker.com/hermes-agent-vps-setup-guide/</guid><description>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.</description><pubDate>Mon, 11 May 2026 00:00:00 GMT</pubDate></item><item><title>I asked my AI agent to document its own debugging — and accidentally built a blog</title><link>https://solutionhacker.com/i-asked-my-agent-to-document-itself/</link><guid isPermaLink="true">https://solutionhacker.com/i-asked-my-agent-to-document-itself/</guid><description>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 &quot;let&apos;s recap&quot; to a draft at a real URL takes under a minute.</description><pubDate>Sun, 10 May 2026 00:00:00 GMT</pubDate></item><item><title>Extending Browserless to Capture Initial XHRs with Listener-First Scripts</title><link>https://solutionhacker.com/listener-first-browserless-xhr-capture/</link><guid isPermaLink="true">https://solutionhacker.com/listener-first-browserless-xhr-capture/</guid><description>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.</description><pubDate>Sun, 17 May 2026 00:00:00 GMT</pubDate></item><item><title>How I Set Up Private and Residential Proxies Behind One Relay</title><link>https://solutionhacker.com/private-residential-proxy-relay-sticky-sessions/</link><guid isPermaLink="true">https://solutionhacker.com/private-residential-proxy-relay-sticky-sessions/</guid><description>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.</description><pubDate>Tue, 16 Jun 2026 00:00:00 GMT</pubDate></item><item><title>Build a Secure VPS Crawl Engine with Proxy Levels and Browserless</title><link>https://solutionhacker.com/vps-crawl-engine-proxy-levels-browserless/</link><guid isPermaLink="true">https://solutionhacker.com/vps-crawl-engine-proxy-levels-browserless/</guid><description>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.</description><pubDate>Sun, 17 May 2026 00:00:00 GMT</pubDate></item></channel></rss>