Hey Anna app developers! ![]()
This batch gives your apps a gorgeous new home on the dashboard, opens up every model
to every plan, and squashes three gnarly forum-reported bugs
(#260, #278, #282 — thank you, as always!
).
And that “something big” we hinted at last time? It’s so close now. Hold that thought until next week… ![]()
Let’s dive in! ![]()
New Features
-
SpringBoard-style Apps desktop on the dashboard (beta.152) — The dashboard now has a top-level Chat | Apps toggle (URL-addressable via ?view=apps). The Apps view is a full-page grid of every installed UI app — with long-press edit mode (yes, they wiggle
), drag-to-reorder that syncs across devices, right-click context menus, and one-tap launch. More surface area and discoverability for your apps, right on the home screen! -
A warm new look (beta.150 & beta.151) — The dashboard traded Matrix green for a warm terracotta palette with refined typography and softer surfaces. Your app windows now live in a much cozier home. 
-
Every model, every plan (beta.150) — Plan-based model gating is gone: all active models are now available to users on every subscription tier. If your app uses sampling, you no longer need to worry about a user’s plan silently limiting which models can serve your requests. One less edge case to handle! 
Bug Fixes
-
CLI-published Executas can now actually be granted host.upload& friends (beta.147, forum #260) — Executas published via PAT (anna-app apps publishorexecuta publish) never registered their protocol manifest, so capability grant toggles never appeared and reverse-RPC tokens were refused (-32201 UPLOAD_NOT_GRANTED). Fixed in three layers: CLI 0.1.50+ uploads your manifest at publish time, the server backfills manifests on reinstall/upgrade/deploy for existing Executas, and capability strings are now validated fail-fast — a typo’d capability gets a loud error instead of a silently missing permission toggle. -
“Repair” no longer silently no-ops on degraded apps (beta.147, forum #278) — Dev-iterated apps could get permanently stuck showing “degraded” while Repair returned 202 and changed nothing. The reconciler now self-heals desired state from your app’s required Executas, tools that can’t be installed write an explicit failure reason instead of being silently skipped, and the installed-app detail panel shows per-tool error messages so you can see exactly what’s wrong and why. 
-
App Center no longer shows “No bundled Executa” for pre-release apps (beta.149, forum #282) — If your app had no released version yet (owner/reviewer view), the Bundled list came up empty even though your candidate clearly bundled tools. The detail view now falls back to the review candidate’s frozen bindings, with a “candidate” badge so everyone knows exactly what they’re looking at.
Compatibility Notes
Everything is additive — no manifest changes required. Existing apps keep working unchanged.
CLI 0.1.50+ is a safe, drop-in update — and re-publishing with it is the easiest way to get your Executa’s protocol manifest registered (see forum #260 above).
Extra-sharp eyes may spot some new fields and version bumps rippling through the stack. All optional, all dormant. For now. 
One More Thing…
Next week. That’s all we’re saying. If you took our earlier hint and started thinking about
what your app would look like on a smaller canvas — you’re going to be very glad you did. ![]()
![]()
Feedback Welcome!
Enjoying the new Apps desktop? Finally seeing real per-tool error messages on degraded installs?
Drop your questions, feedback, and wild theories below — this batch was once again powered by
your forum reports (#260, #278, #282
).
Happy building! ![]()
![]()