Repository navigation
Releases: anchor-inference/daedalus
Release list
desktop-v0.16.2
What's new in 0.16.2
A new desktop layout
- The sidebar splits Projects from Chats. A project is one you made with + New project, or a chat a
second chat joined; everything else is a chat, grouped by day. Rows are two-line plates with status, model
and time; a collapsed project still shows its chats that wait for you, work or failed. - All projects and + New project sit side by side under New chat; All projects is now a page with a
table instead of a dialog. Filters All / Waiting / Working, and keys:/search, arrows, F2, E, Del,
Ctrl+Shift+O for a new chat. - New project is rebuilt: a name and a folder. A new folder gets a readable name; an existing one is
picked in a real folder browser, for the container and for the host, with recent and favourite places.
The orchestration fields (goal, first task, checks) moved to New orchestrated project in orchestration
mode. - The start screen shows what is active now and Start in … project chips; the session header is two lines
with the project, the model and the live status.
Work on the host from a server install
- In Docker, a plain chat can run on the host (Run on: Container / Host), outside orchestration. Such chats
carry a Host mark; their files pane, ImageView, SendFile and the browser's uploads read the host folder.
Settings that explain themselves
- An error caused by a setting shows a Go to setting button that opens the page, scrolls to the row and
highlights it: the summary model, the vision model, a missing provider key, speech recognition, web search,
spend caps. - New setting Fall back to the session's model (on by default): when the summary or vision model is unset
or refuses (quota, balance, outage), the session's model does the work and a yellow notice says so. A manual
compaction no longer ends in Server unavailable (500).
Fixes
- A running command's card and the file viewer no longer lose their scroll and selection every second while
the agent works. - A message sent as a turn ended no longer leaves a stuck bubble, and a message with a secret shows its chip.
- A secret handed to a running Claude Code member is a real variable from its next command, a re-handed value
replaces the old one, and using it no longer triggers a stream of permission requests.
Daedalus on your own machine, as an application of its own: install it, open it from the Start
menu, Launchpad or the application menu, and it sets itself up in its own window — the mode, the
keys, the first start — and then shows the app there. Native mode needs nothing else; Docker mode
needs Docker Desktop (macOS, Windows) or Docker Engine with the compose plugin (Linux), which the
application never installs for you.
Install it
| Machine | File | Then |
|---|---|---|
| Windows 10 and 11, x86-64 | Daedalus-Setup-x64.exe |
Run it: Next, Install, Finish. It installs for you only, in %LOCALAPPDATA%\\Programs\\Daedalus, with no administrator, and puts Daedalus in the Start menu and on the desktop. The installer is not code-signed, so SmartScreen warns once: More info → Run anyway. Uninstall it from Settings → Apps; it asks whether to delete your data too, and keeps it unless you say so. |
| macOS 12 and later, Apple Silicon and Intel | Daedalus-macOS.dmg |
Open it and drag Daedalus onto Applications. The application is signed ad-hoc, not with a Developer ID, so macOS refuses the first opening ("Apple could not verify…"): open it once, then System Settings → Privacy & Security → Open Anyway; or in Terminal xattr -dr com.apple.quarantine /Applications/Daedalus.app. Only the first opening asks. |
| Debian, Ubuntu and their relatives, x86-64 | Daedalus-linux-amd64.deb |
sudo apt install ./Daedalus-linux-amd64.deb, or open it with your software centre. Daedalus appears in the application menu. sudo apt remove daedalus removes it and leaves your data. |
| Debian, Ubuntu and their relatives, ARM64 | Daedalus-linux-arm64.deb |
The same. |
| Any Linux, x86-64 | Daedalus-linux-x86_64.AppImage |
Make it executable (chmod +x, or Properties → Allow executing) and open it. |
| Any Linux, ARM64 | Daedalus-linux-arm64.AppImage |
The same. |
Your data — the conversations, the settings, the keys, the checkouts — lives in a folder of your
own that no installer or update touches: %LOCALAPPDATA%\\Daedalus\\data on Windows,
~/Library/Application Support/Daedalus/data on macOS, ~/.local/share/daedalus/data on Linux.
An installation from an earlier archive that kept data/ beside the launcher is moved there by its
first start, and daedalus-desktop import <folder> brings one in from anywhere else.
Updating
The application says when a newer release is out, in its own window and in a notification. On
Windows, on macOS and from the archives, Install and restart installs it: the data is protected
first (a kept whole copy on Linux with ext4, a checked backup elsewhere), the new version is put in
place, started and checked, and if it does not come up the data and the previous version are put
back. The .deb and the AppImage are updated by installing the new release's file the same way.
The archives
daedalus-desktop-windows-amd64.zip, Daedalus-macOS.zip and daedalus-desktop-linux-*.tar.gz
are the same applications unpacked. Every launcher from v0.10 on upgrades from them
(daedalus-desktop upgrade), and they are what the one-line installers fetch:
curl -fsSL https://raw.githubusercontent.com/anchor-inference/daedalus/main/desktop/install.sh | shirm https://raw.githubusercontent.com/anchor-inference/daedalus/main/desktop/install.ps1 | iexSHA256SUMS covers every file here, installers and archives alike, and SHA256SUMS.sig signs it
together with this release's tag, by the project's release key — minisign key id
A18524FA935353DF, key line RWTfU1OT+iSFoaxGzNfGzkwHdVs2o8WmnCzBUo/LBUw2L4ssGN4xYx/2, whose
SHA-256 (what the installers print as its fingerprint) is
f75fa5a293fdd55b36c794f4787f7af8646e4dac95e19d74e6288e55c357c285. The application, the launcher
and the one-line installers refuse a release that is not signed by it; to check an installer you
downloaded yourself, desktop/SIGNING.md shows how. desktop/README.md
has the folders, the disk the runtime takes, and every command.
desktop-v0.16.1
What's new in 0.16.1
Fixed on Windows
- Pictures work on a native Windows install. Every image write failed there (the blob store flushed
its folder in a way Windows refuses), so a screenshot pasted while the agent worked answered
Request failed (500) and the image model was never asked. Grok, Claude and Codex models marked
images now describe pictures through their subscription routes, as on Linux. - A key saved in Settings → Providers reaches the key proxy, so Add a model and the composer see
the same key state Settings shows. A key stuck in the old place is moved on the next start.
Conversations
- Text the agent writes between tool calls stays between them; on a long run it used to jump above
earlier steps. - A message queued while the agent works keeps its pictures, whether it waits for the turn or is
sent with Steer. - A steered message's card above the composer goes away once the agent has taken it.
- The microphone stays beside Send and Stop: after typing, attaching a file, and while a run is on.
- Files under an answer: the files the agent sent are cards (three, then "+N"); everything it wrote
or edited is one Changed N files line with paths relative to the project. - Secrets. "+" → Secret hands the agent a password or token by name. The agent gets a
placeholder and an environment variable, never the value; the browser, MCP calls, commands and
coding-CLI staff can use it, and any output that contains it is masked. Manage them in
Settings → Security. - In the desktop application: Open in Explorer / Show in Finder / Open in file manager for the
project's folders, the session's workspace and each changed file.
Orchestration
- A requirement added to a card a member is working on goes into its run; it no longer stops the
member and leaves the card hanging.Requireneeds only the task, the kind and the text. - A finished report on a card with no branch is accepted with
ReviewResult(op='accept'), and the
card is closed; when you say a matter is settled, the orchestrator closes the card in the same turn. - A member started on the host with the Codex CLI runs with the model asked for (newer Codex keeps its
control socket behind a link, which the terminal daemon now follows), and a failed start says why. - A member's browser can ask to open a site on the local network; the request goes to its
orchestrator, which allows it when you already did, or asks you. Cloud metadata addresses and
Daedalus's own ports stay closed.
Phone
- A new phone layout, built the way familiar phone chat apps are: a drawer for chats, projects and
settings instead of the global tab bar, a borderless top bar, sheets for the model, the "+" menu and
row actions, and phone screens of their own for the team, the board, terminals and the Inbox. - It is a size smaller than the first cut; every provider has its logo, and the model sheet's
subtitle no longer runs into the search field.
Agent's commands
uv addin a project builds the project's own.venv; it used to aim at the application's own
read-only environment and fail with Read-only file system.
Daedalus on your own machine, as an application of its own: install it, open it from the Start
menu, Launchpad or the application menu, and it sets itself up in its own window — the mode, the
keys, the first start — and then shows the app there. Native mode needs nothing else; Docker mode
needs Docker Desktop (macOS, Windows) or Docker Engine with the compose plugin (Linux), which the
application never installs for you.
Install it
| Machine | File | Then |
|---|---|---|
| Windows 10 and 11, x86-64 | Daedalus-Setup-x64.exe |
Run it: Next, Install, Finish. It installs for you only, in %LOCALAPPDATA%\\Programs\\Daedalus, with no administrator, and puts Daedalus in the Start menu and on the desktop. The installer is not code-signed, so SmartScreen warns once: More info → Run anyway. Uninstall it from Settings → Apps; it asks whether to delete your data too, and keeps it unless you say so. |
| macOS 12 and later, Apple Silicon and Intel | Daedalus-macOS.dmg |
Open it and drag Daedalus onto Applications. The application is signed ad-hoc, not with a Developer ID, so macOS refuses the first opening ("Apple could not verify…"): open it once, then System Settings → Privacy & Security → Open Anyway; or in Terminal xattr -dr com.apple.quarantine /Applications/Daedalus.app. Only the first opening asks. |
| Debian, Ubuntu and their relatives, x86-64 | Daedalus-linux-amd64.deb |
sudo apt install ./Daedalus-linux-amd64.deb, or open it with your software centre. Daedalus appears in the application menu. sudo apt remove daedalus removes it and leaves your data. |
| Debian, Ubuntu and their relatives, ARM64 | Daedalus-linux-arm64.deb |
The same. |
| Any Linux, x86-64 | Daedalus-linux-x86_64.AppImage |
Make it executable (chmod +x, or Properties → Allow executing) and open it. |
| Any Linux, ARM64 | Daedalus-linux-arm64.AppImage |
The same. |
Your data — the conversations, the settings, the keys, the checkouts — lives in a folder of your
own that no installer or update touches: %LOCALAPPDATA%\\Daedalus\\data on Windows,
~/Library/Application Support/Daedalus/data on macOS, ~/.local/share/daedalus/data on Linux.
An installation from an earlier archive that kept data/ beside the launcher is moved there by its
first start, and daedalus-desktop import <folder> brings one in from anywhere else.
Updating
The application says when a newer release is out, in its own window and in a notification. On
Windows, on macOS and from the archives, Install and restart installs it: the data is protected
first (a kept whole copy on Linux with ext4, a checked backup elsewhere), the new version is put in
place, started and checked, and if it does not come up the data and the previous version are put
back. The .deb and the AppImage are updated by installing the new release's file the same way.
The archives
daedalus-desktop-windows-amd64.zip, Daedalus-macOS.zip and daedalus-desktop-linux-*.tar.gz
are the same applications unpacked. Every launcher from v0.10 on upgrades from them
(daedalus-desktop upgrade), and they are what the one-line installers fetch:
curl -fsSL https://raw.githubusercontent.com/anchor-inference/daedalus/main/desktop/install.sh | shirm https://raw.githubusercontent.com/anchor-inference/daedalus/main/desktop/install.ps1 | iexSHA256SUMS covers every file here, installers and archives alike, and SHA256SUMS.sig signs it
together with this release's tag, by the project's release key — minisign key id
A18524FA935353DF, key line RWTfU1OT+iSFoaxGzNfGzkwHdVs2o8WmnCzBUo/LBUw2L4ssGN4xYx/2, whose
SHA-256 (what the installers print as its fingerprint) is
f75fa5a293fdd55b36c794f4787f7af8646e4dac95e19d74e6288e55c357c285. The application, the launcher
and the one-line installers refuse a release that is not signed by it; to check an installer you
downloaded yourself, desktop/SIGNING.md shows how. desktop/README.md
has the folders, the disk the runtime takes, and every command.
desktop-v0.16.0
Daedalus on your own machine, as an application of its own: install it, open it from the Start
menu, Launchpad or the application menu, and it sets itself up in its own window — the mode, the
keys, the first start — and then shows the app there. Native mode needs nothing else; Docker mode
needs Docker Desktop (macOS, Windows) or Docker Engine with the compose plugin (Linux), which the
application never installs for you.
Install it
| Machine | File | Then |
|---|---|---|
| Windows 10 and 11, x86-64 | Daedalus-Setup-x64.exe |
Run it: Next, Install, Finish. It installs for you only, in %LOCALAPPDATA%\\Programs\\Daedalus, with no administrator, and puts Daedalus in the Start menu and on the desktop. The installer is not code-signed, so SmartScreen warns once: More info → Run anyway. Uninstall it from Settings → Apps; it asks whether to delete your data too, and keeps it unless you say so. |
| macOS 12 and later, Apple Silicon and Intel | Daedalus-macOS.dmg |
Open it and drag Daedalus onto Applications. The application is signed ad-hoc, not with a Developer ID, so macOS refuses the first opening ("Apple could not verify…"): open it once, then System Settings → Privacy & Security → Open Anyway; or in Terminal xattr -dr com.apple.quarantine /Applications/Daedalus.app. Only the first opening asks. |
| Debian, Ubuntu and their relatives, x86-64 | Daedalus-linux-amd64.deb |
sudo apt install ./Daedalus-linux-amd64.deb, or open it with your software centre. Daedalus appears in the application menu. sudo apt remove daedalus removes it and leaves your data. |
| Debian, Ubuntu and their relatives, ARM64 | Daedalus-linux-arm64.deb |
The same. |
| Any Linux, x86-64 | Daedalus-linux-x86_64.AppImage |
Make it executable (chmod +x, or Properties → Allow executing) and open it. |
| Any Linux, ARM64 | Daedalus-linux-arm64.AppImage |
The same. |
Your data — the conversations, the settings, the keys, the checkouts — lives in a folder of your
own that no installer or update touches: %LOCALAPPDATA%\\Daedalus\\data on Windows,
~/Library/Application Support/Daedalus/data on macOS, ~/.local/share/daedalus/data on Linux.
An installation from an earlier archive that kept data/ beside the launcher is moved there by its
first start, and daedalus-desktop import <folder> brings one in from anywhere else.
Updating
The application says when a newer release is out, in its own window and in a notification. On
Windows, on macOS and from the archives, Install and restart installs it: the data is protected
first (a kept whole copy on Linux with ext4, a checked backup elsewhere), the new version is put in
place, started and checked, and if it does not come up the data and the previous version are put
back. The .deb and the AppImage are updated by installing the new release's file the same way.
The archives
daedalus-desktop-windows-amd64.zip, Daedalus-macOS.zip and daedalus-desktop-linux-*.tar.gz
are the same applications unpacked. Every launcher from v0.10 on upgrades from them
(daedalus-desktop upgrade), and they are what the one-line installers fetch:
curl -fsSL https://raw.githubusercontent.com/anchor-inference/daedalus/main/desktop/install.sh | shirm https://raw.githubusercontent.com/anchor-inference/daedalus/main/desktop/install.ps1 | iexSHA256SUMS covers every file here, installers and archives alike, and SHA256SUMS.sig signs it
together with this release's tag, by the project's release key — minisign key id
A18524FA935353DF, key line RWTfU1OT+iSFoaxGzNfGzkwHdVs2o8WmnCzBUo/LBUw2L4ssGN4xYx/2, whose
SHA-256 (what the installers print as its fingerprint) is
f75fa5a293fdd55b36c794f4787f7af8646e4dac95e19d74e6288e55c357c285. The application, the launcher
and the one-line installers refuse a release that is not signed by it; to check an installer you
downloaded yourself, desktop/SIGNING.md shows how. desktop/README.md
has the folders, the disk the runtime takes, and every command.
desktop-v0.15.2
Daedalus on your own machine, as an application of its own: install it, open it from the Start
menu, Launchpad or the application menu, and it sets itself up in its own window — the mode, the
keys, the first start — and then shows the app there. Native mode needs nothing else; Docker mode
needs Docker Desktop (macOS, Windows) or Docker Engine with the compose plugin (Linux), which the
application never installs for you.
Install it
| Machine | File | Then |
|---|---|---|
| Windows 10 and 11, x86-64 | Daedalus-Setup-x64.exe |
Run it: Next, Install, Finish. It installs for you only, in %LOCALAPPDATA%\\Programs\\Daedalus, with no administrator, and puts Daedalus in the Start menu and on the desktop. The installer is not code-signed, so SmartScreen warns once: More info → Run anyway. Uninstall it from Settings → Apps; it asks whether to delete your data too, and keeps it unless you say so. |
| macOS 12 and later, Apple Silicon and Intel | Daedalus-macOS.dmg |
Open it and drag Daedalus onto Applications. The application is signed ad-hoc, not with a Developer ID, so macOS refuses the first opening ("Apple could not verify…"): open it once, then System Settings → Privacy & Security → Open Anyway; or in Terminal xattr -dr com.apple.quarantine /Applications/Daedalus.app. Only the first opening asks. |
| Debian, Ubuntu and their relatives, x86-64 | Daedalus-linux-amd64.deb |
sudo apt install ./Daedalus-linux-amd64.deb, or open it with your software centre. Daedalus appears in the application menu. sudo apt remove daedalus removes it and leaves your data. |
| Debian, Ubuntu and their relatives, ARM64 | Daedalus-linux-arm64.deb |
The same. |
| Any Linux, x86-64 | Daedalus-linux-x86_64.AppImage |
Make it executable (chmod +x, or Properties → Allow executing) and open it. |
| Any Linux, ARM64 | Daedalus-linux-arm64.AppImage |
The same. |
Your data — the conversations, the settings, the keys, the checkouts — lives in a folder of your
own that no installer or update touches: %LOCALAPPDATA%\\Daedalus\\data on Windows,
~/Library/Application Support/Daedalus/data on macOS, ~/.local/share/daedalus/data on Linux.
An installation from an earlier archive that kept data/ beside the launcher is moved there by its
first start, and daedalus-desktop import <folder> brings one in from anywhere else.
Updating
The application says when a newer release is out, in its own window and in a notification. On
Windows, on macOS and from the archives, Install and restart installs it: the data is protected
first (a kept whole copy on Linux with ext4, a checked backup elsewhere), the new version is put in
place, started and checked, and if it does not come up the data and the previous version are put
back. The .deb and the AppImage are updated by installing the new release's file the same way.
The archives
daedalus-desktop-windows-amd64.zip, Daedalus-macOS.zip and daedalus-desktop-linux-*.tar.gz
are the same applications unpacked. Every launcher from v0.10 on upgrades from them
(daedalus-desktop upgrade), and they are what the one-line installers fetch:
curl -fsSL https://raw.githubusercontent.com/anchor-inference/daedalus/main/desktop/install.sh | shirm https://raw.githubusercontent.com/anchor-inference/daedalus/main/desktop/install.ps1 | iexSHA256SUMS covers every file here, installers and archives alike, and SHA256SUMS.sig signs it
together with this release's tag, by the project's release key — minisign key id
A18524FA935353DF, key line RWTfU1OT+iSFoaxGzNfGzkwHdVs2o8WmnCzBUo/LBUw2L4ssGN4xYx/2, whose
SHA-256 (what the installers print as its fingerprint) is
f75fa5a293fdd55b36c794f4787f7af8646e4dac95e19d74e6288e55c357c285. The application, the launcher
and the one-line installers refuse a release that is not signed by it; to check an installer you
downloaded yourself, desktop/SIGNING.md shows how. desktop/README.md
has the folders, the disk the runtime takes, and every command.
desktop-v0.15.1
Daedalus on your own machine, as an application of its own: install it, open it from the Start
menu, Launchpad or the application menu, and it sets itself up in its own window — the mode, the
keys, the first start — and then shows the app there. Native mode needs nothing else; Docker mode
needs Docker Desktop (macOS, Windows) or Docker Engine with the compose plugin (Linux), which the
application never installs for you.
Install it
| Machine | File | Then |
|---|---|---|
| Windows 10 and 11, x86-64 | Daedalus-Setup-x64.exe |
Run it: Next, Install, Finish. It installs for you only, in %LOCALAPPDATA%\\Programs\\Daedalus, with no administrator, and puts Daedalus in the Start menu and on the desktop. The installer is not code-signed, so SmartScreen warns once: More info → Run anyway. Uninstall it from Settings → Apps; it asks whether to delete your data too, and keeps it unless you say so. |
| macOS 12 and later, Apple Silicon and Intel | Daedalus-macOS.dmg |
Open it and drag Daedalus onto Applications. The application is signed ad-hoc, not with a Developer ID, so macOS refuses the first opening ("Apple could not verify…"): open it once, then System Settings → Privacy & Security → Open Anyway; or in Terminal xattr -dr com.apple.quarantine /Applications/Daedalus.app. Only the first opening asks. |
| Debian, Ubuntu and their relatives, x86-64 | Daedalus-linux-amd64.deb |
sudo apt install ./Daedalus-linux-amd64.deb, or open it with your software centre. Daedalus appears in the application menu. sudo apt remove daedalus removes it and leaves your data. |
| Debian, Ubuntu and their relatives, ARM64 | Daedalus-linux-arm64.deb |
The same. |
| Any Linux, x86-64 | Daedalus-linux-x86_64.AppImage |
Make it executable (chmod +x, or Properties → Allow executing) and open it. |
| Any Linux, ARM64 | Daedalus-linux-arm64.AppImage |
The same. |
Your data — the conversations, the settings, the keys, the checkouts — lives in a folder of your
own that no installer or update touches: %LOCALAPPDATA%\\Daedalus\\data on Windows,
~/Library/Application Support/Daedalus/data on macOS, ~/.local/share/daedalus/data on Linux.
An installation from an earlier archive that kept data/ beside the launcher is moved there by its
first start, and daedalus-desktop import <folder> brings one in from anywhere else.
Updating
The application says when a newer release is out, in its own window and in a notification. On
Windows, on macOS and from the archives, Install and restart installs it: the data is protected
first (a kept whole copy on Linux with ext4, a checked backup elsewhere), the new version is put in
place, started and checked, and if it does not come up the data and the previous version are put
back. The .deb and the AppImage are updated by installing the new release's file the same way.
The archives
daedalus-desktop-windows-amd64.zip, Daedalus-macOS.zip and daedalus-desktop-linux-*.tar.gz
are the same applications unpacked. Every launcher from v0.10 on upgrades from them
(daedalus-desktop upgrade), and they are what the one-line installers fetch:
curl -fsSL https://raw.githubusercontent.com/anchor-inference/daedalus/main/desktop/install.sh | shirm https://raw.githubusercontent.com/anchor-inference/daedalus/main/desktop/install.ps1 | iexSHA256SUMS covers every file here, installers and archives alike, and SHA256SUMS.sig signs it
together with this release's tag, by the project's release key — minisign key id
A18524FA935353DF, key line RWTfU1OT+iSFoaxGzNfGzkwHdVs2o8WmnCzBUo/LBUw2L4ssGN4xYx/2, whose
SHA-256 (what the installers print as its fingerprint) is
f75fa5a293fdd55b36c794f4787f7af8646e4dac95e19d74e6288e55c357c285. The application, the launcher
and the one-line installers refuse a release that is not signed by it; to check an installer you
downloaded yourself, desktop/SIGNING.md shows how. desktop/README.md
has the folders, the disk the runtime takes, and every command.
desktop-v0.15.0
Daedalus on your own machine, as an application of its own: install it, open it from the Start
menu, Launchpad or the application menu, and it sets itself up in its own window — the mode, the
keys, the first start — and then shows the app there. Native mode needs nothing else; Docker mode
needs Docker Desktop (macOS, Windows) or Docker Engine with the compose plugin (Linux), which the
application never installs for you.
Install it
| Machine | File | Then |
|---|---|---|
| Windows 10 and 11, x86-64 | Daedalus-Setup-x64.exe |
Run it: Next, Install, Finish. It installs for you only, in %LOCALAPPDATA%\\Programs\\Daedalus, with no administrator, and puts Daedalus in the Start menu and on the desktop. The installer is not code-signed, so SmartScreen warns once: More info → Run anyway. Uninstall it from Settings → Apps; it asks whether to delete your data too, and keeps it unless you say so. |
| macOS 12 and later, Apple Silicon and Intel | Daedalus-macOS.dmg |
Open it and drag Daedalus onto Applications. The application is signed ad-hoc, not with a Developer ID, so macOS refuses the first opening ("Apple could not verify…"): open it once, then System Settings → Privacy & Security → Open Anyway; or in Terminal xattr -dr com.apple.quarantine /Applications/Daedalus.app. Only the first opening asks. |
| Debian, Ubuntu and their relatives, x86-64 | Daedalus-linux-amd64.deb |
sudo apt install ./Daedalus-linux-amd64.deb, or open it with your software centre. Daedalus appears in the application menu. sudo apt remove daedalus removes it and leaves your data. |
| Debian, Ubuntu and their relatives, ARM64 | Daedalus-linux-arm64.deb |
The same. |
| Any Linux, x86-64 | Daedalus-linux-x86_64.AppImage |
Make it executable (chmod +x, or Properties → Allow executing) and open it. |
| Any Linux, ARM64 | Daedalus-linux-arm64.AppImage |
The same. |
Your data — the conversations, the settings, the keys, the checkouts — lives in a folder of your
own that no installer or update touches: %LOCALAPPDATA%\\Daedalus\\data on Windows,
~/Library/Application Support/Daedalus/data on macOS, ~/.local/share/daedalus/data on Linux.
An installation from an earlier archive that kept data/ beside the launcher is moved there by its
first start, and daedalus-desktop import <folder> brings one in from anywhere else.
Updating
The application says when a newer release is out, in its own window and in a notification. On
Windows, on macOS and from the archives, Install and restart installs it: the data is protected
first (a kept whole copy on Linux with ext4, a checked backup elsewhere), the new version is put in
place, started and checked, and if it does not come up the data and the previous version are put
back. The .deb and the AppImage are updated by installing the new release's file the same way.
The archives
daedalus-desktop-windows-amd64.zip, Daedalus-macOS.zip and daedalus-desktop-linux-*.tar.gz
are the same applications unpacked. Every launcher from v0.10 on upgrades from them
(daedalus-desktop upgrade), and they are what the one-line installers fetch:
curl -fsSL https://raw.githubusercontent.com/anchor-inference/daedalus/main/desktop/install.sh | shirm https://raw.githubusercontent.com/anchor-inference/daedalus/main/desktop/install.ps1 | iexSHA256SUMS covers every file here, installers and archives alike, and SHA256SUMS.sig signs it
together with this release's tag, by the project's release key — minisign key id
A18524FA935353DF, key line RWTfU1OT+iSFoaxGzNfGzkwHdVs2o8WmnCzBUo/LBUw2L4ssGN4xYx/2, whose
SHA-256 (what the installers print as its fingerprint) is
f75fa5a293fdd55b36c794f4787f7af8646e4dac95e19d74e6288e55c357c285. The application, the launcher
and the one-line installers refuse a release that is not signed by it; to check an installer you
downloaded yourself, desktop/SIGNING.md shows how. desktop/README.md
has the folders, the disk the runtime takes, and every command.
desktop-v0.14.0
Daedalus on your own machine, as an application of its own: install it, open it from the Start
menu, Launchpad or the application menu, and it sets itself up in its own window — the mode, the
keys, the first start — and then shows the app there. Native mode needs nothing else; Docker mode
needs Docker Desktop (macOS, Windows) or Docker Engine with the compose plugin (Linux), which the
application never installs for you.
Install it
| Machine | File | Then |
|---|---|---|
| Windows 10 and 11, x86-64 | Daedalus-Setup-x64.exe |
Run it: Next, Install, Finish. It installs for you only, in %LOCALAPPDATA%\\Programs\\Daedalus, with no administrator, and puts Daedalus in the Start menu and on the desktop. The installer is not code-signed, so SmartScreen warns once: More info → Run anyway. Uninstall it from Settings → Apps; it asks whether to delete your data too, and keeps it unless you say so. |
| macOS 12 and later, Apple Silicon and Intel | Daedalus-macOS.dmg |
Open it and drag Daedalus onto Applications. The application is signed ad-hoc, not with a Developer ID, so macOS refuses the first opening ("Apple could not verify…"): open it once, then System Settings → Privacy & Security → Open Anyway; or in Terminal xattr -dr com.apple.quarantine /Applications/Daedalus.app. Only the first opening asks. |
| Debian, Ubuntu and their relatives, x86-64 | Daedalus-linux-amd64.deb |
sudo apt install ./Daedalus-linux-amd64.deb, or open it with your software centre. Daedalus appears in the application menu. sudo apt remove daedalus removes it and leaves your data. |
| Debian, Ubuntu and their relatives, ARM64 | Daedalus-linux-arm64.deb |
The same. |
| Any Linux, x86-64 | Daedalus-linux-x86_64.AppImage |
Make it executable (chmod +x, or Properties → Allow executing) and open it. |
| Any Linux, ARM64 | Daedalus-linux-arm64.AppImage |
The same. |
Your data — the conversations, the settings, the keys, the checkouts — lives in a folder of your
own that no installer or update touches: %LOCALAPPDATA%\\Daedalus\\data on Windows,
~/Library/Application Support/Daedalus/data on macOS, ~/.local/share/daedalus/data on Linux.
An installation from an earlier archive that kept data/ beside the launcher is moved there by its
first start, and daedalus-desktop import <folder> brings one in from anywhere else.
Updating
The application says when a newer release is out, in its own window and in a notification. On
Windows, on macOS and from the archives, Install and restart installs it: the data is protected
first (a kept whole copy on Linux with ext4, a checked backup elsewhere), the new version is put in
place, started and checked, and if it does not come up the data and the previous version are put
back. The .deb and the AppImage are updated by installing the new release's file the same way.
The archives
daedalus-desktop-windows-amd64.zip, Daedalus-macOS.zip and daedalus-desktop-linux-*.tar.gz
are the same applications unpacked. Every launcher from v0.10 on upgrades from them
(daedalus-desktop upgrade), and they are what the one-line installers fetch:
curl -fsSL https://raw.githubusercontent.com/anchor-inference/daedalus/main/desktop/install.sh | shirm https://raw.githubusercontent.com/anchor-inference/daedalus/main/desktop/install.ps1 | iexSHA256SUMS covers every file here, installers and archives alike, and SHA256SUMS.sig signs it
together with this release's tag, by the project's release key — minisign key id
A18524FA935353DF, key line RWTfU1OT+iSFoaxGzNfGzkwHdVs2o8WmnCzBUo/LBUw2L4ssGN4xYx/2, whose
SHA-256 (what the installers print as its fingerprint) is
f75fa5a293fdd55b36c794f4787f7af8646e4dac95e19d74e6288e55c357c285. The application, the launcher
and the one-line installers refuse a release that is not signed by it; to check an installer you
downloaded yourself, desktop/SIGNING.md shows how. desktop/README.md
has the folders, the disk the runtime takes, and every command.
desktop-v0.13.0
Daedalus on your own machine: one folder, Docker, and this launcher. It clones the two
repositories, asks for the keys on a page of its own, starts the stack and opens the app —
on macOS and Windows in a window of its own, on Linux in a browser window with nothing
around it. Docker Desktop (macOS, Windows) or Docker Engine with the compose plugin
(Linux) has to be installed and running — the launcher never installs it for you.
Install it in one line — macOS and Linux
curl -fsSL https://raw.githubusercontent.com/anchor-inference/daedalus/main/desktop/install.sh | shIt picks the right archive, checks it against the checksums below, and unpacks it into
./Daedalus.
Or download it
| Machine | File | Then |
|---|---|---|
| macOS (Apple Silicon and Intel) | Daedalus-macOS.zip |
Unzip it into a folder of its own. Double-click Daedalus in the folder. This build is signed ad-hoc rather than with a Developer ID certificate, so macOS refuses a copy that came through a browser ("Apple could not verify…"), and since macOS 15 a right-click Open no longer gets past it. Open it once, then System Settings → Privacy & Security → Open Anyway; or in Terminal run xattr -dr com.apple.quarantine Daedalus.app in the folder. Only the first launch asks. A copy installed with the one-liner below never asks at all. |
| Linux x86-64 | daedalus-desktop-linux-amd64.tar.gz |
tar -xzf it into an empty folder and run ./daedalus-desktop. |
| Linux ARM64 | daedalus-desktop-linux-arm64.tar.gz |
tar -xzf it into an empty folder and run ./daedalus-desktop. |
| Windows x86-64 | daedalus-desktop-windows-amd64.zip |
Expand-Archive daedalus-desktop-windows-amd64.zip -DestinationPath Daedalus in PowerShell, then run daedalus-desktop.exe. The executable is unsigned, so SmartScreen warns once: More info → Run anyway. The window needs the WebView2 runtime, which Windows 11 and any machine with a current Edge already has; without it the launcher opens a browser instead. |
The launcher makes the checkouts, the keys and the database inside the folder you put it in,
and natively keeps its downloaded runtime and local state outside it;
daedalus-desktop uninstall removes those, and deleting the folder then removes the rest.
SHA256SUMS covers every archive here, and SHA256SUMS.sig signs it together with this
release's tag, by the project's release key — minisign key id A18524FA935353DF, key line
RWTfU1OT+iSFoaxGzNfGzkwHdVs2o8WmnCzBUo/LBUw2L4ssGN4xYx/2, whose SHA-256 (what the
installers print as its fingerprint) is
f75fa5a293fdd55b36c794f4787f7af8646e4dac95e19d74e6288e55c357c285. The launcher and the
installers refuse a release that is not signed by it; desktop/SIGNING.md shows how to check
the signature by hand. desktop/README.md has the folder layout, the disk the images take, and every command.
desktop-v0.12.0
Daedalus on your own machine: one folder, Docker, and this launcher. It clones the two
repositories, asks for the keys on a page of its own, starts the stack and opens the app —
on macOS and Windows in a window of its own, on Linux in a browser window with nothing
around it. Docker Desktop (macOS, Windows) or Docker Engine with the compose plugin
(Linux) has to be installed and running — the launcher never installs it for you.
Install it in one line — macOS and Linux
curl -fsSL https://raw.githubusercontent.com/anchor-inference/daedalus/main/desktop/install.sh | shIt picks the right archive, checks it against the checksums below, and unpacks it into
./Daedalus.
Or download it
| Machine | File | Then |
|---|---|---|
| macOS (Apple Silicon and Intel) | Daedalus-macOS.zip |
Unzip it into a folder of its own. Double-click Daedalus in the folder. This build is signed ad-hoc rather than with a Developer ID certificate, so the first time you open a copy that came through a browser, macOS asks: right-click the app, choose Open, then Open again. Only the first launch asks. A copy installed with the one-liner below never asks at all. |
| Linux x86-64 | daedalus-desktop-linux-amd64.tar.gz |
tar -xzf it into an empty folder and run ./daedalus-desktop. |
| Linux ARM64 | daedalus-desktop-linux-arm64.tar.gz |
tar -xzf it into an empty folder and run ./daedalus-desktop. |
| Windows x86-64 | daedalus-desktop-windows-amd64.zip |
Expand-Archive daedalus-desktop-windows-amd64.zip -DestinationPath Daedalus in PowerShell, then run daedalus-desktop.exe. The executable is unsigned, so SmartScreen warns once: More info → Run anyway. The window needs the WebView2 runtime, which Windows 11 and any machine with a current Edge already has; without it the launcher opens a browser instead. |
The launcher makes everything else — the checkouts, the keys, the database — inside the folder
you put it in, so deleting that folder deletes the installation.
SHA256SUMS covers every archive here. desktop/README.md has the folder layout, the disk the images take, and every command.
desktop-v0.11.0
Daedalus on your own machine: one folder, Docker, and this launcher. It clones the two
repositories, asks for the keys on a page of its own, starts the stack and opens the app —
on macOS and Windows in a window of its own, on Linux in a browser window with nothing
around it. Docker Desktop (macOS, Windows) or Docker Engine with the compose plugin
(Linux) has to be installed and running — the launcher never installs it for you.
Install it in one line — macOS and Linux
curl -fsSL https://raw.githubusercontent.com/anchor-inference/daedalus/main/desktop/install.sh | shIt picks the right archive, checks it against the checksums below, and unpacks it into
./Daedalus.
Or download it
| Machine | File | Then |
|---|---|---|
| macOS (Apple Silicon and Intel) | Daedalus-macOS.zip |
Unzip it into a folder of its own. Double-click Daedalus in the folder. This build is signed ad-hoc rather than with a Developer ID certificate, so the first time you open a copy that came through a browser, macOS asks: right-click the app, choose Open, then Open again. Only the first launch asks. A copy installed with the one-liner below never asks at all. |
| Linux x86-64 | daedalus-desktop-linux-amd64.tar.gz |
tar -xzf it into an empty folder and run ./daedalus-desktop. |
| Linux ARM64 | daedalus-desktop-linux-arm64.tar.gz |
tar -xzf it into an empty folder and run ./daedalus-desktop. |
| Windows x86-64 | daedalus-desktop-windows-amd64.zip |
Expand-Archive daedalus-desktop-windows-amd64.zip -DestinationPath Daedalus in PowerShell, then run daedalus-desktop.exe. The executable is unsigned, so SmartScreen warns once: More info → Run anyway. The window needs the WebView2 runtime, which Windows 11 and any machine with a current Edge already has; without it the launcher opens a browser instead. |
The launcher makes everything else — the checkouts, the keys, the database — inside the folder
you put it in, so deleting that folder deletes the installation.
SHA256SUMS covers every archive here. desktop/README.md has the folder layout, the disk the images take, and every command.