[RedStar071]

❓ Type of change

• 📖 Documentation
• 🐞 Bug fix
• 👌 Enhancement
• ✨ New feature
• 🧹 Chore
• ⚠️ Breaking change

📚 Description

Agents and their sessions should live on Hogwild, and the dashboard should only be the interface to them. #19 went the other way and made the Cloudflare Container an Agent session host. This undoes that: the Worker keeps webhook intake with the Queue, the dashboard proxy and Cloudflare Access, and forwards both to CONTROLLER_URL. The Container, its Durable Object, /setup, provider logins, Artifacts snapshots and the Edge session host are gone, along with the dashboard settings that talked to them.

Workers AI and the Jev classification stay. They are model providers, not hosting, and work from Hogwild.

⚠️ Breaking Changes

The Worker no longer runs a controller. Webhooks and the dashboard need a controller reachable at CONTROLLER_URL.

📝 Migration

1. wrangler secret put GITHUB_WEBHOOK_SECRET with the same value the controller reads from webhook.secret_path. Until it is set, every delivery gets a 503.
2. Check CONTROLLER_URL in wrangler.jsonc. It defaults to https://agent.harlanzw.com, the Caddy route in scripts/public-dashboard.md, and must be a public https origin.
3. The deploy applies migration v2, which deletes ControllerContainer and the setup record it stored (GitHub App key, dashboard password, provider logins). The Container application and the controller/ journal in R2 stay until you delete them by hand.

🤖 AI disclosure: Wolfstar Agent Kit modified this description. My AI open-source policy.

[coldtea-pr-lens]

Architecture

Inside the changed components — 1 view

Component view — Edge Worker & Relay

Internal components of the edge relay and reverse proxy connecting to the external controller.

Data flow

Review

✨ Nothing flagged · reviewed 3cd80c0

Tip

Set github.draw: on-demand in .github/pr-lens.yml and PR Lens stops drawing pull requests on its own. Comment @pr-lens draw on a pull request when you want that one drawn

🪧 More tips

• Run npx skills add coldteadotai/pr-lens, then tell your coding agent: "Diagram the change you just made with PR Lens and attach it to the pull request."
• Run npx @coldtea/pr-lens-cli analyze --base origin/main on a branch, then npx @coldtea/pr-lens-cli render .pr-lens/graph.json. Same lenses, your own model key, before the pull request exists
• Click the link under each diagram to open it on a canvas you can zoom, pan and step through
• The diagrams are links. Click one to open it on the canvas, then press W or click play to walk through the change
• Open a diagram on the canvas, then press W or click play to walk through the change one step at a time
• The CLI's render reads .github/pr-lens.yml and applies your renames, exclusions and lane pins at draw time
• Set github.comment.collapsed: true in .github/pr-lens.yml to fold the comment behind one View architecture and data flow row. Drawing still runs as before
• Add .github/workflows/pr-lens.yml with coldteadotai/pr-lens/packages/action@v0 and your model provider's key as its api-key to run PR Lens from your own CI. Any /chat/completions endpoint works
• After a push, tick Redraw to draw the latest commit
• Switch GitHub to dark mode and the diagrams follow. The moving dots are this pull request's data in motion
• Set github.description: false in .github/pr-lens.yml to stop PR Lens adding buttons to your PR descriptions

_{Thanks for using PR Lens! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out on X, Bluesky, Mastodon, Reddit or LinkedIn}