<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Self-Hosted-Runners on Start AI Tools - Presented by Intent Solutions</title><link>https://startaitools.com/tags/self-hosted-runners/</link><description>Recent content in Self-Hosted-Runners on Start AI Tools - Presented by Intent Solutions</description><generator>Hugo</generator><language>en-US</language><copyright>Intent Solutions. All rights reserved.</copyright><lastBuildDate>Sat, 17 Oct 2026 10:00:00 -0600</lastBuildDate><atom:link href="https://startaitools.com/tags/self-hosted-runners/index.xml" rel="self" type="application/rss+xml"/><item><title>Move the deploy runner onto the tailnet, skip Tailscale OIDC</title><link>https://startaitools.com/posts/when-the-tailnet-trial-ends-move-the-runner-onto-the-network/</link><pubDate>Sat, 17 Oct 2026 10:00:00 -0600</pubDate><guid>https://startaitools.com/posts/when-the-tailnet-trial-ends-move-the-runner-onto-the-network/</guid><description>&lt;p&gt;When a deploy needs a fresh login token every run, and the broker that issues those tokens stops being free, the token call returns 402 Payment Required and the rest of the job still reports success. Production stays on the previous build for days. What you have at the end of this post is a GitHub Actions deploy workflow with two settings any caller can flip (join-tailnet: false, and send-revision: false), a mode where the runner is already a member of the private network and so does not need to mint a token at all, and the order in which to migrate each repo that calls this workflow one at a time.&lt;/p&gt;</description></item></channel></rss>