Error Report: 2026-04-23 (223 errors in last 24h)

[claude]

Summary

User validation errors continue at expected levels with appropriate CLI messaging. Backend API restrictions and environment issues affect some users. All CLI error handling working correctly with clear user guidance. No CLI bugs requiring action.

Metric	Value
Time range	last 24 hours
Total errors	223
CLI bugs	0
Backend issues	1
User errors (working as designed)	8
Unique users affected	101+
Internal user occurrences	8

Errors requiring action

No CLI bugs requiring immediate action. All errors show appropriate validation and error handling.

Backend issues (not CLI fixes)

Error	Occurrences	Users	Command	PostHog
Backend Platform app restrictions (428)	15	10+	deploy, functions deploy, entities push	View

Backend Platform restriction analysis: The CLI correctly makes API requests to the backend, which returns 428 Precondition Required with messages like "This endpoint is only available for Backend Platform apps" when users try to access features unavailable for their app type. The CLI properly reports these via ApiError.fromHttpError() in packages/cli/src/core/errors.ts:335-384. This is working backend business logic, not a CLI issue.

User errors (working as designed)

Error	Occurrences	Users	Command	PostHog
Project not found validation	62	22	dev, link	View
Various input validation	57	21	eject, link, deploy, exec	View
Schema validation errors	37	13	exec, entities push, eject	Multiple PostHog links
Deno dependency missing	14	10	exec, dev	View
Project already linked	10	5	link	View
App configuration missing	10	9	exec	View
Authentication timeout	5	5	whoami	View

CONFIG_NOT_FOUND analysis: From packages/cli/src/core/project/config.ts:75-77, when findProjectRoot() returns null (no config.jsonc/config.json found), the CLI throws clear guidance: "Project root not found. Please ensure config.jsonc or config.json exists in the project directory or base44/ subdirectory." This is working as designed.

INVALID_INPUT analysis: Multiple validation patterns including non-interactive mode requirements ("--project-id is required in non-interactive mode", "--yes is required in non-interactive mode"), missing stdin input ("No input provided. Pipe a script to stdin"), and duplicate resource names ("Duplicate function name") all provide appropriate error messaging.

SCHEMA_INVALID analysis: Entity, agent, and configuration validation from Zod provides specific field-level guidance like "Invalid input: expected string, received undefined → at id" and "Entity name must be alphanumeric only → at name" which helps users fix their configuration files.

DEPENDENCY_NOT_FOUND analysis: From packages/cli/src/core/errors.ts:268-279, the CLI properly validates Deno installation and provides clear guidance: "Deno is required to run scripts with exec" when the dependency is missing.

AUTH_EXPIRED analysis: Authentication timeout handling from packages/cli/src/core/errors.ts:147-163 provides clear guidance: "Authentication timed out. Please try again." directing users to re-authenticate.

Environment issues (not CLI fixes)

Error	Occurrences	Users	Command	PostHog
Disk space errors during npm install	7	3	eject	View

Disk space analysis: Error shows "ENOSPC: no space left on device" during npm install operations when users run eject command. This is a user environment issue where the machine has insufficient disk space, not a CLI bug. The CLI correctly propagates the Node.js filesystem error.

Recurring errors

Based on previous daily reports (issues #492, #490, #489, #488, #486), these errors continue from multiple days:

Error	Days recurring	Existing issue	Tracked?
CONFIG_NOT_FOUND validation	10+ days	Referenced in #492, #490, #489, #488, #486	Yes (expected user error)
INVALID_INPUT validation	10+ days	Referenced in #492, #490, #489, #488, #486	Yes (expected user error)
Backend Platform restrictions (428)	3+ days	Referenced in #492, #490	Yes (backend business rules)
Schema validation errors	10+ days	Referenced in #492, #490, #489, #488, #486	Yes (expected user error)
Authentication timeout	10+ days	Referenced in #492, #490, #489, #488, #486	Yes (expected timeout)
Dependency validation	10+ days	Referenced in #492, #490, #489, #488, #486	Yes (expected user error)

All recurring errors are expected user validation patterns or documented backend business rules. No new error categories requiring investigation.

Action items

No CLI code changes required. Backend business rule for Backend Platform app restrictions is working as designed:

1. [low] Backend Platform app restrictions (428 errors) represent backend access control - users attempting to use features unavailable for their app type receive appropriate error messages via the CLI's standard API error handling