Error Report: 2026-03-21 (164 errors in last 24h)

[claude]

Summary

Authentication timeout classification bug persists for 13+ consecutive days requiring immediate fix. The majority of errors are expected user validation errors where the CLI correctly handles invalid states.

Metric	Value
Time range	last 24 hours
Total errors	164
CLI bugs	1
Backend issues	1
User errors (working as designed)	7
Unique users affected	74
Internal user occurrences	8

Errors requiring action

1. Authentication timeout lacks error classification — CLI bug

Error code	None (unclassified)
Occurrences	20 (0 internal)
Users affected	17
Command	whoami
Platforms	Linux, Darwin
PostHog	View in error tracking
Existing issue	Referenced in #430, #426, #423
Recurring	Yes (13+ days)

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

Error: Authentication timed out. Please try again.

Stack trace: (only showing frames from packages/cli/src/)

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:69-74
} 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 (line 60: timeout: expiresIn * 1000). 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:71, replace the generic Error with a proper error class. Import AuthRequiredError or create a new AuthTimeoutError class to properly classify this as a user error with appropriate hints.

---

Backend issues (not CLI fixes)

Error	Occurrences	Users	Command	PostHog
OAuth expired_token	16	10	deploy	View

These are not CLI bugs but may need backend team attention.

User errors (working as designed)

Error	Occurrences	Users	Command	PostHog
No input provided to exec	57	18	exec	View
No Base44 project found	30	12	secrets set	View
App not configured	12	7	functions deploy	View
Invalid function config	11	5	functions deploy	View
Deno not installed	5	4	exec	View
Project already linked	3	1	link	View
--yes required in non-interactive	9	8	deploy	View

The high volume of "No input provided to exec" errors (57 occurrences) suggests users may need clearer guidance on the exec command usage. Consider improving the help text or error message.

Recurring errors

Error	Days recurring	Existing issue	Tracked?
Authentication timeout	13+ days	#430, #426, #423	yes
OAuth expired_token	Multiple days	none	no

The untracked recurring OAuth error should be investigated for backend solution.

Action items

1. [high] packages/cli/src/cli/commands/auth/login-flow.ts:71 — Replace generic Error with proper error classification (AuthRequiredError or new AuthTimeoutError) to fix telemetry tracking