Slack
The Slack mirror shows your project's agents, conflicts and messages in one Slack channel, and carries your replies back into the agents. It is a window with a mail slot: you can read, reply and resolve a conflict from Slack, but you cannot start, stop or steer an agent from there.
What appears in the channel
- A daily status post. One root post per project per day (UTC), with the project's status line, up to 15 agents, up to 8 open conflicts and links to their posts. It is edited as things change, never reposted. It is created by the first activity of the day, so a quiet day has no post.
- Agent updates, threaded under the daily post: an agent connected, went idle, ended, or its files in use changed. A burst of edits from one agent is grouped into one line.
- Messages between agents, threaded under the daily post.
- Conflicts, each as its own top-level post, edited in place as the conflict changes. Each has the buttons Open dashboard, Message agent and, while open, Resolve.
Choosing what to show
In Settings, Show in Slack sets how much reaches the channel:
| Setting | Shows |
|---|---|
| Agents, files in use, conflicts and messages | Everything above |
| Conflicts and messages | Conflicts, and messages between agents |
| Conflicts only | Conflict posts |
You can also set quiet hours, in UTC: updates are held during them and posted after. Replies from Slack are never held. A project gets at most 200 new posts a day; after that, existing posts are still edited and the daily post says the mirror is muted.
Replying from Slack
- Reply in a conflict's thread to message both agents in that conflict. Message agent points you there.
- Reply in the daily post's thread to message every agent in the project that has not ended.
- Resolve a conflict with the Resolve button or a ✅ reaction on its post. Both agents are told:
Conflict resolved in Slack. Coordinate before resuming edits.
Your reply reaches each agent as a message from you, by your Slack display name, up to 4000 characters. Replies from other channels, shared channels, bots, edits and deletions are ignored.
Slash commands
/coordigent works only in the connected channel, and only you see its answers.
| Command | Does |
|---|---|
/coordigent status | Shows the same status block as coord status, with each agent's short id and state |
/coordigent claim [agent] | Lists files edited by one agent, or by every agent that has not ended |
/coordigent msg <agent> <text> | Messages one agent that has not ended |
Every answer starts with that status block. <agent> is the short id /coordigent status shows, or any longer start of the agent's id, at least four characters, and must match exactly one agent that has not ended. An id that matches none, such as an old last-four id, gets No agent starts with …, which points you back to /coordigent status; one that matches several asks for more characters.
Setting it up
Any member of the project can connect Slack.
- Open your project's Settings page on the website and choose Connect Slack. From a terminal,
coord chat connect slackprints the link. - Approve the Coordigent app in Slack.
- Back in Settings, pick a channel, choose what to show, set quiet hours if you want them, and choose Save settings. The daily post appears shortly.
coord chat connect slackTo use a private channel, invite the Coordigent app to it first. Shared channels are not supported. One Slack can mirror only one project: connecting a second project from the same Slack fails.
Disconnecting
Choose Disconnect mirror in Settings. Coordigent stops posting and drops anything still waiting to be sent. This does not remove the app from Slack; do that in Slack itself. Removing the app in Slack disconnects the mirror too.