Repository navigation
Releases
Beans 1.0.14
Beans 1.0.14 ships the coral Beans app identity and all-platform release artifacts. The website is live at https://usebeans.app.
The all-platform workflow succeeded for macOS, Windows, Linux, Android and iOS. The Mac app is Developer ID signed, notarized and stapled. Android APK version code 6 and store AAB version code 7 use the retained Beans upload key. The iOS store IPA is version 1.0.14, build 4, with signed app and notification extension.
The Ed25519-signed readiness inventory contains 31 distribution assets and binds exact source 5d13389, protocol 3, sizes and SHA-256 digests. GitHub exposes the Windows installer as Lorca.Setup.1.0.14.exe; its bytes match the inventory's staged filename Lorca Setup 1.0.14.exe.
Windows installers have updater integrity signatures and do not have Authenticode publisher signing. The store IPA requires TestFlight/App Store distribution and is not an ad-hoc installer. Play and TestFlight uploads, public store approval, and real-device pairing/push/install/upgrade acceptance remain separate steps.
Beans 1.0.13
Beans 1.0.13 release source.
Mobile release profiles pin Bun 1.4.2 to match the checked-in lockfile. Platform release notes are present and checked before builds.
All-platform artifacts are being built and verified. Deployment readiness is established only when the signed beans-update.json inventory and its signature are present. Store testing uploads are separate.
Beans 1.0.12
Beans 1.0.12 build attempt.
Mobile builds failed during dependency installation because the EAS image used Bun 1.3.14 with a Bun 1.4 lockfile. This release has no completed signed app inventory and is not ready for deployment. The compatible Bun version is pinned for the next release attempt.
Beans 1.0.11
The first server-only Beans release targets Linux relay, Runner and updater assets
under beans-v1.0.11. The Cargo component version remains 0.1.10; desktop package
metadata remains independent. Signed readiness must be finalized before automatic
updates can use this release; this server scope does not authorize native client updates.
Includes upstream #61, #62, #65 and #66:
- Commands on macOS and Linux run in their own terminals. Bots can start background commands, and users can send a waiting command to the background so the bot continues. Running tasks exposes their output and Stop; stopping a chat turn leaves background commands running.
- Groups carry an editable description that reaches every member's system prompt, alongside the group's name and owner.
- Provider, sign-in, relay and HTTP MCP requests use configured environment proxies or the macOS/Windows system proxy. PAC files and macOS proxy bypass lists are not read.
- HTTPS uses system certificate trust on macOS and Windows, including administrator-installed roots, and system plus bundled roots on Linux. Certificate failures expose the underlying cause; the phone core retains bundled-root trust.
- Server updates verify schema-1 readiness with the Beans Ed25519 public anchor and verify artifact hashes before installation. Finalized release bytes and inventories are immutable. The updater upgrades and checks the relay's component version and compatible protocol before moving Runners.
- Renewable, token-authenticated Runner admission leases hold new work while existing turns, routines, commands and remote waits finish. Queued relay work remains pending; cancellation or lease expiry resumes admission without changing account Pause.
- Binary and catalog replacement retains synced originals and a durable, service-bound recovery journal. Interrupted swaps reuse those originals for recovery and rollback; incompatible databases are never automatically restored.
- Release failures hold the failed root version until a newer release or explicit operator clearance. Configuration, authentication, unsafe-path and recovery faults hold all further rollout until repaired and cleared; a busy Runner cancels its lease for a later pass.
- Unattended Linux updates require trusted bootstrap, root-owned configuration, immutable executables, matching Runner drain tokens and explicit timer enablement after a successful manual pass. Release publication and live deployment remain separate operator actions.
Server-only release: signed Linux relay/Runner archives and the signed server updater. Phone and desktop artifacts are not part of this release.