Route collaborative room traffic across tmux and zellij panes with deterministic headers.
npx skills add https://github.com/joshka0/foxctl --skill foxctl-tmux
Please help me install this Agent Skill. Skill: foxctl-tmux Source: https://github.com/joshka0/foxctl/tree/main/configs/skills-pack/foxctl-tmux Command: npx skills add https://github.com/joshka0/foxctl --skill foxctl-tmux
foxctl-tmux resolves confusion during collaborative agent sessions by mapping legacy room viewing and tmux mux commands to the current room viewer layer, ensuring operators route room traffic correctly across tmux/zellij panes.
Use case: you reopen an existing zellij session and need to ensure each pane is properly joined to the correct room/role so agents can exchange messages and produce durable knowledge reliably.
Ask foxctl-tmux to show the correct pane-to-room binding steps for your current tmux or zellij setup and how to send a review message using the tmux-bridge format.
High-intent search queries and answers about installing and using this skill.
To bind panes to a specific agent room, you must explicitly assign room membership using designated variables rather than inferring it from shared session names. This ensures agents can correctly route collaborative traffic and exchange messages reliably.
Agent messages fail to route correctly across tmux panes when deterministic send header formatting is missing or pane bindings are broken. You need to enforce consistent message headers and run explicit pane join checks to restore parseable traffic.
No, you cannot use a shared tmux session name to infer room membership. Panes must be explicitly bound to room roles using ROOM, ACTOR, ROLE, PANE, and SESSION variables to ensure correct message delivery and agent orchestration.
The best way to repair pane bindings in an existing zellij session is to run explicit rebind checks based on session variables. This restores correct routing for collaborative room traffic if panes have moved or detached.
To save tmux agent interactions durably, you should promote derived facts only through a ContextWiki or Obsidian flow rather than storing raw pane dumps. This filters relevant information after reviewing tmux exchanges for reliable knowledge retention.
Yes, foxctl-tmux works with zellij by providing a legacy compatibility layer that maps historical mux commands to the current room viewer layer. It ensures collaborative room traffic routes correctly across both tmux and zellij panes.
joshka0Route legacy tmux/zellij room viewer commands to current guidance.
joshka0Bundle context architecture surfaces and transcript-derived continuity into a single pack.
joshka0Manages foxctl room membership, inbox tasks, lifecycle actions, and durable chain-aware replies for participant agents.
delorenjGuide Zellij layout customization for panes, tabs, and session configurations.
