Improve CLI stage telemetry and error reporting#807
Draft
zahlekhan wants to merge 2 commits into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
cli_create_stagelifecycle event with stage rank, status, duration, and per-run/per-attempt IDs--no-install, and unrequested skill installation do not reduce completion ratesWhy
The current CLI reports that dependency installation or creation failed, but discards the process error and the existing
CreateError.stage. Stage instrumentation is also manually duplicated, so fields and semantics drift between steps. This makes pnpm failures difficult to diagnose and blends intentional skips or retries into apparent drop-off.This combines the canonical stage runner with hardened subprocess and error handling. Raw stdout/stderr, local paths, response bodies, project names, and user-entered values are never sent to PostHog. A bounded diagnostic window remains local, while only code-defined failure fingerprints are retained for classification.
Impact
PostHog can benchmark conversion and p50/p95 duration by stage and CLI version, and failures can be broken down by normalized category, package manager, package-manager version, Node version, auth method, and AI setup. Prompt cancellation, auth skip,
--no-install, recoverable auth failure, and an unrequested skill install are reported separately.Package-manager selection and install flags are unchanged: pnpm still runs
pnpm install; this change does not add--strict-peer-dependencies.Validation
pnpm --filter @openuidev/cli testpnpm exec tsc -p packages/openui-cli/tsconfig.test.json --noEmitpnpm --filter @openuidev/cli run buildpnpm --filter @openuidev/cli run lint:checkpnpm --filter @openuidev/cli run format:check--auth skip --no-install --no-skill --no-interactive