feat(dev): add kiloclaw-worker-tunnel for local wrangler dev checkin routing#1955
feat(dev): add kiloclaw-worker-tunnel for local wrangler dev checkin routing#1955evanjacobson wants to merge 6 commits intomainfrom
Conversation
…routing Adds a second named cloudflare tunnel (kiloclaw-worker) that routes machine checkins to the local wrangler dev worker on port 8795. Without this, checkins from Fly machines hit the production worker and fail auth (403) because the gateway token secret differs between envs.
![kilo-code-bot[bot]](https://avatars.githubusercontent.com/in/2193792?s=60&v=4){kind=small}
Code Review SummaryStatus: 1 Issue Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
Other Observations (not in diff)No additional issues outside the current diff. The two previously reported Files Reviewed (2 files)
Fix these issues in Kilo Cloud Reviewed by gpt-5.4-20260305 · 145,687 tokens |
| const captureServiceSet = new Set(['kiloclaw-tunnel', 'kiloclaw-stripe', 'app-builder-tunnel']); | ||
| const captureServiceSet = new Set([ | ||
| 'kiloclaw-tunnel', | ||
| 'kiloclaw-worker-tunnel', |
There was a problem hiding this comment.
WARNING: kiloclaw-worker-tunnel is started as a capture service but never awaited
cmdUp only snapshots and waits for KILOCODE_API_BASE_URL, STRIPE_WEBHOOK_SECRET, and BUILDER_HOSTNAME. After adding kiloclaw-worker-tunnel here, the code still never waits for KILOCLAW_CHECKIN_URL to change, so kiloclaw can start before the worker tunnel writes its endpoint into kiloclaw/.dev.vars. On a fresh quick-tunnel startup that leaves the worker booting with a stale or missing check-in URL.
2 participants
Summary
These changes extend the existing start-tunnel script & other kiloclaw dev infra to spin-up a second cloudflare tunnel for the worker, which adds a missing piece of infra (machine checkin) to the KiloClaw admin panel.
Reviewer Notes