Error Report: 2026-04-09 (203 errors in last 24h)

[claude]

Summary

Critical path corruption bug in eject command affects Windows users, causing filesystem errors. Backend API continues experiencing timeout and entity validation issues. User validation errors remain at expected levels with clear CLI messaging.

Metric	Value
Time range	last 24 hours
Total errors	203
CLI bugs	1
Backend issues	4
User errors (working as designed)	6
Unique users affected	58
Internal user occurrences	5

Errors requiring action

1. Path corruption in eject command causing ENOENT errors — CLI bug

Error code	None (unclassified)
Occurrences	3 (0 internal)
Users affected	3
Command	eject
Platforms	Windows
PostHog	View in error tracking
Existing issue	None
Recurring	Yes (appears in previous reports)

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

Error: ENOENT: no such file or directory, mkdir 'C:\Users\<redacted>\site-scan-proC:\Users\<redacted>\Downloads\SiteScan'

Stack trace: (only CLI stack trace frames)

at runCLI (packages/cli/src/cli/index.ts:59:4)
at Command.parseAsync (commander/lib/command.js:1243:4)

Root cause: Path corruption occurs during Windows path resolution in the eject command:

// packages/cli/src/cli/commands/project/eject.ts:114
const resolvedPath = resolve(selectedPath);

// This path gets passed to:
// packages/cli/src/core/project/api.ts:85
await makeDirectory(projectPath);

// Which calls:
// packages/cli/src/core/utils/fs.ts:131
await mkdir(dirPath, { recursive: true });

The error shows two paths incorrectly concatenated: original input path and destination path get merged on Windows systems, suggesting an issue with resolve() or path handling in the eject flow.

Suggested fix: Add proper path normalization and validation in eject.ts:114 before calling resolve(), especially for Windows drive letter handling.

---

Backend issues (not CLI fixes)

Error	Occurrences	Users	Command	PostHog
Agent entity validation errors	46 (0 internal)	9	deploy	link
Deploy timeout errors	32 (0 internal)	8	deploy	link
App not found (404) errors	4 (0 internal)	3	secrets set, functions list	link
Network connectivity errors	2 (0 internal)	1	deploy	link

Agent validation errors indicate backend validation rules for entity references in agent configurations. Deploy timeouts suggest server-side performance issues during site deployment.

User errors (working as designed)

Error	Occurrences	Users	Command	PostHog
Config not found	58 (0 internal)	34	link, functions deploy	link
Link requires parameters	69 (5 internal)	27	link	link
Project already linked	22 (0 internal)	8	link	link
Schema validation errors	16 (0 internal)	10	eject	link
Missing build output	12 (0 internal)	6	deploy	link
Auth timeout	6 (0 internal)	6	dev, eject	link

These errors show proper CLI validation with clear messaging to guide users.

Recurring errors

Error	Days recurring	Existing issue	Tracked?
Path corruption in eject	3+ days	None	No
Deploy timeouts	Multiple days	None	No
Agent entity validation	Multiple days	None	No

The eject path corruption and backend timeout issues are untracked recurring problems.

Action items

1. [high] packages/cli/src/cli/commands/project/eject.ts:114 — Add Windows-specific path normalization before resolve() call to prevent path concatenation corruption
2. [medium] Monitor backend deploy timeout patterns — may need timeout adjustment or server-side optimization
3. [medium] Review agent entity validation logic on backend to reduce validation failures during deploy