Agent Team Inbox

Open the bell and choose Open Agent Team Inbox, or go directly to /inbox. Filter Needs action, Active, Completed, or Failed, then select one run to inspect its private receipt without leaving the queue.

• Needs action combines authenticated approval requests and quiet-hour recovery.
• Active shows queued and running work.
• Completed keeps durable step, cost, and evidence receipts even after a notification is cleared.
• Failed shows stopped runs, rejected source requests, and reply deliveries that can be retried safely.

In Trigger Hub choose App event, select the connected account and exact channel or mailbox query, and keep Reply in the source conversation enabled. If a Slack or Teams text filter is blank, the message must begin with /codelit, @codelit, or codelit so ordinary conversation cannot start work.

1. 1Reconnect Slack once if the connection predates sender-email verification.
2. 2For Microsoft Teams, reconnect Microsoft 365 with Use Agent Team channel, then choose the Team and channel from the picker.
3. 3For an existing Gmail or Outlook account, choose Enable Agent Team inbox access in Trigger Hub so the same connection adds bounded read and reply permission.
4. 4Choose one bounded mailbox query, publish the automation, send one request as a current workspace member, and follow the private receipt link in the provider-native thread reply.

A source reply names the exact gated step, risk, and editable-field count, then links to Codelit. Workspace reviewers use the same bounded approval editor as the global bell. Personal owners can approve or hold from their authenticated private receipt. The source message itself never grants decision authority.

If Slack, Teams, or email cannot receive the status reply, the run remains complete and the Inbox records a recoverable delivery failure. Choose Retry on that delivery after reconnecting the app. Retrying sends the existing receipt link; it does not rerun the Agent Team or repeat external actions.

Connected conversations receive status, step count, approximate cost, and a private receipt URL. Model output, source content, credentials, sender email, binding digest, logs, and unrestricted evidence remain out of the conversation and out of the Inbox list. Full output appears only after deployment access is checked for the signed-in account.

• Sender email is used transiently for member matching and is not retained in the conversation binding.
• Quiet-hour source payloads are encrypted until the run resumes.
• Conversation delivery records are bounded inside the run and follow the existing account, workspace, run, and trigger-delivery deletion paths.
• Reply preferences can be disabled per automation without disabling terminal email or signed result webhooks.