Skip to content

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

Kshitij Jhunjhunwalacbc6cfc64bda
diff --git a/install.sh b/install.sh
index fbd6233ab..4370c0de3 100755
--- a/install.sh
+++ b/install.sh
@@ -415,7 +415,7 @@ fi
if [[ $install_agent = true ]]; then
echo
info "Setting up Composio agent login..."
- if ! "$exe" login --agent --no-skill-install; then
+ if ! COMPOSIO_CLI_INVOCATION_ORIGIN=installer "$exe" login --agent --no-skill-install; then
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>`.'
fi
fi
diff --git a/ts/packages/cli/CHANGELOG.md b/ts/packages/cli/CHANGELOG.md
index 06da0dc36..90dd9e143 100644
--- a/ts/packages/cli/CHANGELOG.md
+++ b/ts/packages/cli/CHANGELOG.md
@@ -11,7 +11,7 @@
### Minor Changes
- Telemetry now delivers directly to PostHog, so pre-login `install`/`setup` events are captured. Opt-outs are unchanged.
-- 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.
+- 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.
- a0bef5d: Bump `@composio/client` to `0.1.0-alpha.74`.
- 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.
diff --git a/ts/packages/cli/src/analytics/events.ts b/ts/packages/cli/src/analytics/events.ts
index df0807270..36f240499 100644
--- a/ts/packages/cli/src/analytics/events.ts
+++ b/ts/packages/cli/src/analytics/events.ts
@@ -103,6 +103,8 @@ export const CLI_EVENT_JOURNEY_STAGES = {
CLI_TOOL_INVOCATION_FAILED: 'execute',
} as const satisfies Record<CliAnalyticsEventName, CliJourneyStage>;
+const CLI_CHANNEL = inferSkillReleaseChannel(APP_VERSION);
+
const buildEvent = (
name: CliAnalyticsEventName,
properties: Record<string, unknown>
@@ -111,7 +113,7 @@ const buildEvent = (
properties: {
...properties,
journey_stage: CLI_EVENT_JOURNEY_STAGES[name],
- cli_channel: inferSkillReleaseChannel(APP_VERSION),
+ cli_channel: CLI_CHANNEL,
},
});