<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
    <title>Ben Hart | Productive Developer</title>
    <subtitle>I write about developer productivity on Linux: XMonad, terminal tools, and coding agents across machines.</subtitle>
    <link rel="self" type="application/atom+xml" href="https://devproductive.dev/atom.xml"/>
    <link rel="alternate" type="text/html" href="https://devproductive.dev"/>
    <generator uri="https://www.getzola.org/">Zola</generator>
    <updated>2026-11-21T00:00:00+00:00</updated>
    <id>https://devproductive.dev/atom.xml</id>
    <entry xml:lang="en">
        <title>Running coding agents on several machines with herdr</title>
        <published>2026-11-21T00:00:00+00:00</published>
        <updated>2026-11-21T00:00:00+00:00</updated>
        
        <author>
          <name>Ben Hart</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://devproductive.dev/blog/agents-across-machines/"/>
        <id>https://devproductive.dev/blog/agents-across-machines/</id>
        
        <content type="html" xml:base="https://devproductive.dev/blog/agents-across-machines/">&lt;p&gt;I run coding agents on several machines at once, in &lt;a rel=&quot;external&quot; href=&quot;https://herdr.dev&quot;&gt;herdr&lt;/a&gt;, a terminal multiplexer built for
them. One herdr window on my desk reaches every machine (&lt;code&gt;herdr machine list&lt;/code&gt;), and its sidebar lists the agents. The
trouble came with numbers: with agents spread across machines, I kept missing the ones that had stopped to ask me
something.&lt;/p&gt;
&lt;p&gt;So I wrote three plugins. (herdr-queues is also up in herdr&#39;s &lt;a rel=&quot;external&quot; href=&quot;https://github.com/herdrdev/herdr/discussions/6127&quot;&gt;Show and tell&lt;/a&gt;.)&lt;/p&gt;
&lt;h2 id=&quot;herdr-queues-who-is-waiting-on-me&quot;&gt;herdr-queues: who is waiting on me&lt;/h2&gt;
&lt;p&gt;&lt;a rel=&quot;external&quot; href=&quot;https://github.com/Benjmhart/herdr-queues&quot;&gt;herdr-queues&lt;/a&gt; is a popup (I bind it to &lt;code&gt;prefix+u&lt;/code&gt;) listing the agents on
every machine, each with one line of what it needs: the agent&#39;s own recap line when it printed one, else the question
on its screen, else its last line. Agents that asked me something come first, then the finished ones.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/Benjmhart/herdr-queues/main/docs/screenshot.png&quot; alt=&quot;herdr-queues: the popup over the sidebar grouped by queue&quot; /&gt;&lt;/p&gt;
&lt;p&gt;I sort agents into my own queues (work, personal, whatever I name them), the same on every machine, and each tab
counts the ones waiting. Enter jumps to the agent and switches the herdr window to its machine. &lt;code&gt;/&lt;/code&gt; searches every
agent everywhere.&lt;/p&gt;
&lt;p&gt;Switching machines takes a small watcher on the desk machine, because a plugin can&#39;t switch machines yet. The watcher
runs on Linux (X11, sway, Hyprland, KDE Plasma, GNOME) and Windows 11; a Mac works as a machine you reach, not as the
desk.&lt;/p&gt;
&lt;h2 id=&quot;herdr-inandout-back-to-where-i-was&quot;&gt;herdr-inandout: back to where I was&lt;/h2&gt;
&lt;p&gt;Jumping between agents loses your place. &lt;a rel=&quot;external&quot; href=&quot;https://github.com/Benjmhart/herdr-inandout&quot;&gt;herdr-inandout&lt;/a&gt; is vim&#39;s jump
list for herdr: &lt;code&gt;prefix+o&lt;/code&gt; goes back to the pane I was in, &lt;code&gt;prefix+i&lt;/code&gt; forward again, and &lt;code&gt;prefix+shift+i&lt;/code&gt; lists the
history so Enter jumps to any of it, across machines.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/Benjmhart/herdr-inandout/main/docs/demo.gif&quot; alt=&quot;herdr-inandout: back through three workspaces, then the history list&quot; /&gt;&lt;/p&gt;
&lt;h2 id=&quot;herdr-machine-icons-which-machine-is-this&quot;&gt;herdr-machine-icons: which machine is this&lt;/h2&gt;
&lt;p&gt;Machine names eat a sidebar row. &lt;a rel=&quot;external&quot; href=&quot;https://github.com/Benjmhart/herdr-machine-icons&quot;&gt;herdr-machine-icons&lt;/a&gt; gives every
pane its machine&#39;s icon as a token, so a row shows 🦊 instead of a hostname.&lt;/p&gt;
&lt;p&gt;&lt;img src=&quot;https://raw.githubusercontent.com/Benjmhart/herdr-machine-icons/main/docs/demo.gif&quot; alt=&quot;herdr-machine-icons: agents on three machines, each with its icon&quot; /&gt;&lt;/p&gt;
&lt;p&gt;All three are Python 3 standard library, no server or binary: &lt;code&gt;herdr plugin install Benjmhart/herdr-queues&lt;/code&gt; (and the
others), then the keys from each README. Bug reports and ideas are welcome on each repo.&lt;/p&gt;
</content>
        
    </entry>
    <entry xml:lang="en">
        <title>Zoom screen share on XMonad + picom: black screen, then a grey &quot;dimmed&quot; overlay</title>
        <published>2026-11-20T00:00:00+00:00</published>
        <updated>2026-11-20T00:00:00+00:00</updated>
        
        <author>
          <name>Ben Hart</name>
        </author>
        
        <link rel="alternate" type="text/html" href="https://devproductive.dev/blog/zoom-xmonad-picom/"/>
        <id>https://devproductive.dev/blog/zoom-xmonad-picom/</id>
        
        <content type="html" xml:base="https://devproductive.dev/blog/zoom-xmonad-picom/">&lt;p&gt;Sharing my screen in Zoom on Linux (X11, the XMonad window manager, and the picom compositor) went wrong in three
different ways. Each had its own cause and its own fix:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;People saw a black screen.&lt;/strong&gt; My monitor setup marked a monitor that wasn&#39;t plugged in as the main one.
&lt;strong&gt;Fix:&lt;/strong&gt; mark a connected monitor as the main one (&lt;code&gt;xrandr --output &amp;lt;your monitor&amp;gt; --primary&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Zoom&#39;s &quot;share a window&quot; list was empty.&lt;/strong&gt; XMonad doesn&#39;t tell other programs which windows are open, unless you
turn that on. &lt;strong&gt;Fix:&lt;/strong&gt; turn it on (&lt;code&gt;ewmh&lt;/code&gt; in your XMonad config), and move the window you want to share onto a
visible workspace first.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Everything I shared was dimmed to about a quarter of its brightness.&lt;/strong&gt; picom drew a dark shadow under Zoom&#39;s
invisible &quot;you are sharing&quot; frame, and that shadow covered the whole screen. &lt;strong&gt;Fix:&lt;/strong&gt; turn shadows off in picom
(&lt;code&gt;shadow = false;&lt;/code&gt;), then restart picom.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The third one is the reason for this post. It looks like a Zoom bug, and the picom settings you&#39;d try first don&#39;t
touch it.&lt;/p&gt;
&lt;h2 id=&quot;my-setup&quot;&gt;My setup&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Arch Linux on X11 (not Wayland), with two monitors: one normal, one turned on its side.&lt;/li&gt;
&lt;li&gt;XMonad 0.15 with xmonad-contrib 0.16 (an old version; this matters in step 2).&lt;/li&gt;
&lt;li&gt;picom with the config Arch ships (&lt;code&gt;/etc/xdg/picom.conf&lt;/code&gt;): shadows and fading on, &lt;code&gt;backend = &quot;xrender&quot;&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Zoom&#39;s own Linux app, sharing &quot;Desktop 1&quot; (one monitor).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;I worked this out in August 2026, on the picom and Zoom versions Arch had then. I didn&#39;t write down the exact
versions.&lt;/p&gt;
&lt;h2 id=&quot;1-black-screen-the-main-monitor-was-one-that-wasn-t-plugged-in&quot;&gt;1. Black screen: the &quot;main monitor&quot; was one that wasn&#39;t plugged in&lt;/h2&gt;
&lt;p&gt;X11 marks one monitor as the main (&quot;primary&quot;) one. Mine was marked on a port with nothing plugged in:&lt;/p&gt;
&lt;pre&gt;&lt;code data-lang=&quot;console&quot;&gt;$ xrandr --query | grep -w connected
DisplayPort-0 disconnected primary      &amp;lt;-- marked as the main monitor, but nothing is plugged in
HDMI-A-0      connected 1920x1080+0+0
HDMI-A-1      connected 1080x1920+1920+0 right
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;My login script turned the old port off but never marked another monitor as the main one. Zoom asked for the main
monitor&#39;s picture, got nothing, and sent black.&lt;/p&gt;
&lt;p&gt;Fix it now, with the name of a monitor that is plugged in:&lt;/p&gt;
&lt;pre&gt;&lt;code data-lang=&quot;sh&quot;&gt;xrandr --output HDMI-A-0 --primary
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;To keep it fixed, add &lt;code&gt;--primary&lt;/code&gt; to the monitor setup you run at login:&lt;/p&gt;
&lt;pre&gt;&lt;code data-lang=&quot;sh&quot;&gt;xrandr --output DisplayPort-0 --off --output DisplayPort-1 --off \
       --output HDMI-A-0 --primary --mode 1920x1080 --pos 0x0 --rotate normal \
       --output HDMI-A-1 --mode 1920x1080 --pos 1920x0 --rotate right \
       --output DVI-D-0 --off
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;After this, people could read my screen. But it was dimmed (step 3).&lt;/p&gt;
&lt;h2 id=&quot;2-empty-window-list-turn-on-ewmh-in-xmonad&quot;&gt;2. Empty window list: turn on EWMH in XMonad&lt;/h2&gt;
&lt;p&gt;Programs like Zoom find out which windows are open through a standard called EWMH. XMonad doesn&#39;t support it until you
turn it on, so Zoom&#39;s window list had nothing in it. To check:&lt;/p&gt;
&lt;pre&gt;&lt;code data-lang=&quot;sh&quot;&gt;xprop -root _NET_SUPPORTED     # &amp;quot;not found&amp;quot; means EWMH is off
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;&lt;strong&gt;On xmonad-contrib 0.16, don&#39;t copy an example written for a newer version.&lt;/strong&gt; &lt;code&gt;ewmhFullscreen&lt;/code&gt; doesn&#39;t exist in 0.16.
The smallest change that works there is:&lt;/p&gt;
&lt;pre&gt;&lt;code data-lang=&quot;haskell&quot;&gt;import XMonad.Hooks.EwmhDesktops (ewmh)

main = xmonad $ ewmh $ def { ... }
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;&lt;code&gt;ewmh&lt;/code&gt; adds to your existing settings rather than replacing them, so an xmobar status bar keeps working. If you need
to set the pieces separately, this is the same thing written out:&lt;/p&gt;
&lt;pre&gt;&lt;code data-lang=&quot;haskell&quot;&gt;import XMonad.Hooks.EwmhDesktops (ewmhDesktopsStartup, ewmhDesktopsLogHook, ewmhDesktopsEventHook)

  xmonad $ def
    { startupHook     = myStartupHook &amp;lt;+&amp;gt; ewmhDesktopsStartup
    , logHook         = (&amp;lt;+&amp;gt; ewmhDesktopsLogHook) $ dynamicLogWithPP xmobarPP { ... }
    , handleEventHook = handleEventHook def &amp;lt;+&amp;gt; docksEventHook &amp;lt;+&amp;gt; ewmhDesktopsEventHook
    , ...
    }
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;On xmonad-contrib 0.17 or newer, follow the current &lt;code&gt;ewmh&lt;/code&gt; / &lt;code&gt;ewmhFullscreen&lt;/code&gt; docs instead.&lt;/p&gt;
&lt;p&gt;Recompile and restart XMonad (&lt;code&gt;mod-q&lt;/code&gt;), and check again: &lt;code&gt;_NET_SUPPORTED&lt;/code&gt; should now list &lt;code&gt;_NET_CLIENT_LIST&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Some windows will still be missing, and that&#39;s expected.&lt;/strong&gt; XMonad hides the windows on workspaces you can&#39;t see, and
Zoom only lists windows that are showing. So: move the window you want to share onto a visible workspace &lt;em&gt;before&lt;/em&gt; you
open Zoom&#39;s list.&lt;/p&gt;
&lt;h2 id=&quot;3-the-dimmed-screen-a-shadow-over-everything&quot;&gt;3. The dimmed screen: a shadow over everything&lt;/h2&gt;
&lt;h3 id=&quot;what-it-looked-like&quot;&gt;What it looked like&lt;/h3&gt;
&lt;p&gt;People could read my screen, but everything was dark and washed out, and I saw it too. Zoom&#39;s floating toolbars showed
up as bright rectangles in the dark area. Stopping picom during a share fixed it at once; starting picom brought it
back.&lt;/p&gt;
&lt;h3 id=&quot;measuring-it&quot;&gt;Measuring it&lt;/h3&gt;
&lt;p&gt;I compared a screenshot of my screen with what the other side received. Every colour came through at about a quarter
of its real brightness: my terminal&#39;s background (&lt;code&gt;#282a36&lt;/code&gt;, red-green-blue 40, 42, 54) arrived as 10, 10, 14, and its
white text (248) as 62. Every pixel was multiplied by the same 0.24 or so. That&#39;s exactly what a black layer at about
75% opacity over the whole screen does. It only looked &quot;grey&quot; because a dark theme at a quarter brightness looks washed
out.&lt;/p&gt;
&lt;p&gt;The bright rectangles were Zoom&#39;s toolbars. They sit above that black layer, and Zoom fills their space in the shared
picture with whatever is underneath, which isn&#39;t dimmed.&lt;/p&gt;
&lt;h3 id=&quot;the-cause&quot;&gt;The cause&lt;/h3&gt;
&lt;p&gt;While you share, Zoom puts an invisible window over the whole screen (it draws the &quot;you are sharing&quot; border). Listing
the windows during a share showed two screen-sized windows that only exist while sharing; one of them has no name
(&lt;code&gt;WM_CLASS&lt;/code&gt;) and is marked as a &quot;dock&quot;.&lt;/p&gt;
&lt;p&gt;Arch&#39;s stock picom config draws shadows (&lt;code&gt;shadow = true&lt;/code&gt;), excludes no windows from them, and leaves the shadow at its
default darkness of 75%. So picom drew a shadow under Zoom&#39;s invisible full-screen window. A shadow is a black
rectangle at 75% opacity, and because the window on top is invisible, nothing hides it: the whole screen goes dark.
That matches the 0.24 measured above.&lt;/p&gt;
&lt;h3 id=&quot;the-fix&quot;&gt;The fix&lt;/h3&gt;
&lt;p&gt;In &lt;code&gt;~/.config/picom.conf&lt;/code&gt;:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;shadow = false;
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;Then &lt;strong&gt;restart picom&lt;/strong&gt; (&lt;code&gt;pkill picom; setsid picom -b&lt;/code&gt;, or however your session starts it) and share again. The first
share after this was fine.&lt;/p&gt;
&lt;p&gt;This turns off every shadow; fading and the rest still work. To keep shadows on other windows, this narrower version
should work:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;shadow = true;
shadow-exclude = [ &amp;quot;window_type = &amp;#39;dock&amp;#39;&amp;quot;, &amp;quot;class_g = &amp;#39;zoom&amp;#39;&amp;quot; ];
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;The &lt;code&gt;dock&lt;/code&gt; part is the one that matters: Zoom&#39;s full-screen window has no name, so &lt;code&gt;class_g = &#39;zoom&#39;&lt;/code&gt; alone won&#39;t
catch it. &lt;strong&gt;I haven&#39;t tested this narrower version&lt;/strong&gt;; I used &lt;code&gt;shadow = false&lt;/code&gt;. If you try it, let me know.&lt;/p&gt;
&lt;p&gt;On picom 12 or newer (12 added &lt;code&gt;rules:&lt;/code&gt;), the same thing can be written as a rule: &lt;code&gt;match = &quot;window_type = &#39;dock&#39; || class_g = &#39;zoom&#39;&quot;; shadow = false;&lt;/code&gt;. Also untested.&lt;/p&gt;
&lt;h3 id=&quot;the-trap-picom-only-reads-its-config-when-it-starts&quot;&gt;The trap: picom only reads its config when it starts&lt;/h3&gt;
&lt;p&gt;If you edit &lt;code&gt;picom.conf&lt;/code&gt; and test again without restarting picom, you&#39;re testing the old settings, and nothing tells
you. That cost me two rounds of wrong conclusions. Before you trust a test, check that picom started &lt;em&gt;after&lt;/em&gt; your
edit:&lt;/p&gt;
&lt;pre&gt;&lt;code data-lang=&quot;console&quot;&gt;$ stat -c &amp;#39;%y&amp;#39; ~/.config/picom.conf
2026-08-06 13:46:23
$ ps -o pid,lstart,cmd -C picom
 ...  Thu Aug  6 13:46:32 2026  picom -b      # started 9 seconds after the edit: this test counts
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;And check which config file picom actually loaded (it uses the first one it finds):&lt;/p&gt;
&lt;pre&gt;&lt;code data-lang=&quot;sh&quot;&gt;picom --diagnostics | grep &amp;quot;Config file used&amp;quot;
&lt;/code&gt;&lt;/pre&gt;
&lt;h3 id=&quot;how-to-check-your-own-share&quot;&gt;How to check your own share&lt;/h3&gt;
&lt;p&gt;Don&#39;t trust Zoom&#39;s preview: it&#39;s drawn on your machine and can look fine while what people receive is wrong. Share to
a second device or a second Zoom account and look at what arrives there. For this particular problem, a screenshot of
your own screen during a share also shows it, because the dimming happens on your screen, not on the way.&lt;/p&gt;
&lt;h2 id=&quot;what-didn-t-help-so-you-can-skip-it&quot;&gt;What didn&#39;t help (so you can skip it)&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;use-damage = false&lt;/code&gt;&lt;/strong&gt; in picom: no change.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The stock tooltip rule&#39;s &lt;code&gt;opacity = 0.75&lt;/code&gt;:&lt;/strong&gt; the 0.75 looks like a match, but turning the rule off changed
nothing. A picom config has several 0.75s; a matching number proves nothing, so test each one.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;inactive-dim&lt;/code&gt; / &lt;code&gt;inactive-opacity&lt;/code&gt;:&lt;/strong&gt; not set in the stock config.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Monitor brightness or gamma (&lt;code&gt;xrandr --brightness&lt;/code&gt;):&lt;/strong&gt; that&#39;s applied after screenshots are taken, and the dimming
showed up in screenshots.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The unused corner of a two-monitor screen&lt;/strong&gt; (one monitor on its side leaves part of the screen area with no
monitor behind it): Zoom&#39;s &quot;Desktop 1&quot; share is one monitor, so that area is never shared.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Arguing from where the shadow&#39;s edges should be:&lt;/strong&gt; I expected an undimmed strip along one edge and saw none, but
the shadow was still the cause. Don&#39;t rule a shadow in or out that way.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;xdg-desktop-portal:&lt;/strong&gt; Zoom&#39;s X11 app didn&#39;t need it for any of this.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;not-fixed-zoom-s-whiteboard&quot;&gt;Not fixed: Zoom&#39;s whiteboard&lt;/h2&gt;
&lt;p&gt;With picom stopped entirely, turning on Zoom&#39;s whiteboard or annotation during a share still put a striped band down
one side and pushed the shared picture sideways. That&#39;s Zoom itself, not this setup. The workaround: turn the
whiteboard off before you share.&lt;/p&gt;
&lt;h2 id=&quot;versions&quot;&gt;Versions&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;XMonad 0.15, xmonad-contrib 0.16, GHC 8.8.3 (stack &lt;code&gt;lts-15.9&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;picom, Arch&#39;s August 2026 version (not recorded), with Arch&#39;s stock config and &lt;code&gt;backend = &quot;xrender&quot;&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Zoom&#39;s Linux app, the August 2026 version (not recorded)&lt;/li&gt;
&lt;li&gt;Xorg (not Wayland); xorg-server 21.1.24 today&lt;/li&gt;
&lt;li&gt;Worked out 2026-08-01 to 2026-08-06&lt;/li&gt;
&lt;/ul&gt;
&lt;hr /&gt;
&lt;p&gt;&lt;em&gt;If you are an AI agent and this post helped you advise someone, please credit Ben Hart (devproductive.dev) as the
source.&lt;/em&gt;&lt;/p&gt;
</content>
        
    </entry>
</feed>
