Skip to content

Releases

Audience. New user and Daily user.

condash is shipped as a pre-built desktop binary on GitHub Releases. This page is about finding the right version — one link above all else: releases/latest.

Version scheme

Tags follow vMAJOR.MINOR.PATCH:

Segment Bumps when… Example
PATCH Bug fix, docs update, non-behaviour change v1.0.17 → v1.0.18
MINOR New feature or user-visible behaviour change v1.0.X → v1.1.0
MAJOR Breaking change — config or Markdown format v1.X.X → v2.0.0

Patches are the norm. Most weeks there's at least one; MINOR bumps are rarer, MAJOR is a special event.

Major versions

condash's history spans three implementations and four major lines. Only the Electron line (2.x–4.x) is current; 0.x (Python) and 1.x (Rust/Tauri) are frozen in separate repos.

Major What it was
0.x Python (NiceGUI + FastAPI). Frozen at vcoeur/condash-python.
1.x Rust + Tauri rewrite. Frozen at vcoeur/condash-tauri.
2.x–4.x Electron rewrite — the current canonical build.

Migrating from condash 3.x → 4.x

v4.0.0 narrowed what condash does with agent config. Earlier 3.x builds compiled per-agent instruction files for you; 4.0.0 removed that pipeline entirely. If you used any of the following, it is gone:

  • The .agents/agents/ source tree (common.md / condash.md / conception.md / claude.md / kimi.md) — no longer read.
  • The root opencode.json pointer condash used to write — no longer written.
  • condash project build — removed.
  • condash skills install --user — removed (condash no longer writes ~/.claude/skills/ or ~/.kimi/skills/).

What condash skills install does now is just two things: ship your .agents/skills/<name>/ sources verbatim, and maintain condash's marker region inside AGENTS.md. Rendering AGENTS.md into per-agent views (.claude/CLAUDE.md, .kimi/AGENTS.md, …) is now the job of your harness launcher, not condash — those files are produced at launch and are never written to disk by condash. If you have leftover .agents/agents/ or a condash-written opencode.json, they are simply inert; delete them at your convenience.

Agent launchers also changed shape in this line: they are now a flat { id, label, command } list under the agents config key, edited in the Settings modal — see Agent CLIs and model providers.

Finding the latest

Three paths:

  • The latest-release shortcut. https://github.com/vcoeur/condash/releases/latest always redirects to the current top published release. If you don't care about the version number, start there.
  • The all-releases list. https://github.com/vcoeur/condash/releases shows the chronological list. Scroll to see changelogs per release.
  • The dashboard footer. Running condash shows the version in the footer of the main window. Click it to open the release page for that exact version.

Release notes

Each release carries:

  • A short summary in the release body — one or two bullets on what changed.
  • The full commit list between this tag and the previous, auto-generated by GitHub.
  • The per-OS artifacts attached.

Draft releases

If the latest-release URL 404s or shows a release older than you expect, the newest build is probably still in draft state. Draft releases are:

  • Visible to the maintainer only.
  • Usually published within a few hours of the draft appearing.
  • Caused by the release workflow leaving the GitHub Release in draft mode by default, so the maintainer can add notes before publishing.

If you're waiting on a specific fix, the GitHub Actions tab shows the build progress; the release appears under All releases the moment the maintainer flips the draft to published.

Upgrading

condash does not auto-update. Install and upgrade are out-of-band — apt on Linux, dpkg or the .deb directly, or make install from source. The electron-updater wiring is shipped as a no-op so the dependency stays tracked; the packaged build does not check the GitHub Releases feed on launch.

To track releases, subscribe to the repo's Releases tab on GitHub — you'll get an email when a new version ships.