You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- For OpenCode teammates: `OPENCODE_SERVER_URL` must be set (for example, `http://localhost:4096`)
59
+
- For OpenCode teammates:
60
+
-`OPENCODE_SERVER_URL` must be set (for example, `http://localhost:4096`)
61
+
- the `claude-teams` MCP server must be connected in that OpenCode instance
60
62
61
63
## Tools
62
64
@@ -65,7 +67,7 @@ Or add to `~/.config/opencode/opencode.json` (OpenCode):
65
67
|`team_create`| Create a new agent team. One team per server session. |
66
68
|`team_delete`| Delete a team and all its data. Fails if teammates are still active. |
67
69
|`spawn_teammate`| Spawn a teammate in tmux (pane by default, window when `USE_TMUX_WINDOWS` is set). |
68
-
|`send_message`| Send direct messages, broadcasts, shutdown/plan approval responses. |
70
+
|`send_message`| Send direct messages (teammates to team-lead), broadcasts (team-lead only), and shutdown/plan responses. |
69
71
|`read_inbox`| Read messages from an agent's inbox. |
70
72
|`poll_inbox`| Long-poll an inbox for new messages (up to 30s). |
71
73
|`read_config`| Read team configuration and member list. |
@@ -79,9 +81,9 @@ Or add to `~/.config/opencode/opencode.json` (OpenCode):
79
81
## How it works
80
82
81
83
-**Spawning**: Teammates launch in tmux via `tmux split-window` (default) or `tmux new-window` when `USE_TMUX_WINDOWS` is set. Backend can be Claude (`claude`) or OpenCode (`opencode`). Each gets a unique agent ID (`name@team`) and color.
82
-
-**Messaging**: JSON-based inboxes under `~/.claude/teams/<team>/inboxes/`. File locking (`fcntl`) prevents corruption from concurrent reads/writes.
84
+
-**Messaging**: JSON inboxes live under `~/.claude/teams/<team>/inboxes/`. Team lead can message anyone; teammates can message only team lead.
83
85
-**Tasks**: JSON task files under `~/.claude/tasks/<team>/`. Tasks have status tracking, ownership, and dependency management (`blocks`/`blockedBy`).
84
-
-**Concurrency safety**: Atomic writes via `tempfile` + `os.replace`for config. `fcntl` file locks for inbox operations.
86
+
-**Concurrency safety**: Atomic config writes via `tempfile` + `os.replace`(with Windows retry). Cross-platform file locks via `filelock`.
0 commit comments