From 3731a80384f5e2b7d3343eb3e4999f626bbc7f91 Mon Sep 17 00:00:00 2001 From: Igor Soarez Date: Tue, 20 Oct 2026 13:04:18 +0300 Subject: pi extension: identify the pane from TMUX_PANE the extension asked tmux for "the current pane", which resolves to the session's active pane, not the pane pi runs in, so agents in background windows reported their state onto another pane. tmux sets TMUX_PANE for every process it starts in a pane; use it. e2e step 12 loads the shipped extension with a fake pi from a pane that is not its session's active pane and asserts the report lands there; it fails against the previous extension. hook reports log at info again. --- crates/dinggerd/src/hooks.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'crates/dinggerd/src/hooks.rs') diff --git a/crates/dinggerd/src/hooks.rs b/crates/dinggerd/src/hooks.rs index 40f0f20..524fb2d 100644 --- a/crates/dinggerd/src/hooks.rs +++ b/crates/dinggerd/src/hooks.rs @@ -124,7 +124,7 @@ fn handle_stream(stream: UnixStream) { continue; } }; - debug!(pane = %params.pane_id, ?state, "hook report"); + info!(pane = %params.pane_id, ?state, "hook report"); { let mut reports = reports(); let pane = reports.entry(params.pane_id).or_default(); -- cgit v1.2.3