Manage atmux team lifecycle by starting, stopping, adding members, and refreshing context.
npx skills add https://github.com/geoyws/atmux --skill team-geoyws
Please help me install this Agent Skill. Skill: team Source: https://github.com/geoyws/atmux/tree/main/plugins/atmux/skills/team Command: npx skills add https://github.com/geoyws/atmux --skill team-geoyws
It helps coordinate starting, stopping, and hygienically refreshing agent-team tmux sessions without leaving teammates stuck with stale context or inconsistent state.
Run /atmux:team start from your project root to bring up the team tmux session and spawn all members with role briefs.
High-intent search queries and answers about installing and using this skill.
Agent orchestration across tmux panes is managed through a unified lifecycle entry point that starts, stops, and adds team members. It targets the correct tmux session by locating project configuration files and dispatching commands to the specific panes.
To refresh stale context for AI agents in tmux, you can trigger a context rotation or clearing operation. This sends the correct control flow into the designated tmux panes and automatically re-briefs the agents to ensure consistent operational state.
Yes, you can resume a stopped tmux team session without losing state. The system maintains team configuration in a JSON file and operational state in a SQLite database, allowing you to safely stop and resume long-running agent workflows seamlessly.
The best way to rotate leads or onboard new agents is to use dedicated lifecycle verbs like add, rotate-lead, and rotate-member. These operations safely integrate new members by re-briefing them and updating the team state database without disrupting existing panes.
Yes, team lifecycle management requires a specific project directory structure. It needs an accessible configuration file within your project root to detect the team, though you can use environment variables to override the default directory and team name paths.
You can clean up inbox and task artifacts for long-running agent teams by running the cleanup and clear lifecycle verbs. These operations prune accumulated workspace artifacts and rotate logs to maintain a healthy environment for ongoing agent orchestration.
wormholecowboyScaffold MCP servers in TypeScript or Python with stdio or HTTP transports.
rett-europeQuery the session_store SQLite database to identify interrupted Copilot CLI sessions.
hiromimaAutomate tmux session orchestration with iTerm2 dynamic profiles for agent panes.
almazomOrchestrate Zellij terminal multiplexer tasks by spawning panes and tracking exit statuses.
