Before you begin
- A supported artifact listed on /download
- Permission to install software on the device
- Either a compatible direct-provider credential or an Orchestris server account
Install and open Chat
Open /download and choose Orchestris Chat. Use the artifact row for your device as the source for the current filename, architecture, minimum operating system, SHA-256 value, and signature information.
| Desktop target | Release package | Architecture |
|---|---|---|
| Windows 10/11 | Setup installer (.exe) | x64 |
| macOS 11 or later | Installer package (.pkg) | Apple Silicon (arm64) |
| Debian/Ubuntu | Debian package (.deb) | x64/amd64 |
| Fedora, RHEL, Rocky Linux, AlmaLinux, openSUSE, or SUSE Linux Enterprise | RPM package (.rpm) | x64/x86_64 |
- Desktop target
- Windows 10/11
- Release package
- Setup installer (.exe)
- Architecture
- x64
- Desktop target
- macOS 11 or later
- Release package
- Installer package (.pkg)
- Architecture
- Apple Silicon (arm64)
- Desktop target
- Debian/Ubuntu
- Release package
- Debian package (.deb)
- Architecture
- x64/amd64
- Desktop target
- Fedora, RHEL, Rocky Linux, AlmaLinux, openSUSE, or SUSE Linux Enterprise
- Release package
- RPM package (.rpm)
- Architecture
- x64/x86_64
- 1
Download and verify the matching artifact
Check the minimum operating system, compare the complete SHA-256 value, and on Linux verify the detached signature when the release supplies one.
- 2
Windows: run Setup
Open the downloaded EXE, confirm that Windows shows the verified Orchestris publisher, keep or review the install options, and choose Launch Orchestris Chat when setup finishes. The Start Menu shortcut opens it later.
- 3
macOS: install and open the application
Double-click the signed PKG, follow the graphical Installer, then open Orchestris Chat from Applications.
- 4
Linux: install and launch the desktop application
Use the package manager command matching the downloaded DEB or RPM, then launch Orchestris Chat from the desktop application menu or with orchestris-chat.
- 5
Confirm the first launch
The Chat window should open without an installer error. Confirm that Settings → API Providers and Servers are available, then choose one of the connection paths below.
The download page shows the exact current filename and a copyable install command for each Linux package. The wildcard templates below are useful when following this guide from a folder containing only the package you intend to install.
sudo apt install ./orchestris-chat_*.deb
orchestris-chatsudo dnf install ./orchestris-chat-*.rpm
orchestris-chatsudo zypper --no-gpg-checks install ./orchestris-chat-*.rpm
orchestris-chatChoose a direct provider or a server
| Connection | You need | Behavior |
|---|---|---|
| Direct provider | A compatible endpoint and a credential accepted by that provider. | Chat calls the provider from the device. Provider configuration and conversations remain local to that Chat profile. |
| Orchestris server | The server's HTTP(S) origin, an active account, and a password. | The server authenticates the account, returns its organizations, and exposes only the models allowed for the selected organization and user. |
| Hosted Chat | A browser and an account on the hosting server. | Open the server's /app/ URL. The hosted client is already bound to that server and does not show Add Server. |
- Connection
- Direct provider
- You need
- A compatible endpoint and a credential accepted by that provider.
- Behavior
- Chat calls the provider from the device. Provider configuration and conversations remain local to that Chat profile.
- Connection
- Orchestris server
- You need
- The server's HTTP(S) origin, an active account, and a password.
- Behavior
- The server authenticates the account, returns its organizations, and exposes only the models allowed for the selected organization and user.
- Connection
- Hosted Chat
- You need
- A browser and an account on the hosting server.
- Behavior
- Open the server's /app/ URL. The hosted client is already bound to that server and does not show Add Server.
Connect Chat directly to a provider
- 1
Open API Providers
In Chat, open Settings → API Providers and choose the action to add a provider.
- 2
Enter the provider connection
Use the endpoint and credential issued by that provider. Save the credential only in your own device profile; Chat stores it through the platform's protected credential storage.
- 3
Choose a discovered model
Open the model picker and select a model returned by the provider. If no model appears, recheck the endpoint, credential, and provider availability.
- 4
Send a small test prompt
Start a new conversation and confirm that a response streams successfully before adding projects, files, or important local-only history.
Connect desktop Chat to an Orchestris server
- 1
Confirm the server first
Open the server's /health endpoint in a browser or with curl. Obtain the exact public server origin and account credentials from the administrator.
- 2
Open Servers
In desktop Chat, choose Servers from the main navigation. If this is the first connection, the empty state also offers Add Server.
- 3
Choose Add Server
Use the plus button or Add Server action. Under Connect to, choose Orchestris Cloud for the built-in managed origin or Custom server for Community Edition and Private Deployment.
- 4
Enter the custom origin
For a custom server, enter an origin including the scheme, for example https://ai.example.com or http://localhost:8080. Do not append /app/, /v1, or another API path.
- 5
Authenticate
Enter the account email and password, then choose Connect. Chat verifies the server-issued token before trusting organization information.
- 6
Verify models
Open the model picker. Organization administrators can see the organization catalog; members see models and aliases granted through their groups.
Update or remove Chat
- Before updating, read the release notes and verify the new artifact on /download. Use the platform's normal installer upgrade path.
- Do not delete the Chat application-data directory as an upgrade step. It contains the local conversation database, direct-provider settings, and device state.
- Removing a server from Chat removes that device's connection and local server-derived state. It does not delete the server, organization, or server-side account.
- Uninstalling Chat and deleting its application data are separate actions. Back up or export any local-only information you need before removing application data.