@devries-cameron20 / composio-1 / commits / cbc6cfc64
Fork 0

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): tag installer-driven agent login; hoist channel; correct changelog

Review follow-ups. - install.sh ran `login --agent` without an origin marker while its `install` and `setup` invocations both set one, so installer-driven agent logins were indistinguishable from manual ones — the exact ambiguity this PR removes for the other two. - Hoist the release channel to a module constant; both inputs are constants, so recomputing it per event was pointless. - The changelog overstated the gap: a Homebrew user running `composio install` by hand still emits install events, they just carry no installer origin. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Kshitij Jhunjhunwala committed Jul 23, 2026 at 16:48 UTC cbc6cfc64bda709590bc7c199690a8333839efd4
3 files changed +5 -3
install.sh
+1 -1
@@ -415,7 +415,7 @@ fi
415 if [[ $install_agent = true ]]; then
416 echo
417 info "Setting up Composio agent login..."
418 - if ! "$exe" login --agent --no-skill-install; then
418 + if ! COMPOSIO_CLI_INVOCATION_ORIGIN=installer "$exe" login --agent --no-skill-install; then
419 error 'Failed to sign up/log in as a Composio agent. If this CLI is already signed in as a regular user, run `composio logout` and then `composio signup` or `composio agent login <composio_agent_key>`.'
420 fi
421 fi
ts/packages/cli/CHANGELOG.md
+1 -1
@@ -11,7 +11,7 @@
11 ### Minor Changes
12
13 - Telemetry now delivers directly to PostHog, so pre-login `install`/`setup` events are captured. Opt-outs are unchanged.
14 -- Telemetry events now carry `journey_stage` (install/setup/login/connect/execute/other) and `cli_channel` (stable/beta) properties, and `install.sh` marks its `composio install` run with `invocation_origin: installer` so script installs are distinguishable from manual ones. npm and Homebrew installs do not run `install.sh`, so they emit no install-stage events.
14 +- Telemetry events now carry `journey_stage` (install/setup/login/connect/execute/other) and `cli_channel` (stable/beta) properties, and `install.sh` marks its `composio install` run with `invocation_origin: installer` so script installs are distinguishable from manual ones. npm and Homebrew installs do not run `install.sh`, so their installs carry no installer origin.
15 - a0bef5d: Bump `@composio/client` to `0.1.0-alpha.74`.
16 - 025a657: Drop CommonJS entrypoints and publish the TypeScript SDK packages as ESM-only packages. This is a breaking change within the existing 0.x release line: consumers must use Node.js 22.22.3 or newer. CommonJS callers can only rely on Node's native `require(esm)` interop, and the SDK no longer ships custom CommonJS compatibility machinery or `.cjs` artifacts.
17
ts/packages/cli/src/analytics/events.ts
+3 -1
@@ -103,6 +103,8 @@ export const CLI_EVENT_JOURNEY_STAGES = {
103 CLI_TOOL_INVOCATION_FAILED: 'execute',
104 } as const satisfies Record<CliAnalyticsEventName, CliJourneyStage>;
105
106 +const CLI_CHANNEL = inferSkillReleaseChannel(APP_VERSION);
107 +
108 const buildEvent = (
109 name: CliAnalyticsEventName,
110 properties: Record<string, unknown>
@@ -111,7 +113,7 @@ const buildEvent = (
113 properties: {
114 ...properties,
115 journey_stage: CLI_EVENT_JOURNEY_STAGES[name],
114 - cli_channel: inferSkillReleaseChannel(APP_VERSION),
116 + cli_channel: CLI_CHANNEL,
117 },
118 });
119