[feat] Add triggers catalog browse and connections UI

[jp-agenta]

Context

The triggers backend (catalog plus connections) had no UI. This lane adds the browse half of the frontend: a Triggers surface where you pick a connected integration, browse its events, and see each event's config schema, plus the connection list. It is the visual dual of the existing Tools settings surface.

Changes

Adds a Triggers settings surface mirroring the Tools UI:

• On a connected integration you browse its events (from the catalog API) and view each event's trigger_config schema read-only, reusing the existing SchemaForm.
• Connections are read via /triggers/connections. The same shared gateway_connections row appears under both Tools and Triggers with no second connect. The two lists use distinct React Query keys so the shared rows never collide in cache, and the connection type is aliased to the tools type so the lists stay byte-compatible.
• New gatewayTrigger modules in @agenta/entities (API client, hooks, state) and @agenta/entity-ui (the events drawer), plus the OSS settings page and sidebar entry.

The API client is built on the shared axios instance with zod validation at the boundary, because the catalog API is not yet in the generated Fern client and regenerating it needs the backend OpenAPI (out of scope for a web-only lane). The local zod schemas mirror the backend DTOs and collapse onto the generated client once it is regenerated.

The Triggers tab is gated by the same Composio gate as Tools (isToolsEnabled()); no separate frontend flag.

Tests / notes

• @agenta/entities unit suite passes, including a new gatewayTriggerApi test covering catalog browse, the shared-row reads, and boundary-validation fallbacks.
• Type-check and lint pass on @agenta/entities and @agenta/entity-ui.

What to QA

• Open Settings on a project with a connected Composio integration. A Triggers tab should appear next to Tools.
• In Triggers, pick the connected integration and browse its events. Each event should show its trigger_config schema. Confirm the connection that appears under Tools also appears under Triggers without prompting a second connect.
• Regression to watch: the Tools connection list must still render and behave exactly as before.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
agenta-documentation	Ready	Preview, Comment	Jun 18, 2026 5:29pm

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 61dfad93-4dfc-4e2a-8bf8-ff251de8da73

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch wp5-web-catalog

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[jp-agenta]

Superseded by #4749, which consolidates the entire gateway-triggers work (api + web + hosting + docs) into a single PR.