Error Report: 2026-03-31 (189 errors in last 24h)

[claude]

Summary

User validation errors continue to dominate with 155 occurrences across config and input validation issues. Agent API validation errors suggest backend schema enforcement changes. Windows path corruption in eject command persists as an unresolved CLI bug affecting 5 users.

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

Errors requiring action

1. Path corruption during eject causes mkdir failures — CLI bug

Error code	None (unclassified)
Occurrences	5 (0 internal)
Users affected	5
Command	eject
Platforms	Windows
PostHog	None (issue_id is null)
Existing issue	Referenced in #448
Recurring	Yes (5+ days)

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

ENOENT: no such file or directory, mkdir 'C:\\Users\\<redacted>\\OneDrive\\Desktop\\160Glow_Operations\\RANDY CLAW\\Randy x Base44\\Users\\<redacted>\\OneDrive\\Desktop\\160Glow_Operations\\RANDY CLAW\\Randy x Base44\\'

Stack trace: (Windows path corruption prevents stack trace from being captured properly)

(not available due to path corruption)

Root cause: Path resolution corruption in eject command input handling:

// packages/cli/src/cli/commands/project/eject.ts:97-114
const suggestedPath = (await isDirEmpty())
  ? `./`
  : `./${kebabCase(selectedProject.name)}`;

const selectedPath =
  options.path ??
  (await text({
    message: "Where should we create your project?",
    placeholder: suggestedPath,
    initialValue: suggestedPath,
  }));

const resolvedPath = resolve(selectedPath);

The corrupted path shows the suggested path (kebab-cased project name) being concatenated with the user's full path input. This indicates an issue with @clack/prompts text input handling or path resolution on Windows where user input gets mixed with the placeholder/initial value.

Suggested fix: In packages/cli/src/cli/commands/project/eject.ts:114, add path validation and sanitization before calling resolve(selectedPath) to prevent Windows path corruption and detect malformed paths.

---

Backend issues (not CLI fixes)

Error	Occurrences	Users	Command	PostHog
Agent name pattern validation	22	14	agents push	link

Backend API now enforces strict pattern ^[a-z0-9_]+$ for agent names, rejecting names like "Banner" that don't match lowercase requirements. This is a backend validation change, not a CLI issue.

User errors (working as designed)

Error	Occurrences	Users	Command	PostHog
No Base44 project found	62	22	link	link
--yes flag required in CI	34	17	deploy	link
Invalid agent file schema	21	10	agents push	link
Project already linked	17	10	link	link
App not configured	17	9	agents push	link
Deno dependency missing	7	6	exec	link
Authentication timeout	4	4	whoami	link

All validation messages are appropriate. CONFIG_NOT_FOUND errors show users running commands outside Base44 projects. Agent schema errors indicate users have invalid JSON in agent configuration files.

Recurring errors

Error	Days recurring	Existing issue	Tracked?
Windows path corruption (eject)	5+ days	Referenced in #448	No dedicated issue
Authentication timeout (unclassified)	19+ days	Referenced in #456, #451, #449, #448, #446	No dedicated issue

The authentication timeout classification bug continues to affect telemetry accuracy but was not present in today's data. Windows path corruption in eject command is an unresolved regression affecting Windows users.

Action items

1. [medium] packages/cli/src/cli/commands/project/eject.ts:114 — Add path validation and sanitization before resolve(selectedPath) to prevent Windows path corruption when user input mixes with suggested paths during interactive prompts