session-chatlisted

# Session Chat Use this skill when the user asks how session-chat works, which command to use, how to configure receiving panes, or how to troubleshoot delivery. ## Choosing A Command | Use case | Command | Notes | | --- | --- | --- | | Short status, acknowledgement, or question | `$session-chat:send <pane> <message>` | Single line only, up to `SESSION_CHAT_SEND_MAX_LEN` characters. Default max is 1024. | | Multi-line task, code, logs, or detailed report | `$session-chat:dispatch <pane> <task>` | Writes the full prompt to a trusted message file and sends a notification. | | Work that should be tracked and resumed from a file | `$session-chat:dispatch <pane> <task>` | Receiver sees the file path, line count, and message id. | | Unsure whether content might contain newlines or shell-sensitive text | `$session-chat:dispatch <pane> <task>` | Avoids send payload limits and inline quoting ambiguity. | | Reply or acknowledgement to an incoming message | `$session-chat:reply <pane> <id> <message>` | Transport adds `[re:<id>]` exactly once; do not type the token manually. | ## Recipient Prerequisites - The recipient must be running inside tmux. - The recipient pane must have a unique registered name, either from `$session-chat:whoami <name>` or best-effort SessionStart auto-naming from the transcript's first user message. - Use `$session-chat:panes` to inspect the current tmux session, or `$session-chat:panes all` when the target may be in another tmux session. - In Codex, the pl