CedarCopilot wants to merge 1 commit into main from staging
Not deployed
Libra has no production signal for this change yet because it has not deployed. Libra checks hourly for 3 days after each deploy.
This change expands agent history, integration configuration, organization-wide Slack defaults, and meeting/event behavior. It also introduces blocking defects: members can disconnect integrations owned by teammates, resolving a channel proposal can relink containers from multiple provider accounts, and concurrent organization-settings writes can erase each other. Two non-blocking presentation defects can misrepresent failed history requests and partial Slack-policy inheritance.
Not safe to merge until integration ownership, channel-container targeting, and concurrent organization-settings writes are corrected. The history and Slack provenance issues are non-blocking but should also be addressed.
Focused checks reproduced three independent failures with concrete unauthorized mutation, incorrect multi-container relinking, and persisted lost-update outcomes. A security-impacting failure is also confirmed.
Files Needing Attention: apps/server/src/mastra/skills/account-config/tools/apply-connection-extras-change.ts, apps/server/src/services/channels/containers.ts, apps/server/src/services/integrations/connection-config.ts, apps/server/src/trpc/routes/org-admin.ts, apps/mail/modules/agents/components/AgentView.tsx, and apps/server/src/services/integrations/slack/slack-config-resolution.ts
An organization member can disconnect another member’s LinkedIn or WhatsApp integration by using an organization-visible provider account ID. The new disconnect actions verify only that the account belongs to the same organization, not that it belongs to the authorized member; WhatsApp disconnection also removes the affected line’s tracked contacts and chats.
What T-Rex did
apps/mail/modules/agents/components/AgentView.tsx, line 322-332 (link)
Libra has not measured any production surfaces for this change yet.