Skip to content

ElastOS 2.0.1

Latest

Choose a tag to compare

@andersalm andersalm released this 11 Nov 17:17

ElastOS 2.0.1 makes Browser ask before it goes online, brings Browser to the Jetson and other Linux ARM computers, and fixes updates, Undo and staying connected.

Install

curl -fsSL https://elastos.elacitylabs.com/install.sh | bash

Runs on Apple Silicon Macs and on Linux (x86-64 and ARM64, including NVIDIA Jetson). When the installer says "ElastOS 2.0.1 is ready", run the Open Home command it prints, then create your passkey.

What's new

These are the same notes System shows when the update is ready.

Added

  • Browser runs on a Jetson and other Linux ARM computers with KVM. Turn it on once with elastos setup --browser, which asks before its one-time administrator step, then restart Home.
  • System, About lets you choose Stable or Test versions for updates. Your passkey confirms the change, and switching never installs an older version.

Changed

  • On a Jetson, Browser uses more of the processor, so scrolling is about twice as smooth.
  • On Linux, the install command no longer sets up Browser or downloads it. Browser is turned on when you choose it.
  • Known issue: on a Jetson, Browser scrolls much more slowly than a browser running directly on the computer (#90).

Fixed

  • Open apps, including Chat, stay connected while Home runs, and reconnect by themselves after a network drop or a restart.
  • Assistant keeps a finished answer in view, also while you type a longer question.
  • Assistant follows a growing answer only while you are at the end, and Jump to latest no longer flashes while an answer streams.
  • A busy Home no longer tells people that their shared model access is inactive.
  • When a Browser session has expired, Browser says so instead of showing a connection message.
  • The install command repairs file permissions in an older Linux or Jetson Home that you own, and shows one command for files owned by the administrator.
  • The install command works whatever language the computer is set to.
  • Closing Browser no longer fails when another program uses a port Browser's media relay may need.
  • When an update check gets no answer, Home tries once more on a new connection.
  • When a Linux computer is short of free space, Browser says how much it needs to open.
  • Updating, or using Undo, on a computer where Browser is set up no longer stops with "installed release support changed". Browser's Python no longer changes ElastOS's own files.

Security

  • Browser opens websites only after you allow internet access with your passkey in Inbox, where you can also turn it off.
  • Known issue: Home itself shows the approval, not a separate ElastOS screen, so read the request before you confirm with your passkey (#178).
  • Known issue: after Undo to 2.0.0, Browser goes online again without asking (#559).
  • Community room access ends when your sign-in ends.

Updating

  • From 2.0.0: update in System, About. Your data stays. The first time you open a website afterwards, Browser asks in Inbox; allow it with your passkey.
  • From a test version (2.0.1-rc.1 or rc.2): update in System, About. To get only Stable versions from now on, choose Stable there; switching never installs an older version.
  • If you ran the install command between 9 and 11 November, you got a test version: check System, About and choose Stable if you want only Stable versions.
  • A Home that stopped with "installed release support changed" on 2.0.1-rc.1 needs a manual repair first. Ask in #535.
  • From anything older than 2.0.0: follow Updating on the 2.0.0 page.
  • On a Jetson or another Linux ARM computer with KVM, Browser stays off until you run elastos setup --browser once. It asks before its one-time administrator step and downloads about 900 MB. Then restart Home. Browser is not available on Linux x86-64.
  • Undo runs in a terminal, returns to the version you had before and leaves Home stopped (#509). After Undo to 2.0.0, Browser goes online again without asking (#559).

Known issues

Found after the in-app notes were final, so System does not show them:

  • Direct messages between two Homes on different home networks stay at Sending: Homes connect to each other directly, and the shared meeting point that lets two Homes behind routers reach each other is not in this release (#345). Restarting does not help. Posts in Community reach everyone; they pass through the main Community node, which can read them.

  • Browser on a Jetson was not tried on this final build. It worked, slowly, on an earlier 2.0.1 test build (#90).

  • Browser's permission has rough edges, each with a simple way out (#566):

    • after Don't Allow or Turn Off, an address you typed is not opened when you then allow access: press Return on it again;
    • if Home stops answering for a moment while Browser waits for your answer, that Browser window stops noticing your answer: close it and open Browser again;
    • a Browser window in full screen is not brought back after you allow access: click Browser in the Dock;
    • a request left unanswered for 30 minutes leaves nothing to allow in Inbox: press Return in Browser again.

    Fixes are planned for 2.0.2.

  • A component Home uses to look up internet addresses has published flaws (RUSTSEC-2026-0487 to 0491). The one that applies to Home lets a tampered address reply make Home use too much memory. It cannot read your data. 2.0.0 has the same component. A fix is planned for 2.0.2 (#569).

Still open from 2.0.0:

  • While a Test version is out, a Stable Home says "Could not check for updates" (#564).
  • On a Mac that uses local AI on 2.0.0-rc.1 or an earlier test version, updating fails and keeps your version. The workaround is in #515.
  • After elastos update or Undo in a terminal, Home stays stopped. Start it with elastos home --browser (#509).
  • AI models cannot read files, open websites or send messages. The small SmolLM2 135M model often pretends it did (#455).
  • Library can lose a save if a file is saved from two places at once, or renamed, moved or deleted meanwhile (#480).
  • Unsaved Documents edits are lost when sign-in ends after 12 hours without Home running (#497). Importing a Recovery Kit does not ask for your passkey (#403).
  • Browser has no Chinese, Japanese or Korean fonts.
  • Not done yet: Home can still use every app's permissions, and background services run with your account's rights (#173).

The developer detail is in the changelog.

Check what you install

The installer checks the release signature and each file's checksum. To check by hand:

  • Signer: did:key:z6MkgwHd2BCWe1jHMXPiR6H1q1RFPcv1YzhMbK5G1kBarbfe
  • Signed release: QmNkZQSd8t7EJbdtN23h9XXxy45o5NNQcoLt7ivxPn4Xtg, named in release-head.json (attached, and served at https://elastos.elacitylabs.com/release-head.json)
  • Source: tag v2.0.1, commit bde18c7bae6564db934cd406c1070b32499473ec
  • Build: package run 42969056808
  • SHA256SUMS lists all 156 signed files. The attached install.sh and Runtime binaries (elastos-aarch64-darwin, elastos-aarch64-linux, elastos-x86_64-linux) are the same bytes the installer downloads. To install, use the command above.
  • Each build-receipt-<platform>.json lists every file built for that platform with its sha256, and GitHub's attestation shows the release workflow made it from the tagged commit:
gh attestation verify build-receipt-aarch64-darwin.json \
  --bundle build-receipt-aarch64-darwin.sigstore.jsonl \
  --repo elastos/elastos-runtime

Report problems in issues.

Full changelog: v2.0.0...v2.0.1