foxctl-room-view

Inspect tmux/zellij panes and PTY output to diagnose viewer-layer room issues.

3|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/joshka0/foxctl --skill foxctl-room-view
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: foxctl-room-view
Source: https://github.com/joshka0/foxctl/tree/main/configs/skills-pack/foxctl-room-view
Command: npx skills add https://github.com/joshka0/foxctl --skill foxctl-room-view

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you separate viewer/presentation-layer issues (tmux/zellij panes and PTY output handling) from room delivery/runtime problems, so you can quickly identify why what you see is wrong—or why delivery fails.

Core Features & Use Cases

  • Pane & PTY inspection: Inspect viewer placement and read PTY output for a specific pane target to validate what the participant runtime is actually emitting.
  • Viewer-layer manipulation: Create viewer panes, relabel/adjust viewer placement, and perform one-off manual “pokes” into panes for controlled debugging.
  • Transport vs presentation debugging: Use room status and room-scoped event timelines as the source of truth, while treating mux/viewer behavior as an attachment layer rather than delivery authority.
  • Operational debugging boundaries: Provide clear rules for when to debug the viewer versus when to debug room transport, membership, delivery traces, or loop state.

Quick Start

Run foxctl room status <room-id>, then use foxctl mux list and foxctl mux read <target> --lines 80 to confirm viewer placement and PTY output for the participant.

Frequently Asked Questions about foxctl-room-view

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug tmux pane output for room participants?

To debug tmux pane output for room participants, inspect viewer placement using mux list and read PTY output for the specific pane target. This validates what the participant runtime is actually emitting, separating viewer presentation issues from room delivery failures.

Why does my zellij viewer show misaligned output when room delivery succeeds?

Viewer misalignment happens when mux or viewer attachments behave inconsistently with room transport. Treat room status and last_delivery_trace as the source of truth, while debugging the viewer pane and PTY output as a non-authoritative presentation layer.

What is the best way to inspect PTY output in multi-agent rooms?

The best way to inspect PTY output in multi-agent rooms is to use mux read commands with a specific target and line count. This allows you to perform one-off manual pokes into panes for controlled debugging of participant presentation.

Can I relabel or adjust viewer placement during room debugging?

Yes, you can relabel and adjust viewer placement during room debugging. The Skill supports creating viewer panes and manipulating viewer-layer components to help diagnose presentation issues without altering underlying room delivery or loop state.

When should I debug room transport instead of the tmux viewer layer?

Debug room transport instead of the tmux viewer layer when room status or last_delivery_trace indicates delivery failures. If delivery invariants hold but output is wrong, debug the viewer; if traces show transport issues, debug room membership or runtime.