Skip to main content

Communications

Every other pillar produces something that needs to reach a person: a plan that needs approval, an incident that needs eyes, a cost or security report, a question the AI got stuck on. Communications is the layer that carries those things to you and carries your replies back. It has no screen of its own. It is the delivery system behind the other pillars.

The three surfaces​

ACE delivers to whichever of these are connected. The in-app inbox is always on; Slack and Teams are optional.

Connect none of the chat surfaces, and everything still works through the inbox and the web app. Connect Slack or Teams, and the same updates also go to where your team already talks.

What flows through it​

  • Chat. Every conversation with ACE is the same underlying session, whether it is a project chat or "Discuss in chat" on an incident or report, and whether you are typing in the web app or replying in Slack or Teams.
  • Human-in-the-loop asks. When an agent hits a checkpoint (an approval, a question), it goes to whichever surface you last talked to ACE from. Reply there, and ACE picks it back up.
  • Reports and events. Incident detection, cost reports, security reports, and pull request or deployment updates are written into a conversation thread and, if a channel is connected, posted there too.

The rule that matters: last-spoken channel​

ACE doesn't guess where to send a follow-up. It remembers the surface you last used with a project (web, Slack, or Teams) and routes the next question or approval request back to that same place. Reply from Slack and the thread continues in Slack. Switch to the web app and it follows you there.

Mandatory vs. optional​

  • The in-app inbox always receives everything. It is not a fallback you configure, it is the floor.
  • Slack and Teams are optional, but connecting one changes delivery for the two things easiest to miss: Operations cost and security reports, and any human-in-the-loop approval, since those hurt most when they land only in a tab you don't have open.
Some notifications cannot be muted

A few notification kinds, a blocking approval or a blocking pull request review issue, are mandatory. You cannot mute them on any surface.

Where to go next​

OperationsCost and security reports that need a channel to reach chat.Pull RequestsThe PR and deployment updates that flow through this layer.Connect a repositorySet up the connections, including a Slack or Teams channel.
On this page