0.1.71 — pin the Copilot CLI version
Pin the Copilot CLI to a version you trust, and open Settings without a crash.
Choose which Copilot CLI version your loops use
When a Copilot CLI release misbehaves, you can hold a known-good one. Make sure the version is present on each machine that runs Copilot, then set Settings ▸ Preferred versions ▸ Copilot CLI to it. New and resumed Copilot sessions use it, locally and over SSH, and so do Copilot title and summary requests. Sessions already running are untouched.
Leave it at Default and nothing changes. Copilot is the only backend whose CLI can select a version, so it is the only one listed; the other backends are unaffected either way.
Settings opens when your home folder is a recent project
Opening Settings could crash outright if your home folder was in the recent projects list, because the same template files were counted twice. Every template now appears once, and templates that share an identity across projects stay separately editable.
Both fixes in this release come from @ZekeAranyLucas. Thank you.
