Tmux Project ManagerInstall

Overview

The "Tmux Project Manager" node facilitates managing software projects and coordinating team members within tmux terminal multiplexer sessions. It enables project initialization, task assignment, progress tracking, quality validation, team member creation, and conducting daily standups by interacting with tmux sessions and sending messages to specialized subagents (e.g., developers, QA engineers) running in tmux windows.

This node is beneficial for teams using tmux-based workflows to organize parallel workstreams and automate communication with AI-powered or scripted agents inside tmux windows. For example, a project manager can create a new project session with predefined team roles, assign tasks to specific agents, gather status updates during daily standups, and validate code quality—all orchestrated through tmux.

Practical scenarios include:

• Automating task delegation to different team roles in a tmux environment.
• Collecting consolidated progress reports from multiple tmux windows representing team members.
• Running quality checks by prompting the project manager agent to perform reviews.
• Adding new team members dynamically as new tmux windows with role-specific briefings.
• Conducting structured daily standup meetings by querying each team member window.

Properties

(Note: Only the "Project Session" property applies to the "Daily Standup" operation as per the provided input properties.)

Output

The output JSON object for the "Daily Standup" operation includes:

• success (boolean): Indicates if the standup was conducted successfully.
• projectSession (string): The tmux session name used.
• standupResults (array): An array of objects, each representing a team member's window with:
  • window (string): The window name.
  • index (number): The window index.
  • status (string): The last 20 lines of the captured content from that window, containing the team member’s standup response.
• teamSize (number): Number of windows (team members plus PM) in the tmux session.
• timestamp (string): ISO timestamp when the standup was completed.

The node does not output binary data.

Dependencies

• Requires access to tmux on the host system to manage sessions and windows.
• Uses an internal utility ("TmuxBridge") to interact with tmux sessions, send messages, and capture window content.
• Optionally uses credentials that may specify external script directories or project base paths.
• Relies on executing shell commands (tmux send-keys, tmux new-window) via child processes.
• No direct external API calls beyond tmux and local environment interaction.

Troubleshooting

• Common issues:

  • The specified tmux session (Project Session) might not exist, causing errors like "Session [name] not found".
  • Delays in receiving responses from team member windows could cause incomplete or missing standup data.
  • Permissions or environment restrictions preventing execution of tmux commands.
  • Misconfiguration of credentials or missing external scripts directory if required.

• Error messages and resolutions:

  • "Session [name] not found": Verify the tmux session name is correct and active before running the node.
  • "Failed to conduct standup: ...": Check tmux availability, permissions, and that all team member windows respond properly.
  • Timeout or empty responses: Ensure that the agents in tmux windows are running and able to receive/send messages.
  • If the node throws errors related to command execution, confirm that the n8n instance has permission to run shell commands and tmux is installed.

Links and References

• tmux official documentation
• n8n Custom Node Development Guide
• General info on terminal multiplexers and automation scripting

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