v0.8.1 — always spawn a new session on project click

Multiple sessions per project directory

Clicking a project row now always spawns a new session against that directory instead of adopting the session already running there. You can run as many concurrent Claude Code sessions in one working directory as you want.

What changed

• SessionManager.create_session uniquifies the tmux session name on collision — cloude_foo → cloude_foo-2 → cloude_foo-3 … (capped at 999) — instead of redirecting into adopt_external_session.
• The collision check is the union of three sources of truth: the live tmux socket, in-memory backends, and the persisted owned_tmux_sessions set. That makes it agree with rename_session's own guard, so a name minted at create time can never be rejected by a later rename.
• The numeric suffix is appended after name sanitization, so it is never mangled.

Side benefit

Newly spawned sessions are no longer mislabelled with the EXTERNAL badge.

Still works as before

Explicitly attaching to a specific running session (from the running-sessions list) still goes through adopt_external_session — that path is untouched.

---

Install: download the DMG below, drag to Applications.

shasum -a 256 "Cloude.Code-0.8.1-arm64.dmg"

00f1beb6af6176ce904d3df472d5d6e37b4400736b2e04255cf72dcbcc89cfa5