Current behavior
When multiple Herdr sessions are attached at the same time — one local session plus two (or more) --remote <host> sessions — clipboard image paste does not seem to be aware of which of the three hosts the currently-focused pane actually belongs to.
In practice, once any remote session has been attached during the run, subsequent image pastes (e.g. Cmd+V of a screenshot) keep landing as a temp file path on one fixed remote host (/tmp/cmux-drop-*.jpg style path), even when:
- the focused pane is the local session, or
- the focused pane belongs to the other remote host (remote2, not remote1).
This means an agent/tool running in the local pane, or in remote2, tries to read an image path that doesn't exist on its own filesystem, because the file was actually written to remote1 (or wherever the "last used"/default target host happens to be).
Expected behavior
Clipboard image paste should resolve the destination host from the currently focused pane's session, not from a single cached/default remote target:
- Local session focused → image written to a local tmp path.
- Remote1 pane focused → image written to remote1's tmp path.
- Remote2 pane focused → image written to remote2's tmp path.
Setup
- 1 local Herdr session
- 2 separate
--remote <host> sessions attached concurrently (different remote hosts)
- Paste behavior tested by copying a screenshot/image to the system clipboard and pasting into panes belonging to each of the three sessions in turn
Why this matters
With herdr increasingly supporting multiple remote servers in one sidebar (see #334), this ambiguity gets worse as more hosts are attached — users/agents can silently receive a path for the wrong machine with no error, only a downstream "file not found" from whatever they paste into.
Additional context
I don't see an existing issue that covers this specific 1-local + N-remote host-resolution ambiguity for clipboard image paste (closest related issues I found: #3975, #828, #1741, #334, #2448 — none of which describe routing to the wrong host among 3+ concurrently attached sessions specifically).
Current behavior
When multiple Herdr sessions are attached at the same time — one local session plus two (or more)
--remote <host>sessions — clipboard image paste does not seem to be aware of which of the three hosts the currently-focused pane actually belongs to.In practice, once any remote session has been attached during the run, subsequent image pastes (e.g. Cmd+V of a screenshot) keep landing as a temp file path on one fixed remote host (
/tmp/cmux-drop-*.jpgstyle path), even when:This means an agent/tool running in the local pane, or in remote2, tries to read an image path that doesn't exist on its own filesystem, because the file was actually written to remote1 (or wherever the "last used"/default target host happens to be).
Expected behavior
Clipboard image paste should resolve the destination host from the currently focused pane's session, not from a single cached/default remote target:
Setup
--remote <host>sessions attached concurrently (different remote hosts)Why this matters
With
herdrincreasingly supporting multiple remote servers in one sidebar (see #334), this ambiguity gets worse as more hosts are attached — users/agents can silently receive a path for the wrong machine with no error, only a downstream "file not found" from whatever they paste into.Additional context
I don't see an existing issue that covers this specific 1-local + N-remote host-resolution ambiguity for clipboard image paste (closest related issues I found: #3975, #828, #1741, #334, #2448 — none of which describe routing to the wrong host among 3+ concurrently attached sessions specifically).