← ClaudeAtlas

coordinatelisted

Inspect Agent Parley status, claim repository issues, and manage explicit handoffs between participants in separate worktrees. Use when working through Agent Parley or when the user requests coordination.
suneel944/agent-parley · ★ 3 · AI & Automation · score 69
Install: claude install-skill suneel944/agent-parley
# Agent Parley coordination Use the installed `agent-parley` executable. Honor `AGENT_PARLEY_HOME` when set; all participants must use the same private state root. Start with `agent-parley status`, `agent-parley participant list`, and `agent-parley issue list` in the current repository. These show ownership separately from activity and reported outcomes. If installation is part of the task, use `uv tool install agent-parley`. Contributors can use `make install` from a checkout. Do not install software merely to answer a status question. ## Select the correct lane Issue mutations infer identity from the current worktree. Only act from this session's assigned lane, never impersonate a peer with `--repo` or by changing to its directory. If this session is not launcher-managed, explain that setup and native hooks require launching through Agent Parley in separate user terminals, one terminal per participant: ```sh agent-parley run claude --repo /path/to/repository agent-parley run codex --repo /path/to/repository agent-parley run claude-2 --provider claude --credentials account-2 --repo /path/to/repository ``` A project can hold up to 32 participants, including several of the same provider under different accounts. Use `list_participants` over MCP, or `agent-parley participant list`, to see who is currently addressable. Do not launch nested interactive agents from a tool call or silently move an existing session. The plugin supplies this workflow; the launcher supplies wor