<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Http on tsvinc</title>
		<link>https://tsvinc.dev/tags/http/</link>
		<description>Recent content in Http on tsvinc</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sat, 24 Oct 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://tsvinc.dev/tags/http/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>To a coding agent, 503 means try again</title>
				<link>https://tsvinc.dev/posts/503-means-try-again/</link>
				<pubDate>Sat, 24 Oct 2026 00:00:00 +0000</pubDate>
				<guid>https://tsvinc.dev/posts/503-means-try-again/</guid>
				<description>&lt;p&gt;&lt;code&gt;opencode run&lt;/code&gt; printed its banner, &lt;code&gt;&amp;gt; build · mock-err503&lt;/code&gt;, and then nothing. No error, no exit code, no output, until the run was killed. The mock server behind it answered every request with a 503 in my LAN proxy&#39;s error format: the status the proxy sent at the time for any model it couldn&#39;t serve, whether the GPU box was down, the engine switch had failed or a benchmark owned the GPU for the next few hours. opencode was retrying, and it had no plans to stop.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
