Skip to content

ccr Desktop v0.1.5 — messages stop vanishing, and the app stops living at /

Choose a tag to compare

@github-actions github-actions released this 17 Jul 03:43
· 7 commits to main since this release

Three fixes, all of which only ever bit the shipped app — which is why they survived this long.

Your messages stopped disappearing (#17)

After the first message in a session, every reply you sent flashed on screen and vanished. Writing the session file woke the file-watcher, which reloaded the transcript from disk and wiped the message you'd just typed — it isn't saved until the reply finishes. Same-session reloads are now additive; only switching sessions replaces the view.

Better default model (#18)

New default is openai/gpt-oss-120b, replacing llama-3.3-70b-versatile. It's the more reliable tool-caller, and the only model available on all four upstream providers — so the app can fail over across every provider instead of a subset. If you've picked a model from the dropdown before, your choice is kept. Delete model from ~/.ccr/config.json to take the new default.

The app no longer runs from your filesystem root (#19)

This is the important one. Launched from Finder/Dock, a packaged app inherits / as its working directory — so every session created with v0.1.4 was rooted at your filesystem root, giving the agent's file tools the run of the whole disk and scanning / for project context. It never appeared in development, where the working directory is the project folder.

v0.1.5 refuses to root a session at /, ever. Launched from Finder it now uses your home folder. Existing sessions keep their history but can no longer operate at /.

A proper folder picker is coming; for now you can pin a project by setting projectRoot in ~/.ccr/config.json.


macOS: unsigned, same as previous releases. If Gatekeeper blocks it:

sudo xattr -cr /Applications/ccr.app

Downloads: Apple Silicon and Intel DMGs, Windows installer + portable, Linux AppImage.

Also the first release ever built by CI rather than by hand — every previous tagged run failed on a misconfigured publish step.