Skip to content

v0.14.1 — callsigns by default, first-run screen order, cloud 403 guidance - #34

Merged
DevMando merged 1 commit into
mainfrom
release/v0.14.1
Jul 29, 2026
Merged

v0.14.1 — callsigns by default, first-run screen order, cloud 403 guidance#34
DevMando merged 1 commit into
mainfrom
release/v0.14.1

Conversation

@DevMando

Copy link
Copy Markdown
Owner

Summary

Fast-follow polish from watching 0.14.0's first run on a truly fresh machine, in three parts: friendlier default agent names, a fixed first-run recovery screen, and honest guidance about cloud model pricing.

What changed

  • New agents get callsigns by default. Tabs open as Morphy, Kernel, Cloud instead of Agent 1, Agent 2. The Settings toggle still switches to numbered naming, and anyone who explicitly chose numbering keeps it — only the default for fresh state flipped.
  • The "can't reach Ollama" screen leads with the likely fix. New order: Install Ollama for me → Open the Ollama Download Page (I'll install it myself) → Change the Endpoint URL (Not Recommended) → Retry → Cancel Setup. Previously the endpoint override — the one option a fresh machine never needs — was listed first. The message now opens with a plain-language diagnosis; the raw socket error still shows, dimmed, for diagnosability.
  • Cloud subscription awareness. ollama.com cloud models require an account with an active cloud subscription; without one, requests fail with 403 Forbidden, which previously surfaced as a raw error that looked like the app breaking. The requirement is now stated at every selection point (starter picker, sign-in prompt, every model switch to a cloud tag), and a 403 gets its own explanation card pointing at the two real fixes: subscribe, or switch to a free local model. Deliberately separate from the 401 path — the sign-in walkthrough cannot fix a 403 and would loop.

Scope and risk

Desktop-only; no engine changes. Version bumped to 0.14.1, changelog rolled. Low risk: option-label strings, transcript messages, and one boolean default.

Verification

225/225 tests pass, including two new ones: a 403 response emits the subscription card without triggering the sign-in walkthrough, and prose containing "403" alone does not false-positive.

…dance

- New agents draw callsigns by default; numbered naming becomes the opt-in
  (explicit prior choices are preserved via the panel-state null-coalesce)
- Can't-reach-Ollama screen: install actions lead, endpoint override marked
  Not Recommended, plain-language diagnosis with the socket error dimmed
- Cloud models need an active ollama.com subscription: stated at every
  selection point, and 403 responses get an explanation card instead of a
  raw error (distinct from 401 — the sign-in walkthrough can't fix a 403)
@DevMando
DevMando merged commit ff12a04 into main Jul 29, 2026
1 check passed
@DevMando
DevMando deleted the release/v0.14.1 branch July 29, 2026 05:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant