fix(startup): scope generated-content and upload dirs to the current user

[localai-bot]

What

Scope the default --generated-content-path and --upload-path to the current user so LocalAI no longer fails to start on multi-user hosts.

Why

The defaults were the fixed, shared locations /tmp/generated/content and /tmp/localai/upload. On any machine with more than one account these collide:

• macOS routes /tmp to the shared /private/tmp for every user. Whichever account starts LocalAI first creates the parent directory with 0750 perms, and every other account then fails startup with:

  ERROR Error running the application  error=LocalAI failed to start: unable to create ImageDir: "mkdir /tmp/generated/content: permission denied".
  ERROR Error running the application  error=LocalAI failed to start: unable to create UploadDir: "mkdir /tmp/localai/upload: permission denied".
  

• The same happens on Linux once a stale root-owned /tmp/generated (e.g. from a prior sudo run) is left behind.

This was observed on macOS both with the desktop launcher and with the raw binary invoked directly by apps that embed LocalAI (Wingman, nib-desktop), which start local-ai run with no path flags.

How

• Server defaults (root cause): both paths now default under the OS temp dir via os.TempDir() (honoring POSIX $TMPDIR, and already per-user on macOS) namespaced by the current UID: TMPDIR/localai-<uid>/generated/content and TMPDIR/localai-<uid>/upload. Wired through new kong vars in cmd/local-ai/main.go (cli.DefaultGeneratedContentPath / cli.DefaultUploadPath) so every consumer of the raw binary inherits the fix. The paths stay ephemeral; all content subdirs (audio, images, …) derive from GeneratedContentDir, so they are fixed transitively.
• Launcher (defense in depth): the desktop launcher now anchors these two paths under its own per-user data directory too, mirroring the Launcher does not pass --data-path, --config-dir, or --state-dir to local-ai run, causing state dirs to resolve to ~/data and ~/configuration instead of under ~/.localai #10610 fix for data/configuration. The local-ai run arg assembly was extracted into a testable BuildRunArgs.
• Docs: updated cli-reference.md.

Overrides are unchanged: LOCALAI_GENERATED_CONTENT_PATH / --generated-content-path (and the upload equivalents) still take precedence, and TMPDIR=/somewhere relocates the whole tree.

Verification

$ local-ai run --help | grep -E 'generated-content-path|upload-path'
  --generated-content-path="/tmp/localai-1000/generated/content"
  --upload-path="/tmp/localai-1000/upload"

$ TMPDIR=/blah local-ai run --help | grep -E 'generated-content-path|upload-path'
  --generated-content-path="/blah/localai-1000/generated/content"
  --upload-path="/blah/localai-1000/upload"

New unit tests: core/cli/run_paths_test.go (server defaults are user-scoped, not the historical shared paths) and a BuildRunArgs spec in cmd/launcher/internal/launcher_test.go (launcher keeps generated-content/upload under its data dir, never /tmp).

Assisted-by: Claude:claude-opus-4-8 [Claude Code]