Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
fix(cli): match `--toolkits` for toolkit slugs with underscores (#5124)
This PR: - Refs #4947 (CLI side); the SDK halves are #4948 (TypeScript core) and #4954 (Python), which use the same rule - makes `composio dev triggers listen --toolkits one_drive` (and `launch_darkly`, `agent_mail`) match events instead of dropping all of them - matches a `--toolkits` entry when it equals the event's derived toolkit, or when the trigger slug starts with `<toolkit>_`, ignoring case - adds a patch entry to `ts/packages/cli/CHANGELOG.md` (the CLI is excluded from Changesets) ## Context Trigger payloads carry no toolkit slug, so `parseTriggerListenEvent` derives it from the trigger slug's first `_` segment: `ONE_DRIVE_FILE_CREATED_TRIGGER` becomes `ONE`, and `--toolkits one_drive` never matched. The prefix rule would let `--toolkits google` match a `GOOGLE_CALENDAR_*` trigger if both `google` and `google_calendar` were toolkits with triggers. No such pair exists: in `docs/public/data/toolkits.json` every trigger slug starts with its own toolkit's slug, and none starts with another toolkit's slug plus `_`. An earlier revision resolved the toolkit exactly through `ToolkitSlugCatalog`; it was reverted to keep the CLI on the same rule as the SDKs for a case that does not occur. `composio listen` and `composio dev listen` filter by trigger id only, so they never hit the bug. ## How Has This Been Tested? - `filter.test.ts`: `gmail` in either case, `one_drive` / `ONE_DRIVE`, `launch_darkly`, `agent_mail`, and `one_drive` not matching `ONE_DRIVEX_*`; the underscore cases fail on `next` - after merging `next`: CLI suite (223 files, 2900 passed, 1 skipped), root `pnpm typecheck`, `lint:effect` and oxlint on `ts/packages/cli`: clean