You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
CLI socket (diffusion-studio.sock) never created; every dapi command fails with 'not running' even though the app IS running and a project is open #60
Reproduced on a completely clean install via the official Homebrew cask (brew install --cask diffusionstudio/tap/editor), version 0.204.1, on macOS (Apple Silicon).
Steps:
Fresh install via brew cask (previously also tried a manual .dmg install with the same result).
Launched the app, signed in (existing account, Free Plan).
Confirmed the app process is running and holds its own SingletonSocket lock file.
Opened a real project (an existing project auto-reopened on launch: 'Wild Ocean 5 Sep', with a scene visible in the editor).
Ran 'dapi context', 'dapi whoami', 'dapi logs' -- all fail identically with: 'Diffusion Studio is not running. Launch the app first, then retry.'
Inspected dapi's own source: it expects a Unix socket at $TMPDIR/diffusion-studio.sock (os.tmpdir() in Node). Confirmed via lsof that the running app process never creates this file -- only its own internal SingletonSocket lock exists, never diffusion-studio.sock.
Tried: restarting the app, reinstalling via the official brew cask from scratch, running dapi from a shell with a corrected $TMPDIR matching the real macOS per-user temp dir, and using the app's own 'Install dapi Command Line Tool...' menu item (installs the CLI symlink but does not appear to affect the runtime socket).
Expected: dapi should be able to connect to a running instance with an open project.
Actual: every dapi command fails immediately as if the app were not running at all, even though it demonstrably is.
Closing as obsolete — the transport this is about no longer exists.
Your diagnosis was right for 0.204.1: `dapi` did expect a Unix socket at `$TMPDIR/diffusion-studio.sock`, and the app did not reliably create it. That whole mechanism is gone. `apps/desktop/src/cli-server.ts` was removed in 059e1f6 (2026-09-03) and there is no socket code left in `apps/cli/src` — the CLI now speaks MCP over Streamable HTTP on a fixed loopback port. There is no socket file to be missing, and no $TMPDIR dependency to get wrong. (PR #64, which moved the socket under $HOME, was closed for the same reason.)
Current `main` is v0.209.0. Please update and re-run `dapi context`; if it still reports the app as not running with a project open, reopen this or file a fresh one — the failure would have a completely different cause and is worth tracking separately.
Thanks for the thorough triage, especially checking `lsof` and trying the corrected `$TMPDIR` — that ruled out the obvious explanations.
Activity
k9p5 commentedon Oct 1, 2026
Closing as obsolete — the transport this is about no longer exists.
Your diagnosis was right for 0.204.1: `dapi` did expect a Unix socket at `$TMPDIR/diffusion-studio.sock`, and the app did not reliably create it. That whole mechanism is gone. `apps/desktop/src/cli-server.ts` was removed in 059e1f6 (2026-09-03) and there is no socket code left in `apps/cli/src` — the CLI now speaks MCP over Streamable HTTP on a fixed loopback port. There is no socket file to be missing, and no $TMPDIR dependency to get wrong. (PR #64, which moved the socket under $HOME, was closed for the same reason.)
Current `main` is v0.209.0. Please update and re-run `dapi context`; if it still reports the app as not running with a project open, reopen this or file a fresh one — the failure would have a completely different cause and is worth tracking separately.
Thanks for the thorough triage, especially checking `lsof` and trying the corrected `$TMPDIR` — that ruled out the obvious explanations.