what

The connections settings page grouped tools by the backend's two coarse buckets (Notification / Productivity), with a small frontend override map on top. The result was bad:

• Most integrations piled into one giant "Productivity" group (Stripe, Salesforce, GitHub, Sentry, Vercel, Brex, Glean, Bee, Readwise, n8n, and ~20 more).
• A handful were plain wrong. Hermes, an autonomous agent, sat under Communication.
• The title-caser mangled acronyms, so the "AI" header rendered as "Ai".

fix

• Expanded CONNECTION_CATEGORY_BY_ID to cover every tile id: all 65 backend integrations plus the frontend-only tiles (88 total), grouped into 17 intuitive categories.
• Moved Hermes / OpenClaw / Skills to Agent, and split the Productivity dump into CRM, Finance, Developer, Support, Automation, Notes, Wearables, and more.
• Updated CATEGORY_ORDER to match.
• Taught normalizeConnectionCategory to preserve all-caps acronyms, so "AI" and "CRM" stop rendering as "Ai" / "Crm".

Keys match each connection's real id (e.g. the backend IntegrationDef.id is github, not github_issues), so the override actually lands instead of falling through to the coarse bucket.

categories

Desktop, AI, Agent, Automation, Meetings, Calendar, Communication, Notes, Documents, Project Management, CRM, Support, Finance, Developer, Wearables, Notifications, System.

verification

• bun run typecheck (tsc, clean)
• bun run build (next build, all routes compiled including /settings and /home)
• Simulated the normalizer + grouping over the full map: all 88 ids resolve into the 17 ordered groups, nothing falls through to "Other".

Two files touched: lib/constants/connections.ts and components/settings/connections-section.tsx.