Summary

Two related pieces of work:

1. Agent config knowledge (cedar-configuration skill). Extends the "how each integration connects and syncs" section with LinkedIn and WhatsApp , plain-English, no vendor/infra terms , plus the WhatsApp reply-window notification mechanic and a LinkedIn-attach capability-gap note. Full research/design writeup: docs/design/mcp-connection-settings-checklist.md.

2. MCP connection-settings surface. Closes the gap between Settings → Connections and what's configurable over MCP:

• update_slack_sync_config gains scope: 'user' | 'org' , the org default is wired into both real runtime sync-decision call sites (link-matching-channels.ts, slack-events-webhook.ts), not a write-only toggle.
• disconnect_linkedin_seat / disconnect_whatsapp_account (by unipileAccountId).
• update_whatsapp_sync_config , syncAllChats override + per-chat trackChat consent grant/revoke.
• resolve_channel_link_proposal , resolve/dismiss one ambiguous Slack/LinkedIn/WhatsApp channel, or sweep the org's pending links.
• update_webhook_export_config , the custom CRM webhook-export endpoint is now agent-writable.
• read-connection-settings gains connectLinks.{linkedin,whatsapp} (the real in-app settings deep link) and slackSyncConfig.usingOrgDefault.

Every new action inherits targetUserId/authorize() from the tool's existing gate , none needed a bespoke check, verified against the two safety-net tests built for exactly this (mutating-actions-are-administrable, target-user-id-reaches-the-authority). Connecting LinkedIn/WhatsApp itself stays correctly human-only (an OAuth-style hosted-auth flow); the agent now hands back the exact settings link instead of refusing outright.

Review passes applied, not just run:

• /code-review thermo-review: found the change growing an already-oversized file instead of following its own established extraction precedent (apply-systems-change.ts) , fixed by extracting into apply-connection-extras-change.ts. Also found a claimed-but-missing test proving the Slack org-default reaches the real runtime path , added slack-events-webhook.parseSlackConfig.test.ts to close it.
• /refresh-agent-knowledge: confirmed authorize()'s DEFAULT_POLICY already grants connection_config:org to ORG_ADMIN (so the new org-scope write is genuinely enforced, not just written), and added org-wide defaults to the skill's "ask before writing" scope list.

Test plan

• pnpm --filter @zero/server run types , clean
• pnpm deps:check , 0 violations
• Scoped vitest: 75/75 across the 7 touched/related test files (new connection-write actions, Slack config-resolution, schema-size budget, both authorization safety nets)
• pnpm --filter @zero/server exec vitest run src/mastra/skills/account-config , 158/158 (knowledge-claims-resolve, allowlist/trigger-type splices, description-length caps)

Not implemented, correctly deferred (see docs/design/mcp-connection-settings-checklist.md §6): org-default policy for LinkedIn/WhatsApp specifically, since a personal account isn't a shared workspace resource the way Slack's bot is , needs a product decision on what "org scope" even means there before building it.

🤖 Generated with Claude Code

https://claude.ai/code/session_01RY8attAx6MwUcZfnFB8ao2

Greptile Summary

Adds agent-facing connection controls for LinkedIn, WhatsApp, Slack channel linking, and custom webhook exports, alongside integration guidance and human-only connection deep links.

• Introduces organization-level Slack defaults and applies them to channel linking and message admission.
• Three functional issues need correction: Slack readback omits effective defaults, an existing organization-settings update can erase the new policy, and webhook configuration accepts destinations the sender cannot use.
• Also identifies an unsupported Slack option that sile