Install Ethen Desktop

The /download route is the verified entry point for Ethen Desktop. Supported operating-system versions, processor architectures, installer names, signing or notarization state, installation directories, update channels, update frequency, and rollback behavior remain undocumented. This page explains what must be verified around installation without fabricating platform-specific commands or release promises.

System requirements

The release package must provide the authoritative operating-system, architecture, signing, and hardware information. Until that material is available, this page can state only the functional dependencies: Ethen Desktop must expose the preload bridge, a supported runtime must be installed and started separately, and at least one model must be available through that runtime. Do not translate those dependencies into unsourced version numbers or package names.

No approved release matrix defines supported platforms or minimum hardware. Confirm compatibility from the actual release offered on /download. Do not infer an operating system, CPU architecture, memory requirement, GPU requirement, or disk estimate from the existence of the Desktop bridge.

The Desktop application and model runtime are separate dependencies. Even when Desktop installs successfully, Local Chat still needs a detected runtime and at least one installed model. Hardware requirements also depend on the model, quantization, context length, and acceleration path.

If the download page does not present a compatible artifact for the current device, stop rather than using an unverified package.

No approved release matrix defines supported platforms or minimum hardware for Ethen Desktop. Ethen Desktop is required for the preferred local-model bridge and local generation path. The browser fallback does not create local inference and reports that Desktop plus a runtime are required. /download is a valid marketing route, but exact release-artifact filenames, checksums, package formats, and platform-compatibility details are not documented here. Confirm those release details on the approved download page.

Ethen Desktop is required for the preferred local-model bridge and local generation path; open the approved download page and confirm that a release artifact is offered for the current device. No approved system-requirements matrix identifies operating systems, CPU architectures, memory, disk, or GPU support; launch Ethen Desktop, then check Local Models for bridge and runtime status. Do not infer an installer filename, terminal command, supported OS, signing state, or update behavior from the existence of the download route.

Install

Open /download and follow the instructions packaged with the current release. Stable installer filenames, shell commands, signing details, and installation directories require release-engineering confirmation.

Use only artifacts and integrity guidance presented through the approved release path. Do not substitute third-party packages or copy commands from an unrelated runtime guide.

The download route is verified, but exact packages and commands must come from the release presented there. No approved system-requirements matrix identifies operating systems, CPU architectures, memory, disk, or GPU support. No verified contract describes automatic updates, update channels, forced upgrades, rollback, or release cadence. The local runtime is a separate dependency from the Desktop application.

At /download, use only the installation instructions and integrity information presented with the approved release; do not infer a platform, package format, or signing state that the page does not show. The local runtime is a separate dependency from the Desktop application; install and start a supported runtime using its own approved documentation. If the page does not offer a compatible build, stop rather than using an unverified package or path.

Launch

A successful launch should expose the Desktop bridge rather than the browser fallback. Open Local Models and inspect runtime status. If the application reports that Desktop or a runtime is required, the local-generation path is not ready even though the web interface loaded correctly.

Desktop readiness and runtime readiness are separate. The application can launch while the model server is stopped, and the runtime can be running without an installed model. Verify all three layers—Desktop, runtime detection, and installed-model inventory—before diagnosing Local Chat.

Launch Ethen Desktop after installation. Desktop makes the local-model bridge available, but it does not automatically start or install a model runtime.

Open Local Models and check whether a runtime is detected. Browser mode uses a safe fallback that reports no runtime and cannot generate a response. If the interface still behaves like browser fallback, confirm that the Desktop build is running and that its bridge loaded correctly.

A detected runtime with no installed models is not ready for Local Chat. Start the runtime and install a model using its verified process before continuing.

Launching Desktop makes the bridge available but does not automatically start a model runtime. After launch, the application must still detect a runtime and at least one installed model before Local Chat can generate. Launch Ethen Desktop, then check Local Models for bridge and runtime status. Install and start a supported runtime using its own approved documentation.

Automatic updates, update channels, forced upgrades, rollback, or release cadence lacks a verified contract; launch Ethen Desktop, then check Local Models for bridge and runtime status. Ethen Desktop is required for the preferred local-model bridge and local generation path; return to Local Chat only after an installed model appears.

Sign in

The supplied installation files do not establish a mandatory sign-in flow for local-runtime detection. Do not invent an account step, role, workspace, or credential requirement for this page.

If the current release asks the user to sign in, follow the labels and policy shown by that build, but keep the local runtime check separate. Account access does not automatically install a runtime or make a model available.

Never place runtime or provider credentials into a generic sign-in field unless the current product explicitly identifies that field and its handling contract.

No mandatory sign-in flow is verified for local-runtime detection. Return to Local Chat only after an installed model appears. Open the approved download page and confirm that a release artifact is offered for the current device.

After launch, the application must still detect a runtime and at least one installed model before Local Chat can generate; install and start a supported runtime using its own approved documentation. Open /download, confirm that a release artifact is offered for the current device, and verify the installation and integrity details presented with that release.

Update

No verified contract describes update channels, automatic updates, forced upgrades, cadence, rollback, or release compatibility. Do not promise that Desktop checks, downloads, or installs updates automatically.

Use the current release’s approved update guidance. Before replacing a working build, record the Desktop version, runtime provider and version, endpoint label, and installed-model inventory so that compatibility issues can be diagnosed.

Model and runtime updates are also separate from Desktop updates. A new application build does not guarantee that the runtime or installed models are updated.

Update channels, cadence, forced upgrades, and rollback behavior remain unverified. Use only the installation instructions and integrity information presented with that release.

The browser fallback does not create local inference and reports that Desktop plus a runtime are required; return to Local Chat only after an installed model appears. Automatic updates, update channels, forced upgrades, rollback, or release cadence lacks a verified contract; use only the installation instructions and integrity information presented with that release.

Troubleshooting

If the download page does not identify a compatible package, stop and request current release guidance. Do not use an unverified installer, bypass operating-system trust checks, or infer support from a generic marketing control. Release engineering must confirm the package and signing state.

Separate installation, bridge, runtime, and model problems:

• No compatible download appears: the current release is not verified for the device.
• Desktop does not launch: use the release-specific diagnostics; package and signing behavior are unverified here.
• Local Models shows browser fallback: confirm that Desktop is running and the bridge loaded.
• No runtime is detected: start and verify the separate model runtime.
• The runtime is detected but no models appear: inspect the runtime’s installed inventory.
• Local Chat cannot generate: confirm runtime status, selected installed model, and endpoint trust.

For support, include the release version and safe runtime status without sharing credentials or private model data. Installer, system-requirement, and update details remain draft until release engineering provides an authoritative contract.

Installation diagnosis must stay tied to the actual release artifact and the later bridge and runtime checks.

No approved system-requirements matrix identifies operating systems, CPU architectures, memory, disk, or GPU support; open the approved download page and confirm that a release artifact is offered for the current device. After launch, the application must still detect a runtime and at least one installed model before Local Chat can generate; launch Ethen Desktop, then check Local Models for bridge and runtime status.