Skip to content

skill: put the zellij review pane where its caller is - #687

Merged
agavra merged 1 commit into
agavra:mainfrom
thiblahute:pr/zellij-pane-placement
Sep 11, 2026
Merged

agavra merged 1 commit into
agavra:mainfrom
thiblahute:pr/zellij-pane-placement

Conversation

@thiblahute

Copy link
Copy Markdown
Contributor

Three fixes to the zellij wrapper for agent-launched reviews:

  • --near-current-pane: the pane used to open beside whatever was focused — the tab the human is looking at — instead of the caller's pane.
  • Called from a floating overlay, a stacked pane opens hidden behind the existing stack; fall back to a right split there.
  • The already-running check now only refuses when the running tuicr is reviewing the same repository (by /proc cwd), not any tuicr anywhere.

--near-current-pane opens the review beside the pane the wrapper runs
in, not whichever tab the human is looking at. A stacked pane is
invisible when the caller is a floating overlay, so fall back to a right
split there. And only refuse to launch when the running tuicr is
reviewing this repository — one on another checkout is no reason.
@agavra
agavra merged commit 4a9bda2 into agavra:main Sep 11, 2026
5 checks passed
FSMaxB added a commit to FSMaxB/config that referenced this pull request Sep 16, 2026
Port of agavra/tuicr#687 to the tuicr_open tool: pass --near-current-pane so
the review opens beside pi's pane instead of the focused tab, and fall back to
a right split when pi itself runs in a floating pane, where a stacked pane
would open hidden behind the existing stack.
FSMaxB added a commit to FSMaxB/config that referenced this pull request Sep 21, 2026
Port of agavra/tuicr#687 to the tuicr_open tool: pass --near-current-pane so
the review opens beside pi's pane instead of the focused tab, and fall back to
a right split when pi itself runs in a floating pane, where a stacked pane
would open hidden behind the existing stack.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants