Problems in. Solutions out.

Solved cases from a working engineer: hands-on AI, coding agents, GEO and cloud. Each one states the problem, shows the fix, and gets an honest verdict.

solve.log

tail solve.log

2026-06-16SH-007How I Set Up Private and Residential Proxies Behind One RelayWORKS
2026-05-17SH-006Extending Browserless to Capture Initial XHRs with Listener-First ScriptsWORKS
2026-05-17SH-005Build a Secure VPS Crawl Engine with Proxy Levels and BrowserlessWORKS
2026-05-15SH-004How to Put a Residential Proxy Behind Cloudflare Tunnel for a WorkerWORKS
2026-05-11SH-003How to Set Up Hermes Agent on a VPS — No Docker, Just RootWORKS
2026-05-10SH-002I asked my AI agent to document its own debugging — and accidentally built a blogWORKS

Case files

7 cases, newest first

SH-007 / Cloudworks

How I Set Up Private and Residential Proxies Behind One Relay

Problem Agents and backend jobs needed direct, private, residential or browser egress without proxy credentials scattered across every script.

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.

Jun 16, 20268 min read

SH-006 / Cloudworks

Extending Browserless to Capture Initial XHRs with Listener-First Scripts

Problem Custom Puppeteer scripts ran after navigation, so they missed the XHRs a page fires during its first load.

May 17, 20265 min read

SH-005 / Cloudworks

Build a Secure VPS Crawl Engine with Proxy Levels and Browserless

Problem My apps and Workers needed controlled egress and optional browser rendering without becoming a public open proxy.

May 17, 202611 min read

SH-004 / Cloudworks

How to Put a Residential Proxy Behind Cloudflare Tunnel for a Worker

Problem A Cloudflare Worker only has fetch() and cannot route requests through a host:port residential proxy.

May 15, 20268 min read

SH-003 / Agentsworks

How to Set Up Hermes Agent on a VPS — No Docker, Just Root

Problem Running Hermes in Docker meant every .env change triggered a container redeploy that replaced the config file.

May 11, 20269 min read

SH-002 / Agentsworks

I asked my AI agent to document its own debugging — and accidentally built a blog

Problem Debugging lessons kept disappearing because the friction of writing them up was always too high.

May 10, 20268 min read

SH-001 / Agentsworks

From Telegram to demo.contextforce.com — wiring an AI agent to ship HTML on demand

Problem My agent answered Telegram requests with Docker-internal URLs like http://172.18.0.2:8090 that my phone could not open.

May 10, 202610 min read

Every case ends in a verdict

works: The fix solved the problem and is still running. Copy it.
partly: It helped, with limits. The case says exactly where it stops.
failed: It did not work. Written up anyway, so you can skip the same dead end.