Error Report: 2026-03-26 (194 errors in last 24h)

[claude]

Summary

Authentication timeout classification bug persists for 17+ consecutive days requiring immediate fix. User validation errors remain the majority of error volume with appropriate CLI behavior.

Metric	Value
Time range	last 24 hours
Total errors	194
CLI bugs	1
Backend issues	1
User errors (working as designed)	6
Unique users affected	82
Internal user occurrences	41

Errors requiring action

1. Authentication timeout lacks error classification — CLI bug

Error code	None (unclassified)
Occurrences	13 (1 internal)
Users affected	12
Command	whoami
Platforms	Various
PostHog	View in error tracking
Existing issue	Referenced in #442, #440, #438, #436, #434
Recurring	Yes (17+ days)

Error: (from PostHog — the actual error message users see)

Error: Authentication timed out. Please try again.

Stack trace: (only show frames from packages/cli/src/ — skip generic entry points)

at waitForAuthentication (packages/cli/src/cli/commands/auth/login-flow.ts:71)
at login (packages/cli/src/cli/commands/auth/login-flow.ts:105)

Root cause: The authentication timeout throws a generic Error without proper classification:

// packages/cli/src/cli/commands/auth/login-flow.ts:71-76
} catch (error) {
  if (error instanceof Error && error.message.includes("timed out")) {
    throw new Error("Authentication timed out. Please try again.");
  }
  throw error;
}

This timeout occurs when the OAuth2 device code expires. The generic Error lacks proper classification for telemetry tracking, causing error_code: null and is_user_error: null in PostHog.

Suggested fix: In packages/cli/src/cli/commands/auth/login-flow.ts:73, replace throw new Error("Authentication timed out. Please try again.") with throw new AuthExpiredError("Authentication timed out. Please try again.") using the existing error class from packages/cli/src/core/errors.ts:147.

---

Backend issues (not CLI fixes)

Error	Occurrences	Users	Command	PostHog
OAuth expired_token	11	10	site deploy	link
Invalid agent model validation	3	3	agents push	link

Backend OAuth token expiration and API validation errors are server-side issues, not CLI bugs.

User errors (working as designed)

Error	Occurrences	Users	Command	PostHog
Project not found or not ejectable	75	20	eject	link
No Base44 project found	53	15	link	link
Invalid app configuration schema	16	8	site deploy	link
Deno dependency missing	13	7	exec	link
App not configured	7	7	site deploy	link
Project already linked	6	6	link	link

All user errors provide appropriate validation messages. The high volume of "Project not found or not ejectable" errors (75 occurrences) suggests users commonly attempt to eject projects that don't exist in their account or are not in an ejectable state.

Recurring errors

Error	Days recurring	Existing issue	Tracked?
Authentication timeout (unclassified)	17+ days	Referenced in #442, #440, #438, #436, #434	No dedicated issue

This is now the longest-running unresolved CLI bug, affecting telemetry accuracy and user experience classification for over two weeks.

Action items

1. [critical] packages/cli/src/cli/commands/auth/login-flow.ts:73 — Replace throw new Error("Authentication timed out. Please try again.") with throw new AuthExpiredError("Authentication timed out. Please try again.") to enable proper telemetry classification. The AuthExpiredError class is already defined in packages/cli/src/core/errors.ts:147 and extends UserError with error code "AUTH_EXPIRED".