feat: surface Tavily in onboarding integrations step
@opencolinchecks…feat/onboard-tavily → main2 files · +6 −0updated 1mo agoloading diff…
@opencolinchecks…feat/onboard-tavily → main2 files · +6 −0updated 1mo ago@opencolinchecks…feat/onboard-tavily → main2 files · +6 −0updated 1mo agoAdd Tavily to the curated onboarding toolkits so new users connect web search alongside Gmail/GitHub/Slack during signup instead of leaving the agent search-less until they hunt through Composio's full catalog.
src/server/api/routers/trustclaw/getIntegrationAuthLinks.ts — add a Tavily entry to ONBOARDING_TOOLKITS. The slug + logo match the existing convention (slug: "tavily", logo from Composio's logo CDN at https://logos.composio.dev/api/tavily).src/app/(authenticated)/dashboard/_components/onboarding/onboarding.consts.ts — add a one-line description ("Search the web for up-to-date information") to INTEGRATION_DESCRIPTIONS.That's it — 6 lines across 2 files.
Tavily already works through Composio's tool ecosystem; the agent picks it up automatically once a user has a Tavily connection on their account. The only thing missing was discoverability during onboarding. Putting it in the same four-tile grid as Gmail/GitHub/Slack means new users actually see the option.
No new env vars, no new dependencies, no new tool code, no changes to the agent runtime. The integrations step already renders its tiles dynamically from the tRPC query — adding a fourth entry just shows up.
pnpm tsc --noEmit — cleanagent.tools() after connectionVisual + flow tests aren't possible from this checkout without a real Composio account + Tavily connection, so they're listed as TODO for review.
🤖 Generated with Claude Code