fix(t3-connect): serve Kamino T3 servers over Tailscale - #2853
Conversation
Publish-only Kamino links have no relay endpoint, and the relay caps managed tunnels at 3 per account, so T3 Connect entries for the workers fail with endpoint_provider_not_managed. Let t3code.service publish itself over Tailscale Serve on 443 so clients pair via the tailnet URL.
|
Warning This organization's free trial has ended, so Indent couldn't start this review. Manage billing to resume reviews on this repository. |
|
Warning Review limit reachedNext included review available in 45 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (3)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes
home-manager/services/t3-connect/default.nix: Added Kamino-specific Tailscale Serve route configuration for the t3-service manager, enabling T3 Code to publish itself over Tailscale on port 443 → 3773 for Kamino workers.named-hosts/kamino/README.md: Added documentation for connecting clients to the T3 server via Tailscale Serve, including the pairing command and workflow.tests/eval.nix: Added assertions to verify that theT3CODE_TAILSCALE_SERVE=trueandT3CODE_TAILSCALE_SERVE_PORT=443environment variables are set in the systemd drop-in for Kamino hosts.
The changes correctly address the publish-only connectivity issue for Kamino workers by leveraging T3-service-owned Tailscale Serve routes, avoiding the relay's managed tunnel limitations. The implementation follows existing patterns and includes appropriate test coverage.
openrouter/openrouter/free | 𝕏

Summary
endpoint_provider_not_managed. The relay also caps managed tunnels at 3 per account, which rules out managed links for the fleet.t3code.serviceruns withT3CODE_TAILSCALE_SERVE=trueand clients pair throughhttps://<name>.tail950b36.ts.net(t3 pair --tailscale).Verification
nix evalofhomeConfigurations.kamino3native-runtime.confcontains both env vars; kyber unchanged (8443).tests/eval.nixsuite and shellspec not run locally.🤖 Generated with Claude Code
Summary by cubic
Fixes T3 Connect failures on Kamino workers by serving the T3 server over Tailscale instead of the relay. Publish-only links have no relay endpoint (so entries fail with
endpoint_provider_not_managed), and the relay caps managed tunnels at 3 per account.t3-connectnow adds at3-service-managed Tailscale Serve route (443 -> 3773) for Kamino hosts, running withT3CODE_TAILSCALE_SERVE=trueandT3CODE_TAILSCALE_SERVE_PORT=443.t3 pair --tailscaleathttps://<name>.tail950b36.ts.net; the new README section and eval assertions cover the flow.Written for commit 120c114. Summary will update on new commits.