[Bug]: deauth-claude fails due to permission error on /app/.automaker

[decoge]

Operating System

Windows

Run Mode

Docker

App Version

0.9.0

Bug Description

Trying to deauthenticate Claude fails with a filesystem permission error. The server attempts to create a directory at /app/.automaker, but the container user does not have write access to /app.

This results in a 500 error and prevents Claude deauthentication from completing.

Environment:
Windows (WSL2 running Ubuntu Linux)

Steps to Reproduce

1. Run Automaker using Docker (default setup)
2. Open the app and go through setup
3. Go to Settings and click on 'Sign Out' from Claude
4. Observe server error

Expected Behavior

The Claude deauthentication process should complete successfully without filesystem errors.

Actual Behavior

The request fails with a permission error:
ERROR [Setup] ❌ Deauth Claude failed: Error: EACCES: permission denied, mkdir '/app/.automaker'

Screenshots

Relevant Logs

OPTIONS /api/setup/deauth-claude 204

ERROR [Setup] ❌ Deauth Claude failed: Error: EACCES: permission denied, mkdir '/app/.automaker'

    at Module.mkdirSync (node:fs:1363:26)

    at file:///app/apps/server/dist/routes/setup/routes/deauth-claude.js:15:20

    at Layer.handleRequest (/app/node_modules/router/lib/layer.js:152:17)

    at next (/app/node_modules/router/lib/route.js:157:13)

    at Route.dispatch (/app/node_modules/router/lib/route.js:117:3)

    at handle (/app/node_modules/router/index.js:435:11)

    at Layer.handleRequest (/app/node_modules/router/lib/layer.js:152:17)

    at /app/node_modules/router/index.js:295:15

    at processParams (/app/node_modules/router/index.js:582:12)

    at next (/app/node_modules/router/index.js:291:5) {

  errno: -13,

  code: 'EACCES',

  syscall: 'mkdir',

  path: '/app/.automaker'

}

Additional Context

This is a Docker filesystem permissions issue.
The server runs as a non-root user, while /app is owned by root. When the app tries to create /app/.automaker during Claude deauth, it fails with EACCES. Creating/chowning this directory at build or startup time (or using a writable path like /data) could resolve the issue.

Checklist

• I have searched existing issues to ensure this bug hasn't been reported already
• I have provided all required information above

[Material-Scientist]

I also got this error when updating settings. Logs say it failed to write to settings.json, but after manually checking the file, the changes were actually applied. I only saw this as of v0.12.0

[Shironex]

This issue was created on an older version (v0.9.0) and the latest release is v0.13.0 (with v0.14.0-rc coming soon), so this may already be fixed or outdated.
I’m going to close this for now, but please feel free to reopen it (or create a new issue) if you can reproduce it on the latest version

i suggest using v0.14.0rc as its got bunch of fixes