Product Roadmap

Where Cordelia and Kent are headed. A plan, not a promise. Dates and order can change as development goes.

See the Release Notes for what shipped in each release.

Release Milestones

What's next, roughly in order. No version numbers here. These are plans, not commitments yet.

  1. Windows 11 support, English first.
  2. Windows 11 support in French, Spanish, German, Italian, and Brazilian Portuguese.
  3. macOS on Apple Silicon support, English first.
  4. macOS on Apple Silicon support in French, Spanish, German, Italian, and Brazilian Portuguese.
  5. Authentication to a proxy server, laying the groundwork for Garmin Connect integration.
  6. Integration with Garmin Connect, subject to Garmin's approval.

Kent

Where Kent is headed. A plan, not a promise. Dates and order can change as development goes.

Getting Kent into your hands

Kent now has a signed Linux x64 download. See Getting Kent. Everything below is what comes next.

  1. A Windows download. Build not posted yet.
  2. macOS. No work on macOS has started; it will be a few more months.

A command that is planned but not available

One more command is designed and written, but is deliberately not connected to the command line. Typing it today gives you unknown command, exactly as an invented word would. It is listed here, and nowhere else in this help, precisely so that nothing on this site implies it works.

Planned commandWhat it would do
kent merge --in <dbfilename> <dbfilename> -out <dbfilename>Merge two databases into a third, newly created one.

It still needs its output format, argument handling and failure behaviour settled to the standard of the commands that already work. merge is also the most consequential thing on this page: it is the only planned command that would write to a database you already have.

activities, sports and verify were on this list until 2026-09-01. All three now ship, and each has its own page: activities, sports, verify.

Migrating an old database

Nothing in Kent brings an old database up to a current schema, and this is the gap most likely to be mistaken for one of the commands above. sqldump and archive will both read an old database out, and restore will put an archive back, but a restore reproduces what was there, old schema version included. Converting between schema versions means changing the data in between, by hand or by script.

Whether that is worth building is a question for the day Cordelia's schema actually changes. No database anywhere is on an old schema yet.

For the commands that do work, see createdb, info, details, files, sqldump, archive, and restore.

Not planned

Two things come up often enough to be worth ruling out explicitly:

See also