Tmux Project ManagerInstall

Overview

The Tmux Project Manager node facilitates managing software development projects by coordinating team members and tasks within tmux terminal multiplexing sessions. It enables project initialization, task assignment, progress tracking, quality validation, team member creation, and daily standup collection—all orchestrated through tmux windows representing different roles or agents.

This node is beneficial in scenarios where teams use tmux sessions to parallelize workstreams and want automated coordination and status reporting via scripted interactions with these sessions. For example:

• Initializing a new project environment with predefined team roles.
• Assigning specific tasks to developers or QA engineers inside tmux windows.
• Gathering real-time progress updates from multiple tmux windows.
• Running quality checks like code reviews or test coverage validations.
• Adding new team members dynamically during the project lifecycle.
• Conducting daily standups by collecting status reports from all team members.

Properties

Output

The output JSON structure for the Get Progress operation includes:

• success (boolean): Indicates if the progress retrieval was successful.
• projectSession (string): The tmux session name queried.
• pmStatus (string): The latest captured content from the project manager's main window, summarizing overall project status.
• teamStatus (array): An array of objects representing each team member window (excluding the main PM window), each containing:
  • window (string): The window name.
  • index (number): The window index.
  • lastActivity (string): The last lines of captured output from that window, showing recent activity or status.
• windowCount (number): Total number of windows in the tmux session.
• timestamp (string): ISO timestamp when the data was retrieved.

This output provides a snapshot of the current project progress by aggregating status messages from the project manager and individual team members' tmux windows.

Dependencies

• Requires access to a tmux environment where project sessions and windows are managed.
• Uses an internal utility bridge to interact with tmux sessions, send commands, and capture window content.
• Optionally uses credentials that may specify external script directories or base paths for projects.
• Relies on the ability to execute shell commands (tmux CLI) on the host system.
• No direct external API dependencies beyond the tmux environment and local execution context.

Troubleshooting

• Session Not Found Error: If the specified tmux session does not exist, the node throws an error indicating the session was not found. Ensure the correct session name is provided and that the tmux session is active.
• Timeouts Waiting for Responses: The node waits briefly after sending requests to tmux windows to allow responses. If responses are delayed or missing, consider increasing wait times or verifying that the tmux windows are responsive.
• Permission Issues: Since the node executes shell commands, ensure the n8n process has sufficient permissions to run tmux commands and access the required sessions.
• Malformed Output Capture: Captured window content is parsed by splitting lines; unexpected output formats may cause incomplete or confusing status summaries.
• Credential Misconfiguration: If using optional credentials for external scripts or base paths, verify these are correctly configured to avoid path resolution errors.

Links and References

• tmux Manual
• n8n Custom Node Development
• Node.js child_process.execSync

This summary focuses exclusively on the "Get Progress" operation of the Tmux Project Manager node as requested.