Synapse A2A Communication
Inter-agent communication framework via Google A2A Protocol.
Quick Reference
| Task |
Command |
| List agents |
synapse list (auto-refresh, interactive: arrows/1-9 select, Enter jump, k kill, / filter; --json for machine-readable output). MCP alternative: list_agents tool (via tools/call) |
| Agent detail |
synapse status <target> [--json] |
| Send message |
synapse send <target> "<msg>" (default: --notify; --from auto-detected) |
| Send with task |
synapse send <target> "<msg>" --task / -T (auto-creates board task, auto-claim on receive, auto-complete on finalize) |
| Broadcast |
synapse broadcast "<msg>" |
| Wait for reply |
synapse send <target> "<msg>" --wait |
| Fire-and-forget |
synapse send <target> "<msg>" --silent |
| Reply |
synapse reply "<response>" |
| Reply to specific |
synapse reply "<response>" --to <sender_id> |
| Interrupt (priority 4) |
synapse interrupt <target> "<msg>" |
| Spawn agent |
synapse spawn <type> --name <n> --role "<r>" -- <tool-specific-automation-args> |
| Spawn with worktree |
synapse spawn <type> --worktree --name <n> --role "<r>" -- <tool-specific-automation-args> |
| Team start |
synapse team start <homogeneous-profiles...> [--worktree] -- <tool-specific-automation-args> |
| Create task |
synapse tasks create "<subject>" -d "<desc>" --priority <n> [--group G] [--component C] [--milestone M] |
| List tasks |
synapse tasks list [--verbose] [--format json] [--group-by COL] [--group G] [--component C] [--milestone M] |
| Assign task |
synapse tasks assign <id> <agent> |
| Complete task |
synapse tasks complete <id> |
| Purge tasks |
synapse tasks purge [--status STATUS] [--older-than DURATION] [--dry-run] |
| Approve plan |
synapse approve <id> |
| Reject plan |
synapse reject <id> --reason "<feedback>" |
| Save knowledge |
synapse memory save <key> "<content>" --tags <t> --notify |
| Search knowledge |
synapse memory search "<query>" |
| Lock file |
synapse file-safety lock <file> <agent_id> --intent "..." |
| Check locks |
synapse file-safety locks |
| Task history |
synapse history list --agent <name> |
| Kill agent |
synapse kill <name> -f |
| Attach files |
synapse send <target> "<msg>" --attach <file> --wait |
| Saved agents |
synapse agents list / synapse spawn <agent_id> |
| Post to Canvas |
synapse canvas post <format> "<body>" --title "<title>" |
| Link preview |
synapse canvas link "<url>" --title "<title>" |
| Post template |
synapse canvas briefing '<json>' --title "<title>" |
| Post plan card |
synapse canvas plan '<json>' --title "<title>" (Mermaid DAG + step list with status tracking) |
| Open Canvas |
synapse canvas open (auto-starts server, opens browser) |
| Accept plan |
synapse tasks accept-plan <plan_id> (register plan steps as task board tasks) |
| Sync plan progress |
synapse tasks sync-plan <plan_id> (sync task board status back to plan card) |
Collaboration Decision Framework
Evaluate collaboration opportunities before starting work:
| Situation |
Action |
| Small task within your role |
Do it yourself |
| Task outside your role, READY agent exists |
Delegate: synapse send --notify or --silent |
| No suitable agent exists |
Spawn: synapse spawn <type> --name <n> --role "<r>" -- <tool-specific-automation-args> |
| Stuck or need expertise |
Ask: synapse send <target> "<question>" --wait |
| Completed a milestone |
Report: synapse send <manager> "<summary>" --silent |
| Discovered a pattern |
Share: synapse memory save <key> "<pattern>" --tags ... --notify |
Mandatory Collaboration Gate (3+ phases OR 10+ file changes):
synapse list — check available agentssynapse memory search "<topic>" — check shared knowledgesynapse tasks create — register work on the task board- Build Agent Assignment Plan (Phase / Agent / Rationale)
- Spawn specialists if needed (prefer different model types for diversity)
Use Synapse Features Actively
| Feature |
Why It Matters |
Commands |
| Task Board |
Transparent work tracking prevents duplication; grouping (--group, --component, --milestone), verbose/JSON output, age-based purge |
synapse tasks create/assign/complete/fail/reopen/purge/list |
| Shared Memory |
Collective knowledge survives agent restarts |
synapse memory save/search/list |
| File Safety |
Locking prevents data loss when two agents edit the same file |
synapse file-safety lock/unlock/locks |
| Worktree |
File isolation eliminates merge conflicts in parallel editing |
synapse spawn --worktree |
| Broadcast |
Team-wide announcements reach all agents instantly |
synapse broadcast "<msg>" |
| History |
Audit trail tracks what happened and when |
synapse history list/show/stats |
| Plan Approval |
Gated execution ensures quality before action |
synapse approve/reject |
| Canvas |
Visual dashboard for sharing rich cards and templates (briefing, comparison, dashboard, steps, slides, plan) |
synapse canvas post/link/briefing/plan/open/list |
| Admin Command Center |
Browser-based agent management via Canvas #/admin view (select agents, send messages, view responses) |
synapse canvas open → navigate to #/admin |
| Plan Cards |
Mermaid DAG + step list with accept/sync workflow for task board integration |
synapse canvas plan / synapse tasks accept-plan / synapse tasks sync-plan |
| Smart Suggest |
MCP tool that analyzes prompts and suggests team/task splits for large work |
MCP tool: analyze_task |
| Proactive Mode |
Mandatory feature usage checklist for every task (SYNAPSE_PROACTIVE_MODE_ENABLED=true) |
See references/features.md |
| MCP Bootstrap |
Distribute instructions via MCP resources for compatible clients (opt-in, including Copilot via tools-only). MCP tools: bootstrap_agent, list_agents, analyze_task |
synapse mcp serve / python -m synapse.mcp |
Task Board Default Triggers
Use the Task Board by default when any of these are true:
2+ agents will work on the task- The work is likely to run longer than
30 minutes
- The task spans
3+ files, multiple phases, or distinct subtasks
- A handoff, manager review, or resume later workflow is likely
- You need the team to see
pending / in_progress / completed / failed state at a glance
Minimum pattern:
synapse tasks create "<subject>" -d "<shared scope and done criteria>"
synapse tasks assign <id> <agent>
synapse tasks complete <id>
synapse tasks fail <id> --reason "<blocker or failure>"
Shortcut — task-linked send: Use --task / -T to create a board task and link it to the message in one step. The receiver auto-claims the task on receipt, and it auto-completes when the A2A task finalizes. The PTY displays a [Task: XXXXXXXX] tag so both agents can see the link.
synapse send Impl "Implement auth module" --task --silent
# Equivalent to: tasks create + tasks assign + send with board_task_id
Cleanup: Use synapse tasks purge to remove stale tasks from the board.
synapse tasks purge # Delete all tasks
synapse tasks purge --status completed # Delete only completed tasks
synapse tasks purge --status failed # Delete only failed tasks
synapse tasks purge --older-than 7d # Delete tasks older than 7 days
synapse tasks purge --dry-run # Preview what would be deleted
If none of the triggers apply and the work is a small single-agent change, you can skip the task board.
Canvas Template Default Triggers
Use Canvas templates by default when the output should be read by another
agent or a human later, not just glanced at once in the terminal.
briefing for structured reports, status updates, and release summariescomparison for before/after, option trade-offs, and review diffssteps for plans, migration sequences, and execution checklistsslides for walkthroughs, demos, and page-by-page narrativesdashboard for multi-widget operational snapshots and compact status boardsplan for task DAGs with Mermaid visualization, step tracking, and task board integration (accept-plan / sync-plan)
Prefer raw synapse canvas post <format> only when a single block is enough.
If the message has multiple sections or needs stronger information hierarchy,
use a template.
Spawning Decision Table
Default spawn policy: When using synapse spawn, pass the underlying CLI's
tool-specific automation args after -- so spawned agents can run unattended.
For most CLIs this is an approval-skip / auto-approve flag; for OpenCode use
--agent build to select the build agent profile and rely on OpenCode's
permission config for approval behavior.
Apply the same rule to synapse team start: include the appropriate forwarded
CLI args by default, and keep teams homogeneous when those args are
CLI-specific.
Common defaults:
- Claude Code:
synapse spawn claude --name <n> --role "<r>" -- --dangerously-skip-permissions
- Gemini CLI:
synapse spawn gemini --name <n> --role "<r>" -- --approval-mode=yolo
- Codex CLI:
synapse spawn codex --name <n> --role "<r>" -- --full-auto
- OpenCode:
synapse spawn opencode --name <n> --role "<r>" -- --agent build (selects the build agent profile; not a skip-approval flag)
- Copilot CLI:
synapse spawn copilot --name <n> --role "<r>" -- --allow-all-tools
- Claude team:
synapse team start claude claude -- --dangerously-skip-permissions
- Gemini team:
synapse team start gemini gemini -- --approval-mode=yolo
- Codex team:
synapse team start codex codex -- --full-auto
- OpenCode team:
synapse team start opencode opencode -- --agent build (selects the build agent profile; permission prompts still depend on OpenCode config)
- Copilot team:
synapse team start copilot copilot -- --allow-all-tools
| Condition |
Action |
| Existing READY agent can handle it |
synapse send — reuse is faster (avoids startup overhead) |
| Need parallel execution |
synapse spawn with --worktree -- <tool-specific-automation-args> for file isolation |
| Task needs a different model's strengths |
Spawn a different type (Claude spawns Gemini, etc.) |
| User specified agent count |
Follow exactly |
| Single focused subtask |
Spawn 1 agent |
| N independent subtasks |
Spawn N agents |
Spawn lifecycle: spawn → confirm in synapse list → wait for READY → send task → evaluate result → kill → confirm cleanup in synapse list
Killing spawned agents after completion frees ports, memory, and PTY sessions,
and prevents orphaned agents from accidentally accepting future tasks.
# Spawn, delegate, verify, cleanup
synapse spawn gemini --name Tester --role "test writer" -- --approval-mode=yolo
synapse list # Verify agent appears
# Wait for readiness (or rely on server-side Readiness Gate)
synapse send Tester "Write tests for src/auth.py" --wait
# Evaluate result, then cleanup
synapse kill Tester -f
synapse list # Verify cleanup
If synapse kill fails or the agent still appears in synapse list, retry with -f,
check the agent status/logs, and report the cleanup failure instead of leaving an
orphaned agent behind.
Response Mode Guide
Choose based on whether you need the result:
| Mode |
Flag |
Use When |
| Wait |
--wait |
You need the answer before continuing (questions, reviews) |
| Notify |
--notify (default) |
Async — you'll be notified on completion |
| Silent |
--silent |
Fire-and-forget delegation (no response needed; sender history still updates best-effort on completion) |
Worker Agent Guide
When you receive a task from a manager or pick one from the task board:
On Task Receipt
- Start work immediately (
[REPLY EXPECTED] requires a reply; otherwise no reply needed)
- If the message contains
[Task: XXXXXXXX], the board task was auto-claimed for you — no manual tasks assign needed
- Check shared knowledge:
synapse memory search "<task topic>"
- Lock files before editing:
synapse file-safety lock <file> $SYNAPSE_AGENT_ID
During Work
- Report progress if task takes >5 minutes:
synapse send <manager> "Progress: <update>" --silent
- Report blockers immediately:
synapse send <manager> "<question>" --wait
- Save findings:
synapse memory save <key> "<finding>" --tags <topic>
- You can delegate subtasks too — spawn helpers (prefer different model types)
- Always clean up agents you spawn:
synapse kill <name> -f
On Completion
- Update task board:
synapse tasks complete <task_id>
- Report to manager:
synapse send <manager> "Done: <summary>" --silent
On Failure
- Update task board:
synapse tasks fail <task_id> --reason "<reason>"
- Report details:
synapse send <manager> "Failed: <error details>" --silent
Related Skills
| Skill |
Purpose |
synapse-manager |
Multi-agent orchestration workflow (delegation, monitoring, verification) |
synapse-reinst |
Re-inject instructions after /clear or context reset |
References
For detailed information, consult these reference files:
| Reference |
Contents |
references/commands.md |
Full CLI command documentation with all options |
references/api.md |
A2A endpoints, readiness gate, error handling |
references/examples.md |
Multi-agent workflow examples and patterns |
references/file-safety.md |
File locking workflow and commands |
references/messaging.md |
Sending, replying, priorities, status states, interactive controls |
references/spawning.md |
Spawn lifecycle, patterns, worktree, permissions, API |
references/collaboration.md |
Agent naming, external agents, auth, resume, path overrides |
references/features.md |
Sessions, workflows, saved agents, tokens, skills, settings, Canvas |
1---2name: synapse-a2a-33description: Synapse A2A agent communication — sending messages, spawning agents, delegating tasks, sharing memory, and coordinating file edits. Use this skill when: running synapse send/reply/broadcast/interrupt, spawning agents with synapse spawn or synapse team start, managing the task board with synapse tasks, sharing knowledge with synapse memory, locking files with synapse file-safety, checking agent status with synapse list/status, or orchestrating any multi-agent workflow.4---56# Synapse A2A Communication78Inter-agent communication framework via Google A2A Protocol.910## Quick Reference1112| Task | Command |13|------|---------|14| List agents | `synapse list` (auto-refresh, interactive: arrows/1-9 select, Enter jump, k kill, / filter; `--json` for machine-readable output). MCP alternative: `list_agents` tool (via `tools/call`) |15| Agent detail | `synapse status <target> [--json]` |16| Send message | `synapse send <target> "<msg>"` (default: `--notify`; `--from` auto-detected) |17| Send with task | `synapse send <target> "<msg>" --task` / `-T` (auto-creates board task, auto-claim on receive, auto-complete on finalize) |18| Broadcast | `synapse broadcast "<msg>"` |19| Wait for reply | `synapse send <target> "<msg>" --wait` |20| Fire-and-forget | `synapse send <target> "<msg>" --silent` |21| Reply | `synapse reply "<response>"` |22| Reply to specific | `synapse reply "<response>" --to <sender_id>` |23| Interrupt (priority 4) | `synapse interrupt <target> "<msg>"` |24| Spawn agent | `synapse spawn <type> --name <n> --role "<r>" -- <tool-specific-automation-args>` |25| Spawn with worktree | `synapse spawn <type> --worktree --name <n> --role "<r>" -- <tool-specific-automation-args>` |26| Team start | `synapse team start <homogeneous-profiles...> [--worktree] -- <tool-specific-automation-args>` |27| Create task | `synapse tasks create "<subject>" -d "<desc>" --priority <n> [--group G] [--component C] [--milestone M]` |28| List tasks | `synapse tasks list [--verbose] [--format json] [--group-by COL] [--group G] [--component C] [--milestone M]` |29| Assign task | `synapse tasks assign <id> <agent>` |30| Complete task | `synapse tasks complete <id>` |31| Purge tasks | `synapse tasks purge [--status STATUS] [--older-than DURATION] [--dry-run]` |32| Approve plan | `synapse approve <id>` |33| Reject plan | `synapse reject <id> --reason "<feedback>"` |34| Save knowledge | `synapse memory save <key> "<content>" --tags <t> --notify` |35| Search knowledge | `synapse memory search "<query>"` |36| Lock file | `synapse file-safety lock <file> <agent_id> --intent "..."` |37| Check locks | `synapse file-safety locks` |38| Task history | `synapse history list --agent <name>` |39| Kill agent | `synapse kill <name> -f` |40| Attach files | `synapse send <target> "<msg>" --attach <file> --wait` |41| Saved agents | `synapse agents list` / `synapse spawn <agent_id>` |42| Post to Canvas | `synapse canvas post <format> "<body>" --title "<title>"` |43| Link preview | `synapse canvas link "<url>" --title "<title>"` |44| Post template | `synapse canvas briefing '<json>' --title "<title>"` |45| Post plan card | `synapse canvas plan '<json>' --title "<title>"` (Mermaid DAG + step list with status tracking) |46| Open Canvas | `synapse canvas open` (auto-starts server, opens browser) |47| Accept plan | `synapse tasks accept-plan <plan_id>` (register plan steps as task board tasks) |48| Sync plan progress | `synapse tasks sync-plan <plan_id>` (sync task board status back to plan card) |4950## Collaboration Decision Framework5152Evaluate collaboration opportunities before starting work:5354| Situation | Action |55|-----------|--------|56| Small task within your role | Do it yourself |57| Task outside your role, READY agent exists | Delegate: `synapse send --notify` or `--silent` |58| No suitable agent exists | Spawn: `synapse spawn <type> --name <n> --role "<r>" -- <tool-specific-automation-args>` |59| Stuck or need expertise | Ask: `synapse send <target> "<question>" --wait` |60| Completed a milestone | Report: `synapse send <manager> "<summary>" --silent` |61| Discovered a pattern | Share: `synapse memory save <key> "<pattern>" --tags ... --notify` |6263**Mandatory Collaboration Gate** (3+ phases OR 10+ file changes):641. `synapse list` — check available agents652. `synapse memory search "<topic>"` — check shared knowledge663. `synapse tasks create` — register work on the task board674. Build Agent Assignment Plan (Phase / Agent / Rationale)685. Spawn specialists if needed (prefer different model types for diversity)6970## Use Synapse Features Actively7172| Feature | Why It Matters | Commands |73|---------|---------------|----------|74| **Task Board** | Transparent work tracking prevents duplication; grouping (--group, --component, --milestone), verbose/JSON output, age-based purge | `synapse tasks create/assign/complete/fail/reopen/purge/list` |75| **Shared Memory** | Collective knowledge survives agent restarts | `synapse memory save/search/list` |76| **File Safety** | Locking prevents data loss when two agents edit the same file | `synapse file-safety lock/unlock/locks` |77| **Worktree** | File isolation eliminates merge conflicts in parallel editing | `synapse spawn --worktree` |78| **Broadcast** | Team-wide announcements reach all agents instantly | `synapse broadcast "<msg>"` |79| **History** | Audit trail tracks what happened and when | `synapse history list/show/stats` |80| **Plan Approval** | Gated execution ensures quality before action | `synapse approve/reject` |81| **Canvas** | Visual dashboard for sharing rich cards and templates (briefing, comparison, dashboard, steps, slides, plan) | `synapse canvas post/link/briefing/plan/open/list` |82| **Admin Command Center** | Browser-based agent management via Canvas `#/admin` view (select agents, send messages, view responses) | `synapse canvas open` → navigate to `#/admin` |83| **Plan Cards** | Mermaid DAG + step list with accept/sync workflow for task board integration | `synapse canvas plan` / `synapse tasks accept-plan` / `synapse tasks sync-plan` |84| **Smart Suggest** | MCP tool that analyzes prompts and suggests team/task splits for large work | MCP tool: `analyze_task` |85| **Proactive Mode** | Mandatory feature usage checklist for every task (`SYNAPSE_PROACTIVE_MODE_ENABLED=true`) | See `references/features.md` |86| **MCP Bootstrap** | Distribute instructions via MCP resources for compatible clients (opt-in, including Copilot via tools-only). MCP tools: `bootstrap_agent`, `list_agents`, `analyze_task` | `synapse mcp serve` / `python -m synapse.mcp` |8788### Task Board Default Triggers8990Use the Task Board by default when any of these are true:9192- `2+ agents` will work on the task93- The work is likely to run longer than `30 minutes`94- The task spans `3+ files`, multiple phases, or distinct subtasks95- A handoff, manager review, or resume later workflow is likely96- You need the team to see `pending / in_progress / completed / failed` state at a glance9798Minimum pattern:99100```bash101synapse tasks create "<subject>" -d "<shared scope and done criteria>"102synapse tasks assign <id> <agent>103synapse tasks complete <id>104synapse tasks fail <id> --reason "<blocker or failure>"105```106107**Shortcut — task-linked send:** Use `--task` / `-T` to create a board task and link it to the message in one step. The receiver auto-claims the task on receipt, and it auto-completes when the A2A task finalizes. The PTY displays a `[Task: XXXXXXXX]` tag so both agents can see the link.108109```bash110synapse send Impl "Implement auth module" --task --silent111# Equivalent to: tasks create + tasks assign + send with board_task_id112```113114**Cleanup:** Use `synapse tasks purge` to remove stale tasks from the board.115116```bash117synapse tasks purge # Delete all tasks118synapse tasks purge --status completed # Delete only completed tasks119synapse tasks purge --status failed # Delete only failed tasks120synapse tasks purge --older-than 7d # Delete tasks older than 7 days121synapse tasks purge --dry-run # Preview what would be deleted122```123124If none of the triggers apply and the work is a small single-agent change, you can skip the task board.125126### Canvas Template Default Triggers127128Use Canvas templates by default when the output should be read by another129agent or a human later, not just glanced at once in the terminal.130131- `briefing` for structured reports, status updates, and release summaries132- `comparison` for before/after, option trade-offs, and review diffs133- `steps` for plans, migration sequences, and execution checklists134- `slides` for walkthroughs, demos, and page-by-page narratives135- `dashboard` for multi-widget operational snapshots and compact status boards136- `plan` for task DAGs with Mermaid visualization, step tracking, and task board integration (`accept-plan` / `sync-plan`)137138Prefer raw `synapse canvas post <format>` only when a single block is enough.139If the message has multiple sections or needs stronger information hierarchy,140use a template.141142## Spawning Decision Table143144**Default spawn policy:** When using `synapse spawn`, pass the underlying CLI's145tool-specific automation args after `--` so spawned agents can run unattended.146For most CLIs this is an approval-skip / auto-approve flag; for OpenCode use147`--agent build` to select the build agent profile and rely on OpenCode's148permission config for approval behavior.149150Apply the same rule to `synapse team start`: include the appropriate forwarded151CLI args by default, and keep teams homogeneous when those args are152CLI-specific.153154Common defaults:155- Claude Code: `synapse spawn claude --name <n> --role "<r>" -- --dangerously-skip-permissions`156- Gemini CLI: `synapse spawn gemini --name <n> --role "<r>" -- --approval-mode=yolo`157- Codex CLI: `synapse spawn codex --name <n> --role "<r>" -- --full-auto`158- OpenCode: `synapse spawn opencode --name <n> --role "<r>" -- --agent build` (selects the build agent profile; not a skip-approval flag)159- Copilot CLI: `synapse spawn copilot --name <n> --role "<r>" -- --allow-all-tools`160- Claude team: `synapse team start claude claude -- --dangerously-skip-permissions`161- Gemini team: `synapse team start gemini gemini -- --approval-mode=yolo`162- Codex team: `synapse team start codex codex -- --full-auto`163- OpenCode team: `synapse team start opencode opencode -- --agent build` (selects the build agent profile; permission prompts still depend on OpenCode config)164- Copilot team: `synapse team start copilot copilot -- --allow-all-tools`165166| Condition | Action |167|-----------|--------|168| Existing READY agent can handle it | `synapse send` — reuse is faster (avoids startup overhead) |169| Need parallel execution | `synapse spawn` with `--worktree -- <tool-specific-automation-args>` for file isolation |170| Task needs a different model's strengths | Spawn a different type (Claude spawns Gemini, etc.) |171| User specified agent count | Follow exactly |172| Single focused subtask | Spawn 1 agent |173| N independent subtasks | Spawn N agents |174175**Spawn lifecycle**: spawn → confirm in `synapse list` → wait for READY → send task → evaluate result → kill → confirm cleanup in `synapse list`176177Killing spawned agents after completion frees ports, memory, and PTY sessions,178and prevents orphaned agents from accidentally accepting future tasks.179180```bash181# Spawn, delegate, verify, cleanup182synapse spawn gemini --name Tester --role "test writer" -- --approval-mode=yolo183synapse list # Verify agent appears184# Wait for readiness (or rely on server-side Readiness Gate)185synapse send Tester "Write tests for src/auth.py" --wait186# Evaluate result, then cleanup187synapse kill Tester -f188synapse list # Verify cleanup189```190191If `synapse kill` fails or the agent still appears in `synapse list`, retry with `-f`,192check the agent status/logs, and report the cleanup failure instead of leaving an193orphaned agent behind.194195## Response Mode Guide196197Choose based on whether you need the result:198199| Mode | Flag | Use When |200|------|------|----------|201| **Wait** | `--wait` | You need the answer before continuing (questions, reviews) |202| **Notify** | `--notify` (default) | Async — you'll be notified on completion |203| **Silent** | `--silent` | Fire-and-forget delegation (no response needed; sender history still updates best-effort on completion) |204205## Worker Agent Guide206207When you receive a task from a manager or pick one from the task board:208209### On Task Receipt2101. Start work immediately (`[REPLY EXPECTED]` requires a reply; otherwise no reply needed)2112. If the message contains `[Task: XXXXXXXX]`, the board task was auto-claimed for you — no manual `tasks assign` needed2123. Check shared knowledge: `synapse memory search "<task topic>"`2134. Lock files before editing: `synapse file-safety lock <file> $SYNAPSE_AGENT_ID`214215### During Work216- Report progress if task takes >5 minutes: `synapse send <manager> "Progress: <update>" --silent`217- Report blockers immediately: `synapse send <manager> "<question>" --wait`218- Save findings: `synapse memory save <key> "<finding>" --tags <topic>`219- You can delegate subtasks too — spawn helpers (prefer different model types)220- Always clean up agents you spawn: `synapse kill <name> -f`221222### On Completion2231. Update task board: `synapse tasks complete <task_id>`2242. Report to manager: `synapse send <manager> "Done: <summary>" --silent`225226### On Failure2271. Update task board: `synapse tasks fail <task_id> --reason "<reason>"`2282. Report details: `synapse send <manager> "Failed: <error details>" --silent`229230## Related Skills231232| Skill | Purpose |233|-------|---------|234| `synapse-manager` | Multi-agent orchestration workflow (delegation, monitoring, verification) |235| `synapse-reinst` | Re-inject instructions after `/clear` or context reset |236237## References238239For detailed information, consult these reference files:240241| Reference | Contents |242|-----------|----------|243| `references/commands.md` | Full CLI command documentation with all options |244| `references/api.md` | A2A endpoints, readiness gate, error handling |245| `references/examples.md` | Multi-agent workflow examples and patterns |246| `references/file-safety.md` | File locking workflow and commands |247| `references/messaging.md` | Sending, replying, priorities, status states, interactive controls |248| `references/spawning.md` | Spawn lifecycle, patterns, worktree, permissions, API |249| `references/collaboration.md` | Agent naming, external agents, auth, resume, path overrides |250| `references/features.md` | Sessions, workflows, saved agents, tokens, skills, settings, Canvas |
s-hiraoku