mirror of
https://github.com/getcompanion-ai/co-mono.git
synced 2026-04-15 05:02:07 +00:00
2.8 KiB
2.8 KiB
| description |
|---|
| Coordinate multiple agents working on a project using shared task lists and messaging via tmux or Zellij. |
Agent Teams
Coordinate multiple agents working on a project using shared task lists and messaging via tmux or Zellij.
Workflow
- Create a team: Use
team_create(team_name="my-team"). - Spawn teammates: Use
spawn_teammateto start additional agents. Give them specific roles and initial prompts. - Manage tasks:
task_create: Define work for the team.task_list: List all tasks to monitor progress or find available work.task_get: Get full details of a specific task by ID.task_update: Update a task's status (pending,in_progress,completed,deleted) or owner.
- Communicate: Use
send_messageto give instructions or receive updates. Teammates should useread_inboxto check for messages. - Monitor: Use
check_teammateto see if they are still running and if they have sent messages back. - Cleanup:
force_kill_teammate: Forcibly stop a teammate and remove them from the team.process_shutdown_approved: Orderly removal of a teammate after they've finished.team_delete: Remove a team and all its associated data.
Teammate Instructions
When you are spawned as a teammate:
- Your status bar will show "Teammate: name @ team".
- You will automatically start by calling
read_inboxto get your initial instructions. - Regularly check
read_inboxfor updates from the lead. - Use
send_messageto "team-lead" to report progress or ask questions. - Update your assigned tasks using
task_update. - If you are idle for more than 30 seconds, you will automatically check your inbox for new messages.
Best Practices for Teammates
- Update Task Status: As you work, use
task_updateto set your tasks toin_progressand thencompleted. - Frequent Communication: Send short summaries of your work back to
team-leadfrequently. - Context Matters: When you finish a task, send a message explaining your results and any new files you created.
- Independence: If you get stuck, try to solve it yourself first, but don't hesitate to ask
team-leadfor clarification. - Orderly Shutdown: When you've finished all your work and have no more instructions, notify the lead and wait for shutdown approval.
Best Practices for Team Leads
- Clear Assignments: Use
task_createfor all significant work items. - Contextual Prompts: Provide enough context in
spawn_teammatefor the teammate to understand their specific role. - Task List Monitoring: Regularly call
task_listto see the status of all work. - Direct Feedback: Use
send_messageto provide course corrections or new instructions to teammates. - Read Config: Use
read_configto see the full team roster and their current status.