Can't launch (ENOENT)

[dwiehoff]

starting using freebuff fails:

Unhandled rejection: ENOENT: no such file or directory, mkdir '/Users/dwiehoff/.config/manicode/projects/drift/chats/2026-06-08T11-25-20.691Z'
    path: "/Users/dwiehoff/.config/manicode/projects/drift/chats/2026-06-08T11-25-20.691Z",
 syscall: "mkdir",% >> freebuff               
   errno: -2,lete! Starting Freebuff...
    code: "ENOENT"

      at mkdirSync (unknown:1:1)
      at ttA (src/project-files.ts:10:3)
      at vS (src/project-files.ts:96:3)
      at EnA (src/utils/logger.ts:139:23)
      at GPL (src/utils/fingerprint.ts:179:12)
      at processTicksAndRejections (native:7:39)

[ubuntupunk]

have the maintainers changed the .config/manicode layout by any chance? I am experiencing an immediate sigkill on start.

[SOUMITRO-SAHA]

As of my research:

What's happening:

When you start freebuff, it tries to create a folder to save your chat logs at ~/.config/manicode/projects/[your-project]/chats/.... But it fails because that folder can't be created.

Why it fails:

During startup, freebuff runs a "fingerprint" step (for login). When that step logs a message, the logger tries to prepare a log file — which means creating the chat folder. The code that creates the folder isn't wrapped in a try-catch, so the crash propagates up and kills the whole app. The logger already has a try-catch around getProjectRoot(), but not around getCurrentChatDir().

Whether this is intentional or a bug, I'm not sure — but it causes a hard crash on launch. I've put up a fix in PR that wraps the call in a try-catch so the logger degrades gracefully (skips file logging) instead of crashing. Really looking forward to the maintainers' thoughts on this.

[codebuff-team]

Marking this stale - there has been no activity here for 72 days. It will close in 7 days unless someone comments.

This is backlog upkeep, not a verdict on the issue. A single comment keeps it open, and anything closed this way can be reopened.

[codebuff-team]

Closing this as stale - no activity since it was flagged 7 days ago. Reopen it any time if it is still relevant; that is not a hassle and we would rather have it open than lost.

_{Closed automatically by the community triage bot. If this is wrong, reopen the issue or reply and a maintainer will take another look.}