v0.8.2

[0.8.2] — 2026-07-17

A reliability release: live-session collaboration now shows the truth, quickly — plus the security and legal
fixes from the pre-beta audit.

Live sessions show who's live, and clear the instant it ends

• When a teammate ends a live session, everyone sees it end — right away, and everywhere. Before, the "● LIVE"
  badge could linger for minutes after a host stopped, and only cleared when you clicked the session. Three
  separate things were wrong: (1) the badge only tracked the project you were actively in, so a session going
  live or ending in a project you were merely looking at froze until you clicked into it; (2) the host's "end"
  could silently fail to publish — a network blip at the wrong moment left you advertised as live until a timeout,
  and closing the shared tab or deleting the shared project didn't stop it cleanly; (3) if you'd joined the
  session, your own connection knew the host was gone within a second or two, but the sidebar ignored that and
  waited on the slow sync. All three are fixed: every open project's badge stays current, ending is reliable and
  immediate, and a joined session clears in ~1–2 seconds. A hard crash (the one case nothing can clean up) now
  clears in about two minutes instead of five.

One kind of project

• Creating a project no longer asks "local or shared repo?" Every project starts as a plain private folder —
  the "Shared repo project" tile is gone. When you actually want it on your other devices or want a teammate in,
  use the project's ▾ menu (Sync across my devices / Invite someone): the same consented flow as before, with
  the same "creates a private GitHub repo — your transcripts stay out" confirmation. Nothing is created on
  GitHub until you say so, ever. Invites, discovery and already-synced projects behave exactly as before; folders
  you adopt still never offer sync (publishing someone's existing repo is not our call to make).

The model can no longer describe your repo from memory

• Claudible now injects the live git state of your project into the model's context on every prompt: branch,
  short commit, package.json version, up-to-date/ahead/behind-origin status, and the last commit subject —
  with an explicit instruction to never state "which version / what's shipped / is it done" from memory or the
  conversation summary. In a multi-machine, multi-collaborator, auto-syncing setup the repo genuinely moves under
  a long session, and a model answering from a 50-turn-old snapshot confidently reported a released project as
  having open bugs. Same cure as the machine-identity line: re-present the truth every turn instead of hoping the
  model remembers to check. Local-only git reads (never a fetch) — no network on the prompt hot path; when the
  local clone is behind origin, the line says so loudly and tells the model to git fetch before making claims.
  Commit subjects are collaborator-authored, so the line is sanitized like every other injected field.

Security & legal

• Third-party licenses now ship with the app. The installer bundles a handful of MIT-licensed libraries
  (ws, node-pty, xterm), and their licenses now travel with it in THIRD-PARTY-LICENSES.md, as those licenses
  require. Enforced by the test suite so it can't silently fall out of the build.
• The live-session guest cap is now enforced at admission, not just at connect. With approval on, a backlog of
  approvals could seat more than the 8-guest limit; it's now re-checked the moment each guest is let in.

Fixed

• A clearer error when "Install" needs admin rights. On first run, the System-check installer runs with no
  terminal, so on a machine without passwordless sudo the package install failed and unhelpfully reported "no
  apt/brew" — which was false. It now tells you exactly what to run yourself. The normal (passwordless / root)
  path is unchanged.

Docs

• An "Uninstalling" section, covering what a Windows uninstall intentionally leaves behind (your projects and
  the voice models) and how to reclaim it, plus how to stop the background voice services.
• The full-transcript sync is now spelled out. Turning on collaboration commits each session's entire
  transcript — including anything Claude read — into the private repo's history for collaborators to see. The
  in-app modal already said this; the README and SECURITY.md now do too.

v0.8.1

[0.8.1] — 2026-07-12

Two security fixes you should take, and the end of a sidebar bug we chased for ten rounds.

Security

• Adopting a folder could run code from that folder. When you point Claudible at a project you already have, it inspects the folder with git. Git can be configured — by the folder itself, in a file that travels inside it — to run a command of its choosing during ordinary, read-only-looking operations. Claudible already had a neutralizer for exactly this, and already used it everywhere else it touched git; the "adopt a folder" path was the one place it was missing, which is also the most likely place for a folder you didn't create to arrive. It's now applied there, and in every other script that runs git. If you've adopted a folder you got from someone else — a template, a zip, a repo you cloned from anywhere you don't fully trust — this is the fix to take.
• The invariant is now enforced by the test suite across the whole tree, rather than by a hand-written list of scripts to remember. A hand-written list is how the gap happened.

Fixed

• An apostrophe in your Windows or Linux account name broke every session. If your user folder was something like C:\Users\O'Brien\, Claudible couldn't launch a single Claude session — and said only "node-pty unavailable", which pointed nowhere. Every session, project, diff and clone command was silently aimed at a path that didn't exist.
• A session could sit in the sidebar wearing a "working" marker forever. If a turn ended in any way other than finishing cleanly — you pressed esc, the session died, Claude Code crashed — the sidebar never found out, and the row kept telling you it was busy indefinitely. The app's actual record of what's running always knew better (it's what stops a busy session being deleted or synced mid-turn); the sidebar simply kept its own, weaker copy. Now there is one record, and the sidebar reads it.
• The mid-turn marker is quiet again. A running session is marked with the small pulsing dot the sidebar already used elsewhere, instead of repainting the whole session title red — which shouted, and which put a red title next to a green ● LIVE badge on the same row.
• A project you renamed and then deleted came back. Deleting a project remembers it by GitHub's permanent id now, not by the name it had before you renamed it — which is a name GitHub no longer reports, so the two never matched and the project reappeared as a fresh invite on the next launch.
• macOS: closing a tab left the session running. The guard that stops Claudible killing an unrelated process reads a file that only exists on Linux, so on a Mac it never confirmed the process and never cleaned anything up — on every tab close and every tab switch. A leftover session holds its conversation open and forces the next resume to fork it, which is where "(empty session)" entries come from. (Fixed in code; still unverified on real Mac hardware.)
• A deleted project's sync state is now dropped from memory along with its other caches.

Docs

• "Share live" tells your collaborators, and now the docs say so. In a synced project, sharing a session live also publishes the invite link to the project's shared branch — that's how a teammate sees the ● LIVE badge and can click Join without you sending anything. It also means anyone with git access to that repo can read the link. Nobody gets in without your by-name approval, but you should know it's there. To share with exactly one person, use Share and hand them the link yourself.
• Releases now carry their changelog section as release notes, instead of publishing an empty body.

v0.8.0

Claudible v0.8.0

A hardening pass with one new behavior: renaming a project renames its
GitHub repo (your transcripts are never touched).

Also: the sidebar tells the truth (no stale rail, no phantom sessions, no
flicker, the active tab always has a row); synced changes and invited
projects land without a nudge; a failed clone can no longer delete a folder
that was already there; and the Linux terminal keeps its pty fallback.

v0.7.0

v0.7.0 — multiplayer identity, session-history complete + default ON,…

v0.6.0

Claudible v0.6.0

v0.5.4

chore(release): v0.5.4 — dependency provisioner + Connect-Claude button

First release carrying the self-bootstrapping dependency provisioner (System check) and the Connect-Claude button/popup + graceful terminal, so a fresh Windows machine can install Claude Code itself instead of crashing on a missing 'claude'.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

v0.5.3

Fix session-sync setup failing on native Windows (missing sessions + …

v0.5.2

fix(win): custom workspace folders land in the right place (mixed C:/…

v0.5.1

fix: desktop shortcut always, Claude-connect override on Windows, clo…

v0.5.0

feat(sync): cross-device workspace sync — one-call discovery + local→…