<feed xmlns='http://www.w3.org/2005/Atom'>
<title>tmuxrdr.git/src/cli/server_not_running.rs, branch v0.9.3</title>
<subtitle>herdr but with less disrespect for the tmux community
</subtitle>
<id>https://git.soarez.net/sz/tmuxrdr.git/atom?h=v0.9.3</id>
<link rel='self' href='https://git.soarez.net/sz/tmuxrdr.git/atom?h=v0.9.3'/>
<link rel='alternate' type='text/html' href='https://git.soarez.net/sz/tmuxrdr.git/'/>
<updated>2026-08-01T13:17:23+00:00</updated>
<entry>
<title>fix: report a clear cli error when no herdr server is running (#1963)</title>
<updated>2026-08-01T13:17:23+00:00</updated>
<author>
<name>Season Saw</name>
<email>season.saw@gmail.com</email>
</author>
<published>2026-08-01T13:17:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.soarez.net/sz/tmuxrdr.git/commit/?id=f99647b2c2d7fbfd11269330a25ea4f9be59bafa'/>
<id>urn:sha1:f99647b2c2d7fbfd11269330a25ea4f9be59bafa</id>
<content type='text'>
* fix: report a clear cli error when no herdr server is running

socket cli commands surfaced a raw io::Error debug string
(`Error: Os { code: 2, ... }`) when nothing was listening on the
api socket, which read like a bad --cwd path. map dead-socket
connect failures to a `server_not_running` json error carrying the
resolved socket path, printed once at the edge that surfaces the
error; recovering callers (plugin offline registry fallback, agent
start polling) recognize the marker and keep their existing
behavior.

refs #1941

* fix: map dead-socket errors on the unchecked cli request path

refs #1941

* fix: make server-not-running guidance session-aware

refs #1941</content>
</entry>
</feed>
