Cloud models load after signing in
Cloud models now load after signing in — the app was fetching the model list without presenting your login.
Changelog
Every Neumann release, newest first. The desktop app updates itself — this is what each one changed.
Sign-in completes through the deep link
Sign-in now completes through the neumann:// deep link — the browser hands the login straight back to the app, with no local port or hostname matching involved.
Sign-in opens the real login page
Sign-in now opens the real neumann.decentparadox.me login page (installed builds were being redirected to a local development address).
Cloud works on installed builds
Cloud features now work on installed builds without any configuration: the app always knows the hosted Neumann Cloud API, and the profile menu correctly offers Log in when you are signed out. Sign in once and models, cloud runs, and GitHub connect all light up.
Login and GitHub connect out of the box
Login and GitHub connect now work out of the box on installed builds: sign-in no longer depends on server auth configuration, and the GitHub device-flow app is built in. This build also ships the current UI (the previous packages bundled a stale web build — this is why the update badge never appeared).
Sign-in on installed builds
Fixes sign-in on installed builds: the desktop server now defaults to single-user auth, so Login with Neumann works out of the box and cloud models load after signing in. The Neumann agent's model list now explains what to do when empty instead of pointing at the wrong setting.
Run agents in the cloud
The release that put a machine behind the composer.
Run agents in the cloud
- Cloud sandbox runs — pick Cloud in the composer's environment menu and the prompt runs in an isolated sandbox against your repository, coming back as a branch and a pull request. Pick a local worktree instead to keep the work on your own machine, or create a new worktree without leaving the composer.
- Connect a repository — link your forge from the chat with a device code, nothing to paste.
- Repository picker — cloud runs target your repository's origin by default; point them at any repository your account can see.
- Forge connections and provider keys persist across restarts, encrypted at rest.
Safer by default
New chats start restricted: shell commands and file writes ask for approval directly above the composer, and you can switch a single chat to full access when you want it to run unattended.
Update-channel baseline
Update-channel baseline (manifest only).