---
title: "RemotiveCLI release notes"
description: "Release notes for RemotiveCLI, with the new features, bug fixes and breaking changes in each version of the remotive command-line tool."
source: https://developer.remotivelabs.com/docs/reference/release-notes/remotive-cli
last_updated: 2026-11-19
---

# RemotiveCLI release notes

## 0.48.0 - 2026-11-17

> **Danger: Breaking changes**
>
> - **broker:** The commands remotive broker record, remotive broker playback, remotive broker files, remotive broker export and remotive connect are removed.
> - **broker:** The command remotive broker scripting is removed.

### Bug fixes

- **schemas:** Keep the CLI's schemas available when Studio's schemas.json is unreadable

  A malformed `studio_ui/schemas.json` made `remotive schemas list` and
  every `show` fail, also for the workspace and launcher schemas, which
  don't come from Studio. It now leaves only the dashboard version
  unknown, with the parse error as the reason, so `show dashboard
  --version 0.3` and the CLI's own schemas still work.

  `Schema.no_version` defaults to None instead of "", and a schema with
  no version must give one, so an unknown version never ends in an empty
  error message.
- **studio:** Check broker health with the HealthCheck RPC

  /runtime/health fetched the broker version through GetConfiguration on
  every poll, but no client reads it. GetConfiguration walks the signal
  tree and serialises the interfaces JSON, so use the empty HealthCheck
  RPC instead and drop broker_version from the response. The version is
  still reported by /runtime/environment.

  The mock broker gains HealthCheck so Studio stays healthy against it.

### Features

- **broker:** Remove broker record, playback, files, export and connect
  - **BREAKING**: The commands remotive broker record, remotive broker playback, remotive broker files, remotive broker export and remotive connect are removed.

  remotive broker record, remotive broker playback, remotive broker files,
  remotive broker export and remotive connect are removed, together with
  the code only they used: the ProtoPie bridge, the recording session
  client and the Broker methods for recording, uploading, deleting files
  and reloading the configuration.

  Playing recordings in RemotiveCloud with remotive cloud recordings
  playback is unchanged.
- **broker:** Remove broker scripting
  - **BREAKING**: The command remotive broker scripting is removed.

  remotive broker scripting, which generated a template Lua script for
  scripted signals, is removed.
- **cloud:** Deprecate remotive cloud and every command under it

  remotive cloud is deprecated, and so is every command under it: help
  marks each one as deprecated. Running one prints a single warning for
  remotive cloud; a command that was already deprecated on its own, such
  as remotive cloud organizations default, still prints its own pointer.
- **schemas:** List the workspace and launcher schemas

  `remotive schemas` listed only the dashboard schema. The CLI publishes
  two schemas of its own, for the workspace marker (`remotive.yaml`) and
  for a cloud launcher (`*.launcher.yaml`), and now lists and shows both.

  Their versions come from the URL the CLI holds for each:
  `WORKSPACE_SCHEMA_URL`, which `workspace init` writes, and a new
  `LAUNCHER_SCHEMA_URL`. They need no RemotiveStudio. The launcher
  schema's release now rewrites `LAUNCHER_SCHEMA_URL` on a bump, as the
  workspace schema's release does for its URL, and a CLI release checks
  that every schema URL it carries has been released, not only the
  workspace one. The tests read the versions from those URLs, so a schema
  release needs no test change.

## 0.47.0 - 2026-11-13

### Bug fixes

- **docs:** Show quotes in man pages

  The quotes were html-encoded which would look like
  "&amp;quot;" both in the man pages and the markdown pages
  for the web.

### Features

- **search:** Read signal databases of version 0.6

  `remotive topology analyze` reads the `.signaldb.yaml` the broker and
  remotive-topology write today, and runs remotive-topology 0.40, the
  first release that writes 0.6.

  - The models are regenerated with `remotive-topology pydantic remotivedb`.
  - A signal database of another version is refused; an older one names
    `remotive-topology convert &lt;file> -o &lt;file>`, since its start bits,
    start values and group lengths mean other things in 0.6.
  - SecOC and E2E are rebuilt from the index by their profile `type`, and a
    signal and a group keep their update bit.
  - The physical channel names and `opt_empty_payload`, gone from 0.6, are
    gone from the index.

### Refactor

- **topology:** Fix the topology runtime in the build, not in the environment

  `remotive topology` ran the container image unless REMOTIVE_TOPOLOGY_RUNTIME=rust
  asked for the bundled Rust remotive-topology. A variable left in a shell then decided
  what a build ran, whichever build it was.

  The runtime is now `RUNTIME` in `topology/runtime.py`, the container, and
  REMOTIVE_TOPOLOGY_RUNTIME is no longer read. REMOTIVE_TOPOLOGY_COMMAND still runs a
  given remotive-topology binary instead. The tests set the runtime they are about
  instead of relying on which one the build names.

  This is what lets the `topology-rust` branch, which runs the Rust runtime, differ from
  main in that one line and the RemotiveStudio version (DEV.md), so that it rebases onto
  main without conflicts.

## 0.46.0 - 2026-11-12

### Features
- **studio:**

  - Search suggestions are ranked across every matching value, not only the
    first 64 of each field, and shown in that order. Scroll, or press the down
    arrow, near the end of the list to load the next 20.
  - Typing an ECU name suggests the ECU before the frames and signals whose
    names start with it.
  - Search options open over the results instead of pushing them down, so the
    results can still be scrolled in a short window. They close on Escape, on a
    click outside, and when you insert a field, which then offers that field's
    values. This applies in the Signals view, the Restbus view and the
    dashboard's signal picker.
  - The Signals view showing favorites says under the table how many frames
    match the search but are hidden for not being favorites.

## 0.45.7 - 2026-11-12

### Bug fixes

- **studio:** Read a signal database on podman when the topology CLI logs a warning

  With podman, Studio could not read a signal database whenever the topology
  CLI logged a warning while converting it, for example about a NO_PROXY entry
  with a /12 mask, an attribute outside its value range in a DBC, or a signal
  placed in no frame in an LDF. Studio showed only "reindex failed: 500".

  The CLI ran podman with a terminal attached even when Studio read the
  output, and podman then merged the container's log lines into the JSON.
  A podman run now gets a terminal only when you run the command yourself
  from one, as with docker. When the output still isn't JSON, the error
  says where it stopped parsing.

### Features

- **cli:** Take one bare version in requires-version

  requires-version also takes one bare version, such as 0.47.0.
- **schemas:** Add `remotive schemas list` and `show`

  RemotiveLabs publishes the JSON schemas of the files its products read
  on files.remotivelabs.com, one URL per version. These commands tell
  which version applies and fetch it, so editors and validation scripts
  can find the schema of, for example, a *.dashboard.json file.

  `list` shows each schema with the version the bundled RemotiveStudio
  writes and its URL, in plain columns so the URL is never cut to fit the
  terminal; `--json` gives the same as JSON. `show NAME` prints the
  published schema, and `--version` picks another version.

  The version comes from the schemas.json that RemotiveStudio 1.36.1 and
  later ship beside the app, and every released CLI bundles Studio. A
  source checkout without it, or with an older Studio, knows no version,
  and the commands say to install RemotiveStudio 1.36.1 or later with
  ./install_studio.sh.
- **settings:** Share config, token and state files safely between CLI versions

  Several RemotiveCLI versions installed side by side read and write the same
  files, so a CLI must not lose or break what another version wrote.

  - Keep keys this CLI does not know when saving config, token and state files
  - Never write a file whose format version has a newer major; say so once
  - Fail a sign-in whose token or account cannot be saved because of that,
    before a key is made or the one it replaces is revoked
  - Leave token files with a newer or unreadable version alone instead of
    failing every command on them
  - Run without a state file in a newer format that cannot be read, and name
    the config file when it is the one
  - Read timestamps with or without a timezone, and treat an unreadable one as
    never; keep writing local time, which released versions require
  - Re-read the config and state file before changing it, so a change made by
    another running CLI is kept
  - Give each install its own completion cache, so two installs stop rewriting
    one shared file

  docs/SHARED_FILES.md says how the format of these files may change: only add
  optional fields, and put a breaking change in a new file.

## 0.45.6 - 2026-11-10

### Features

- **topology:** Pass --instances-dir to the Rust build in a workspace

## 0.45.5 - 2026-11-10

## 0.45.4 - 2026-11-10

## 0.45.3 - 2026-11-10

## 0.45.2 - 2026-11-04

### Features

- **studio:** Capture in Wireshark from an ECU or a SOME/IP message

  - Capture every bus an ECU is on in one window, filtered to the frames it
    sends. A frame with several senders shows under each of them.
  - Capture a SOME/IP message on all of its provider sockets, UDP and TCP,
    with the ports bound to the SOME/IP dissector.
  - The capture buttons are in the entity detail panel and the dashboard
    filter menu, and follow the active filter.

### Bug fixes

- **studio:**

  - A reopened file that fails its check now shows the error and a retry
    instead of the stored copy, so problems such as a file the converter now
    rejects are no longer hidden.

## 0.45.1 - 2026-11-04

## 0.45.0 - 2026-11-03

### Features

- **studio:**

  - The Overview page leads with Getting started, Guides and the installed
    versions, which link to their release notes. Integrate with, RemotiveLabs
    resources and Legal start collapsed below.
  - Updated to support the latest topology schema so all signal databases can
    be viewed.
  - A calmer look for errors, warnings and status: one layout where only the
    icon and border carry the colour, plainer connection-lost and crash
    screens, and a blue status chip when the topology is not running.

### Bug fixes

- **studio:**

  - A topology error shows its cause with its own error code, and each code
    links to its documentation.
  - Live timeseries charts no longer lurch forward and back when panels
    subscribe to frames that reach the broker by different paths.
  - Right-click the ID header in the Restbus table to sort or show IDs in
    decimal, hex or both, as in the Signals view.
  - Dragging a column header in the Signals view no longer scrolls the frame
    list.
  - Frames without a cycle time sort as 0 instead of apart from the numbers.
  - Inline code in markdown panels renders as a chip without the literal
    backticks.
  - Long URLs wrap inside the status tooltip.

## 0.44.1 - 2026-10-30

### Bug fixes

- **dist:** The macOS release job failed in 0.44.0

## 0.44.0 - 2026-10-30

### Features

- **auth:** Authentication moves to `remotive auth`

  Sign in with `remotive auth login`; see `remotive auth --help` for the rest.
  The old `remotive cloud auth` commands keep working.
- **dist:** `man remotive` and `remotive --manual`

  The deb, rpm, Homebrew, macOS and install.sh installs now include a man page
  with the full command reference. `remotive --manual` prints the same
  reference regardless of installation.

## 0.43.1 - 2026-10-28

- **topology:** The default RemotiveTopology image is now 0.39.

## 0.43.0 - 2026-10-27

### Features

- **studio:**

  - Better Ethernet and SOME/IP support in search, the signal tables, the
    topology panels and the dashboards.
  - Choose the Signals view's columns from a Columns menu: a Suggested
    layout picked for what the file holds, the CAN, LIN, SOME/IP, Ethernet
    PDUs and Compact layouts, or layouts of your own saved per workspace.
    Right-click a header to sort or hide, drag it to move the column, and
    widen columns as far as you like.
  - ID columns show decimal, hex or both. Right-click the column's header to
    choose. Trace panels and frame information follow the same setting.
  - Every ID is searchable in decimal or hex: frame and PDU IDs with
    `id:`, and SOME/IP IDs with `service_id:`, `method_id:`, `event_id:`
    and `event_group_id:`. `id:0x18FF0010` and `id:419364880` find the
    same frame.
  - Search suggestions take the rest of the query into account: with
    `channel:eth1 service:` typed, only eth1's services are offered,
    not every service in the file.
  - In the dashboards, an Ethernet PDU can be listened on any of its
    connections' views and taps, several at once to compare them. The
    broker signal picker lists frames as the Signals view does, with the
    database channel's name and ID, Type, Size and Service columns. The
    dashboard filter plots the cycle times of the PDUs an ECU sends on
    Ethernet.
  - Frame information and signal information show how the frame or signal
    is exposed on a broker: the namespaces it can be subscribed to or
    published on, each with a copy button, and the name the broker uses for
    it.

### Bug fixes

- **studio:**

  - The playback bar keeps updating after its status stream drops, reopens the
    stream when the broker ends it, and shows a reconnecting notice instead of
    disappearing. Channel activity reconnects after a network error, and one
    dashboard's reconnect no longer clears another's playbacks.
  - A trace listening on several namespaces that see the same message, such as
    the taps at both ends of an Ethernet connection, shows every view's copy. A
    long frame ID stays inside its column.
  - Cycle time charts always auto-scale, so longer cycle times are no longer
    hidden.

## 0.42.1 - 2026-10-26

## 0.42.0 - 2026-10-23

### Features

- **setup:** Ask setup's questions the way the service-account wizard does

  `remotive setup` now asks with the same pick-from-a-list and y/n prompts as
  `remotive cloud service-accounts create --it`, instead of typed choices and
  numbered tables.

  - What is already in place is shown and kept with a Yes ("Signed in as ...
    Use this account?", "Default organization: ... Keep it?"). A No lists the
    alternatives: your other saved accounts or a sign-in in the browser, and
    all your organizations with the current one marked. `--only-missing`
    keeps everything without asking.
  - When you are not signed in, or the sign-in has expired, your other saved
    accounts are offered before the browser.
  - When both docker and podman work, you pick one from a list with their
    versions. An installed engine that does not work is reported on the
    engine step, and its error is quoted in an "Errors" section at the end.
  - The first RemotiveTopology image download shows the engine's progress,
    and Ctrl-C stops it cleanly.
  - Setup needs a terminal.
- **topology:** A workspace can require a RemotiveCLI version

  `remotive.yaml` can set `requires-version` to the RemotiveCLI versions the
  workspace works with, written as in Python packaging, e.g.
  ">=0.40,&lt;1.0".
- **doctor:** `remotive doctor` reports a Docker Compose plugin older than
  2.33 as outdated and links to the upgrade instructions. Podman is not
  affected.

### Documentation

- Links in help text, messages and documentation now go to
  developer.remotivelabs.com, where the documentation has moved. Old
  docs.remotivelabs.com links still redirect there, and links to pages that
  have moved open their replacements.
- The command reference on developer.remotivelabs.com is now titled
  "RemotiveCLI command reference" and describes what it covers in search
  results.

## 0.41.0 - 2026-10-16

### Features

- **auth:** Create a service account and its access token step by step

  `remotive cloud service-accounts create --it` guides you through creating a
  service account and downloading an access token for it, so you no longer
  need to look up project IDs and role names first. It picks the project from
  the ones you administer in your default organization (or one you choose),
  asks for a name, lets you tick the roles from a list, creates the account
  and saves the access token file, telling you where it is and offering to
  print the token. You can also use it to create a new access token for an
  existing service account. Pass `--project` or set `REMOTIVE_CLOUD_PROJECT`
  to skip the project question.

  - Need a project first? When your organization lets you create projects, the
    project list ends with "Create a new project". If there is no project you
    administer, it lists the projects you are a member of and your role in
    each, so you know which administrator to ask.
  - Stopping part-way, with Ctrl-C or on an error, is safe: it tells you what
    has been created so far. If an access token was issued but could not be
    saved, it tells you how to find and revoke it.
  - The guided flow needs a terminal. In scripts, keep using
    `service-accounts create`, `service-accounts tokens create` and
    `projects create`, which work as before.
  - The help of `service-accounts create` and `update` now lists the available
    roles and what each allows.
  - The outdated sample script for creating a service account with a secret is
    removed; use the guided flow or the commands above instead.

## 0.40.0 - 2026-10-14

> **Danger: Breaking changes**
>
> - **tools:** `remotive tools can convert` and `remotive tools can validate` are
>   removed, together with the `remotive tools` group.

### Features

- **setup:** New `remotive setup` wizard to get started with the RemotiveLabs
  tool chain

  It walks you through sign-in, choosing a default
  organization, a RemotiveTopology subscription (starts a 30-day trial if none exists), the
  CLI version, container engine, RemotiveBus (Linux), the RemotiveTopology
  image and RemotiveStudio Desktop. Each step checks what is already in place
  and offers to fix what is missing; every step is optional. Use
  `remotive upgrade` to install components.

  - The container engine can be saved as the default with
    `remotive topology config set container-engine`.
  - The install script recommends `remotive setup` after a first install.
- **studio:**

  - Search signals with a text query instead of filter chips. Queries support
    quoted phrases, `?`/`*` wildcards, `field:=value` for exact matches,
    `field:(a OR b)` groups and `+` for required terms. Suggestions only offer
    fields the open file can match. Hover over `?` in the search bar for the
    full syntax and the fields you can search.
  - The dashboard's signal pickers find SOME/IP and Ethernet frames, e.g.
    `service:=SpeedService` or `channel:=NET2`, and show a SOME/IP frame's
    method or event ID.
  - Drag to reorder and remove frames and signals in trace and restbus panels,
    and drag to reorder timeseries charts.
  - Sort grouped trace frames by column, and select a frame's signals from its
    signal table header.
  - Find in the YAML view, and export the topology graph as PNG or SVG.
  - Errors when loading a file name the failing signal database and link to
    the files involved.
- **cli:**

  - `remotive build` gives stable output that doesn't change between builds.
  - E092 reports every conflict between a channel's signal databases, and
    lists the databases involved.
  - A DBC platform's CAN channel gets its bus speed and CAN FD bit rate from
    the DBC.

### Performance

- **studio:** Faster file opening and a more responsive Studio

  - A file is resolved and converted once per version and cached, so
    reopening it, also after restarting Studio, is close to instant. A file
    already opened in the shows at once and refreshes in the
    background if it changed.
  - The running topology instance is prepared when Studio starts, so the
    first open is fast.
  - Search is faster
  - Responses are compressed, which helps when Studio runs on another machine.
  - Studio loads faster: a much smaller initial download, a lighter file
    viewer, and the broker's frame list decoded off the main thread.

### Bug fixes

- **auth:** `remotive cloud auth login` shows a clear message when the account
  is disabled, instead of an unexpected error.
- **studio:**

  - A channel on the macvlan, ipvlan or external Ethernet driver shows its
    driver instead of "Unknown driver type".
  - Signal table values stay under their headers when a column is resized.
    Tooltips no longer swallow clicks or get stuck after switching view.
  - Paused playback moves the slider thumb when the position changes.

## 0.39.0 - 2026-10-05

### Features

- **upgrade:** Include RemotiveStudio Desktop

  `remotive upgrade` now also upgrades RemotiveStudio Desktop and keeps it on
  the channel it was installed from (Homebrew, DMG, apt, dnf or tarball). A
  missing desktop app is listed as a hint and can be installed with
  `--install-studio-desktop`. Components without a build for your platform are
  shown as "not supported on this platform", and a release that cannot be
  checked no longer fails the whole command.
- **upgrade:** Add --install-all

  `remotive upgrade --install-all` also installs every missing component that
  has a build for this host: RemotiveBus on Linux and RemotiveStudio Desktop.

## 0.38.2 - 2026-10-04

### Bug fixes

- **install:** Refuse an explicit --method that does not fit the host OS

  `apt`, `yum` and `tar` are now Linux-only and `brew` and `pkg` macOS-only, and
  a mismatch is rejected before anything is changed.
- **upgrade:** Make a missing RemotiveBus a hint, add --install-remotivebus

  A host without RemotiveBus is no longer reported as outdated on every run.
  Install it with `remotive upgrade --install-remotivebus` (Linux only).

## 0.38.1 - 2026-10-02

### Bug fixes

- **studio:**

  - Launch the desktop app without analytics consent or authorization

    `remotive studio --desktop` without a workspace path only opens the app, so
    it no longer asks for analytics consent or authorization first.
  - Fix "workspace not found" when launching with a path while the desktop app
    is already running

## 0.38.0 - 2026-10-02

> **Danger: Breaking changes**
>
> - **broker:** `remotive broker discover` is removed. Scripts that call it need
>   to be updated.

## 0.37.0 - 2026-10-02

### Bug fixes

- **settings:** Fix update checks that stopped running after a day
- Use the correct URL for downloads

### Features

- **cli:** Add remotive upgrade

  `remotive upgrade` checks the installed CLI and, on Linux, RemotiveBus against
  the latest releases and, after confirmation, upgrades them in place on the
  channel the CLI was installed from. pip, pipx and uv installs get a hint to
  upgrade with their own tool instead. `--check` only reports and `--dry-run`
  shows what would happen.

## 0.36.1 - 2026-10-01

No user-facing changes.

## 0.36.0 - 2026-10-01

> **Danger: Breaking changes**
>
> - The `remotive mcp-server` command is removed.

### Bug fixes

- **install:** Keep package signature checks on for the RemotiveLabs yum
  repository, and keep an existing repo file unless `-f` is passed
- Security updates to bundled third-party packages

### Features

- **studio:** Show the `remotive studio <path>` command to use when the running
  topology belongs to another workspace

## 0.35.1 - 2026-09-28

### Bug fixes

- Support signal database format 0.4

## 0.35.0 - 2026-09-28

### Bug fixes

- `remotive doctor` resolves kernel modules the same way RemotiveBus does
- Support empty frames in LDF files
- Run ARXML LIN schedule slots with the delay given in the file
- Do not generate a namespace with the 'ANY' remote host
- Name the default gateway mapping file after its format

### Features

- **cli:** Index LIN integrity groups
- **topology:** Add `analyze busload` for the base CAN bus load per channel

  `remotive topology analyze busload -f <platform-or-instance.yaml>` computes the
  cyclic (base) bus load of every CAN channel: each frame with a cycle time is
  assumed to be sent continuously, and its on-wire size is derived from the CAN
  2.0 / CAN FD frame format, with and without worst-case bit stuffing.
- LIN schedule tables in Remotive SignalDB
- AUTOSAR E2E profiles 2 and 5 and the profile 1 data id mode in Remotive SignalDB
- Add the FlexRay channel type to Remotive SignalDB

## 0.34.1 - 2026-09-15

No user-facing changes.

## 0.34.0 - 2026-09-15

### Features

- **distribution:** Recommend RemotiveBus from the deb/rpm packages

  A plain apt or dnf install of the CLI now also installs the RemotiveBus
  daemon.

## 0.33.0 - 2026-09-14

### Bug fixes

- **studio:**

  - Report a clear error when a signal database declares an unreadable schema
    version
  - Include the schema version in signal database documents assembled from the
    index

### Features

- **studio:**

  - Index an Ethernet channel's PDUs
  - Index and assemble a SOME/IP service's messages

### Performance

- **studio:** Faster signal indexing

## 0.32.0 - 2026-09-14

No user-facing changes.

## 0.31.1 - 2026-09-10

### Bug fixes

- **cli:** Honor --force when launching the RemotiveStudio desktop app

  `remotive studio --desktop --force <path>` silently dropped `--force`, so a
  path nested inside another workspace failed with "workspace already exists".
  The workspace path is now resolved before the app launches, with the same
  rules as browser mode.
- **studio:** The macOS update hint no longer suggests `brew upgrade --cask` for
  apps that were installed from the DMG

### Features

- **studio:** Show the running broker version

## 0.31.0 - 2026-09-10

### Features

- **studio:** Add workspace file search

  Search files in the workspace by name, with case-insensitive substring
  matching, file-type filters and hidden-file control. The index is cached and
  rebuilt in the background.

## 0.30.1 - 2026-09-09

No user-facing changes.

## 0.30.0 - 2026-09-08

No user-facing changes.

## 0.29.1 - 2026-09-01

No user-facing changes.

## 0.29.0 - 2026-09-01

No user-facing changes.

## 0.28.1 - 2026-09-01

No user-facing changes.

## 0.28.0 - 2026-08-31

### Bug fixes

- **cli:** Much smaller packages

  The compressed package size drops from about 470 MB to about 60 MB.

### Features

- **cli:** Support the NO_PROXY environment variable

  `NO_PROXY` and `no_proxy` are forwarded to remotive-topology.

## 0.27.2 - 2026-08-28

### Bug fixes

- **studio:**

  - Raise the studio server keep-alive timeout to 120 seconds
  - Handle concurrent signal database index requests without indexing twice
  - Show the topology container's own error instead of a generic "Topology
    command failed"

### Performance

- **studio:** Much faster indexing of large signal databases

## 0.27.1 - 2026-08-27

### Bug fixes

- **studio:** Skip files that cannot be read, such as dangling symlinks, in
  directory listings instead of failing the whole listing

## 0.27.0 - 2026-08-21

### Features

- **doctor:** Add `remotive doctor` host prerequisite checks

  Verifies RemotiveBus (installation, service, CAN kernel modules, plugin
  socket), container engines (docker or podman including compose, one working
  engine is enough), RemotiveCloud authentication (credentials, whoami
  round-trip, default organization) and optional Wireshark capture tooling.
  One actionable hint per failing component; informational checks never fail
  the run. Exit code 0 or 1.

## 0.26.4 - 2026-08-20

No user-facing changes.

## 0.26.3 - 2026-08-19

No user-facing changes.

## 0.26.2 - 2026-08-17

### Bug fixes

- Let the desktop client handle Wireshark profiles

## 0.26.1 - 2026-08-12

No user-facing changes.

## 0.26.0 - 2026-08-10

### Features

- **studio:** Add --advertised-broker-url for clients behind a tunnel

  The new option (defaulting to `--broker-url`) is the broker URL that Studio
  clients use, for example when they reach the broker through an SSH tunnel on
  a remapped local port. The backend keeps using `--broker-url`.

## 0.25.0 - 2026-08-05

### Bug fixes

- **settings:** Ignore relative paths in `REMOTIVE_*_DIR` and `XDG_*_HOME`

  Values that are not absolute paths are ignored with a warning, per the XDG
  spec, instead of being resolved against the current directory.

### Features

- **studio:** RemotiveStudio Desktop installation and start is available to all
  users

## 0.24.0 - 2026-08-05

### Bug fixes

- Security updates to bundled third-party packages

### Features

- **studio:** Make --desktop a launcher

  `--desktop` now only launches RemotiveStudio Desktop. Installs and upgrades
  are handled by the install script, whose prompts (such as Homebrew or DMG on
  macOS) and progress show in the terminal. Desktop options are labeled Beta.
- Launch Wireshark locally
- Wireshark capture profiles

  Generates a throwaway Wireshark profile with coloring rules, frame-name and
  sender columns and a CAN id to sending ECU mapping for legible captures, and
  reports startup failures. Generated profiles are cleaned up on exit.
- Studio disables Wireshark capture when the host cannot run it

## 0.23.5 - 2026-07-22

### Bug fixes

- **install:** Uninstall script for tar packages

### Features

- **dist:** RPM packages are signed with a RemotiveLabs key

  Released `.rpm` packages can be verified by dnf with `gpgcheck=1`, on both
  dnf4 (RHEL, Rocky, Alma) and dnf5 (Fedora).

## 0.23.4 - 2026-07-19

### Features

- **dist:** Distribute the CLI on macOS via Homebrew and a .pkg installer

  Both are self-contained and bundle their own Python, and both are Apple
  Silicon (arm64) only:
  - Homebrew: `brew install remotivelabs/tap/remotivelabs-cli`
  - A signed and notarized `.pkg` installer (no Homebrew required), with an
    uninstaller available on the PATH as `remotive-uninstall`

  A cross-platform install script, `install.sh`, installs or upgrades through
  the native channel per platform and falls back to the self-contained bundle:

  macOS -> Homebrew tap (fallback: signed .pkg installer)
  Debian/Ubuntu -> apt repo (fallback: glibc tar bundle)
  RHEL/Fedora -> dnf/yum repo (fallback: glibc tar bundle)

  On macOS with Homebrew present it asks whether to use Homebrew or the `.pkg`,
  also when run as `curl ... | bash`.

## 0.23.3 - 2026-07-13

### Bug fixes

- Security update of a bundled third-party package

## 0.23.2 - 2026-07-13

No user-facing changes.

## 0.23.1 - 2026-07-07

### Bug fixes

- Document the org/studioRunner role in `service-accounts --help`

## 0.23.0 - 2026-07-02

### Bug fixes

- Security updates to bundled third-party packages

### Features

- **auth:** Mandatory default organization selection

  Login and activate now require selecting a default organization, and the
  related auth commands are restructured around it:
  - prompt for and persist a default organization on login and activate,
    auto-selecting only when exactly one organization is available
  - set the organization for service accounts automatically, from the token
  - split 'auth organization' into print and set subcommands; the deprecated
    'organizations default' still works
  - drop the --account and --organization column toggles from 'auth list'
  - login and activate no longer fail when organization selection fails

## 0.22.0 - 2026-06-24

No user-facing changes.

## 0.21.0 - 2026-06-24

No user-facing changes.

## 0.20.4 - 2026-06-22

### Bug fixes

- Fix tab completion, which silently returned no suggestions on some installs

## 0.20.3 - 2026-06-22

No user-facing changes.

## 0.20.2 - 2026-06-18

### Features

- Service accounts can read organization info and features

  A service account can be activated, set a default organization and get the
  subscription status in the same way as a personal user.

## 0.20.1 - 2026-06-17

### Bug fixes

- Improve error messages when the instance file is missing

### Features

- Bundle RemotiveStudio 1.20.0

## 0.20.0 - 2026-06-17

### Bug fixes

- **studio:** Verify the macOS desktop app's signature and notarization before
  installing it

## 0.19.0 - 2026-06-16

### Bug fixes

- Signal database indexing no longer blocks the studio server

### Features

- **topology:** Add host-gateway mapping for docker runs
- **trace:** Add --trace troubleshooting mode

  `--trace` logs the operations the CLI performs, with secrets redacted, for
  troubleshooting.

## 0.18.0 - 2026-06-12

> **Danger: Breaking changes**
>
> - The completion cache moves from the legacy location to
>   `$XDG_CACHE_HOME/remotive/`. Users with shell completions installed may need
>   to regenerate them on first run.

### Features

- **topology:** Use the schema's `$id` URL in workspace markers

  The workspace marker (`remotive.yaml`) now references its schema through a
  `schema` key carrying the canonical versioned URL, replacing the
  `remotive-topology-workspace:0.1` identifier. Generated markers start with a
  yaml-language-server modeline so editors validate and complete them out of
  the box, and no longer include an empty `description` by default.
- XDG directories and topology workspace commands

  The CLI honors the XDG Base Directory Specification for all its state.
  Configuration, cache, state and data files now live under `$XDG_CONFIG_HOME`,
  `$XDG_CACHE_HOME`, `$XDG_STATE_HOME` and `$XDG_DATA_HOME` (each under
  `remotive/`), and each kind can be overridden with `REMOTIVE_CONFIG_DIR`,
  `REMOTIVE_CACHE_DIR`, `REMOTIVE_STATE_DIR` and `REMOTIVE_DATA_DIR`. Existing
  files at the legacy location are copied forward on first run.

  New workspace commands create and inspect a `remotive.yaml`-marked project
  root. Legacy workspaces that only have the `.remotive/` directory get the
  marker added on first use:

      remotive topology workspace init
      remotive topology workspace current

  New topology lifecycle commands:

      remotive topology build [--no-workspace]
      remotive topology clean
      remotive topology prune [--all]

  `build` writes outputs under `.remotive/build/` in the workspace by default;
  pass an output path (inside the workspace, unless `--no-workspace` is set) to
  override. `prune --all` clears every workspace's topology cache, reclaiming
  space from moved or renamed workspaces. Supported on WSL2, macOS and Linux.

## 0.17.2 - 2026-06-08

### Features

- **studio:** Safer desktop app installs
  - `--desktop-version` is validated, and a malformed remotely-resolved
    "latest" version is rejected.
  - Installs are interactive only: without a terminal nothing is downloaded or
    installed. An existing install launches as-is and a missing install is an
    error. `--desktop-force-install` is removed.
  - Every install action is recorded in an audit log in the install state
    directory.

## 0.17.1 - 2026-06-08

### Bug fixes

- Prevent browsers from caching stale Studio UI files

### Features

- Studio can show whether the broker and topology are up

## 0.16.1 - 2026-06-03

### Bug fixes

- Improved checks to determine whether a graphical environment is available on
  Linux
- Allow up to 3 attempts at entering the PKCE code, to allow for copy-paste
  issues
- Validate the PKCE verification code and show the server's response on error
  instead of guessing
- Trust `XDG_SESSION_TYPE=x11` or `wayland` as a graphical session, skipping
  the display probe
- Always show the hint about `--no-browser`, even when a browser window seems
  to have opened

## 0.16.0 - 2026-06-01

### Bug fixes

- **cli:** Use the workspace cache directory when running a custom topology
  command through the CLI

### Features

- Add the `--with-metrics` flag (requires support in remotive-topology)

## 0.15.1 - 2026-05-22

### Bug fixes

- **studio:** Fix desktop embedded mode when the app is launched directly
  instead of through the CLI

  On macOS, an app launched from Spotlight fell back to browser mode and opened
  a browser window.

## 0.15.0 - 2026-05-21

### Features

- **studio:**

  - Install RemotiveStudio Desktop on demand and launch it with --desktop

    `remotive studio --desktop` installs the RemotiveStudio Desktop app if it is
    missing and launches it, forwarding the workspace path and `--broker-url`.
    - Supported on Linux (x86_64, arm64) and macOS (arm64). WSL2 is treated as
      Linux; native Windows is not supported.
    - Downloads are signature-verified on Linux.
    - Installs are atomic: a failed download leaves an existing install
      untouched.
    - On Linux, a desktop entry, icon and a `remotive-studio-desktop` command in
      `~/.local/bin` are created, without overwriting a file you put there
      yourself.
  - The desktop launcher is a preview feature

    `--desktop` is available when `REMOTIVE_STUDIO_DESKTOP_ENABLED` is set to a
    truthy value ("true", "1", "yes", "on").
- **tls:** Local HTTPS for localhost servers

  The CLI generates a local certificate authority and server certificate under
  `~/.config/remotive/certs/` on first use. They serve any localhost HTTPS
  server the CLI runs, such as the local broker on `https://localhost:50443`
  and Studio in desktop mode, and the CA is trusted by the CLI's own
  connections. `REQUESTS_CA_BUNDLE` and `GRPC_DEFAULT_SSL_ROOTS_FILE_PATH`
  keep working.

## 0.14.1 - 2026-05-21

### Bug fixes

- **search:** Silence spurious parser warnings printed on startup
- **studio:**

  - Fix a deadlock in the studio server when a topology command ran while a
    broker call was in flight
  - Studio no longer exposes internal error details in responses, and a hung
    topology command times out after 120 seconds (600 for docker pull)

## 0.14.0 - 2026-05-18

### Bug fixes

- Remove the old `remotive tui` command

### Features

- **search:** Lucene query syntax in the TUI

  `name:foo OR -unit:degC`, regex `/RPM\d+/`, ranges and parentheses. Searching
  for numbers such as cycle time works, and senders and receivers get
  suggestions.
- **tui:** Rebuild the broker explorer

  `remotive broker --ui` is reshaped on top of the signal browse and live
  values view:
  - New capabilities: restbus publish and plan modals, an in-app help screen, a
    command palette, and Lucene-syntax search.
  - One search bar drives all navigation; marks let you pick signals across
    multiple queries and feed them into the live view, restbus modal or
    publish modal.
  - Sidebar, tree, detail and live view share a single broker connection, so
    reconnects and subscriptions are handled centrally.

## 0.12.0 - 2026-05-15

### Bug fixes

- Read instance files from both locations the topology CLI may write them to

### Features

- Bundle the latest RemotiveTopology, topology schema and RemotiveStudio

## 0.11.4 - 2026-05-08

### Bug fixes

- **topology:** Keep the topology build cache inside the workspace when running
  in a container, so builds are no longer cold on every run
- Users with a skewed clock are no longer locked out of feature authorization

## 0.11.3 - 2026-05-04

### Bug fixes

- Open Studio in the browser the same way as login, on all platforms
- Relabel podman bind mounts for SELinux hosts

  Without it, the topology container could not access the mounted config and
  workspace directories on SELinux-enforcing systems.

## 0.11.2 - 2026-05-04

### Bug fixes

- Studio accepts more video, image and text file types
- Fix mount and interactive mode when running topology with podman

## 0.11.1 - 2026-05-04

### Bug fixes

- Pass all environment variables starting with `REMOTIVE_` to the container
  running topology

## 0.11.0 - 2026-04-30

### Features

- Use remotive-topology 0.23.0

## 0.10.18 - 2026-04-30

### Bug fixes

- New RemotiveStudio with a warning when hardware acceleration is not enabled,
  which charts require

### Features

- **broker:** Add --ui flag for the signal explorer
  - `remotive broker --ui` launches the interactive TUI explorer
  - `REMOTIVE_MOCK_DB` enables mock mode for offline demos
  - The `broker explore` subcommand is dropped
- **tui:** Show frame payload size and validate the payload length when
  publishing
- **tui:** Mark and unmark signals and frames
  - Mark individual signals, frames or entire namespaces with `m`, clear all
    marks with `M`. Press `m` on the root to toggle all namespaces at once.
  - Marked items are shown with a bold asterisk in the tree. Marking a frame
    also marks all its signals.
  - Marks feed into subscribe and publish actions.
- **tui:** Publish signals and frames
  - Publish a single signal or frame, or a batch of marked items, with `p`
  - Hex payload publish for frames, with size validation
- **tui:** Frame state subscription windows
  - Subscribe to marked signals and frames, or all signals in a frame
  - Expandable signal history with adjustable depth (`+` and `-` keys)
  - Click a signal line to expand it
- **tui:** Sidebar, unified live view, clickable filter fields and debounced search
  - Collapsible left sidebar (`Ctrl+B`)
  - A unified live view in the right pane that switches between a
    single-signal chart and a multi-signal frame-state view; `q` closes it
  - Detail-panel fields are clickable: left-click adds an include filter,
    right-click opens a modal with include, exclude and, for numeric fields,
    comparison operators and an OR toggle
  - Values containing whitespace or punctuation can be searched by wrapping
    them in double quotes
  - Search is debounced and runs in the background so typing stays responsive
    on large indexes; expanded frames are preserved when the tree is rebuilt

## 0.10.17 - 2026-04-27

### Bug fixes

- Fix recurring errors in the studio backend when reindexing a topology

### Features

- Add a simple health check to the studio backend

## 0.10.16 - 2026-04-21

### Features

- Faster CLI startup: subcommands are loaded only when used
- Near-instant tab completion

  Completions are served from a cached command tree at
  `~/.cache/remotivelabs/cli/completion_cache.json`, which is rebuilt
  automatically after an install or upgrade. bash, zsh and fish are supported,
  and zsh and fish show descriptions.

## 0.10.15 - 2026-04-17

### Bug fixes

- The topology search API returns all results when the query is empty

## 0.10.13 - 2026-04-14

### Bug fixes

- Fix the Studio trace raw data field showing the entire value

## 0.10.12 - 2026-04-14

### Features

- Bundle RemotiveStudio 1.16.12 with many improvements and bug fixes

## 0.10.11 - 2026-04-08

### Bug fixes

- Use `show instance` instead of `show platform` to get the current instance
- Do not force the user to be signed in to use Studio

### Features

- Open the browser by default when starting Studio
  - Validates that the user is signed in with an activated account and a
    default organization

## 0.10.10 - 2026-04-07

### Bug fixes

- Improved messages during sign-in

### Features

- Load the current runtime `instance.yaml` file

  This lets Studio show what is currently running.

## 0.10.9 - 2026-04-02

### Bug fixes

- Show an informative message and a hint on file read and write errors
- Bundle RemotiveStudio 1.16.11 with fixes to signal indexing

## 0.10.7 - 2026-04-01

### Features

- Bundle RemotiveStudio 1.16.10

## 0.10.6 - 2026-03-26

### Bug fixes

- Improved readability of named values and column resizing in Studio

## 0.10.5 - 2026-03-25

### Bug fixes

- Align signal database fields with RemotiveDB
- `mode=status` now takes filters and the query into account when returning
  the document count
- Status returns the same row count as search

### Features

- Beta 1 of Studio with signal database search
- The CLI is also distributed as a self-contained tar archive bundled with
  Python
- First version of Studio with a signal database viewer

## 0.10.2 - 2026-03-20

### Bug fixes

- RemotiveStudio 1.16.3: the frame distribution view shows the frame name and
  id as hex, and only one frame distribution panel can be added

## 0.10.1 - 2026-03-18

### Bug fixes

- Move `signals explore` from `topology` to `broker`

### Features

- **broker:** Add the `signals publish` command
  - Publish one or more signals to the broker in a single call
  - Supports scalar and comma-separated multi-value inputs; signals of
    different lengths are zipped to the longest
- **broker:** Add the `restbus` subcommand

  `add`, `start`, `stop`, `update`, `remove` and `reset` drive periodic frame
  transmission on a broker.
- Bundle RemotiveStudio 1.16.2

## 0.10.0 - 2026-03-17

### Bug fixes

- Container registry support via options
  - Removed the default docker.io for podman
  - Added `--container-registry`

## 0.9.4 - 2026-03-16

### Bug fixes

- Removed `frame_name` and `frame_description`
- Renamed `bus_type` to `channel_type`

### Features

- OpenAPI documentation for the Studio API
- Bundle RemotiveStudio 1.16.1

## 0.9.3 - 2026-03-16

### Bug fixes

- Fix a crash caused by a missing import

## 0.9.2 - 2026-03-16

### Bug fixes

- Path traversal protection for the YAML file indexing endpoints

### Features

- Index and search frames and signals from `remotive topology convert`
- List, search, see details of and subscribe to signals interactively
- Use remotive-topology 0.21

## 0.9.1 - 2026-03-09

### Bug fixes

- Convert all channels

## 0.9.0 - 2026-03-06

### Features

- RemotiveStudio is available without a feature toggle

## 0.8.5 - 2026-03-05

### Bug fixes

- XML files are assumed to be Fibex signal databases
- Fix the spinner failing with "Only one live display may be active at once"

### Features

- Allow an automatically assigned port with `--port auto`

  This makes it simple to run multiple workspaces at the same time, for example
  from the VS Code extension.

## 0.8.4 - 2026-03-02

### Features

- Use the fixed port 57123 and check whether Studio or another process is
  already running before starting

## 0.8.3 - 2026-02-27

### Bug fixes

- Add the missing `REMOTIVE_TOPOLOGY_WORKING_DIRECTORY` in docker
- Show a "Checking for updates..." spinner when a pull takes 2 seconds or more
  - A pull is only done every 30 minutes, since even an empty pull may take a
    few seconds

### Features

- Bundle RemotiveStudio alpha 9

## 0.8.1 - 2026-02-26

### Features

- Studio shows the CLI, topology and broker versions
- Bundle RemotiveStudio alpha 8, the first release with Studio bundled

## 0.7.4 - 2026-02-04

### Features

- Support for uploading a file

  An existing file is overwritten.
- Always warn when running as root, and show the config directory path after
  signing in
- Add `remotive topology subscription status` and `start-trial`
  - `status` shows all information about the current subscription, account
    and organization

## 0.7.2 - 2026-01-28

### Bug fixes

- ProtoPie connect no longer crashes when `--api-key` is not provided and
  https is not used

## 0.6.3 - 2026-01-21

### Bug fixes

- Do not try to open a web browser on Linux, since it fails on WSL

## 0.6.2 - 2026-01-21

### Bug fixes

- Removed a docker-only check that prevented podman from working when docker
  was not installed
  - Fixed the mount path and working directory on Windows
  - Containers run with `--rm`, so no dangling containers are left
- A more generic upgrade message, excluding pipx and docker installs

### Features

- Response pages look more professional and are easier to read

## 0.6.1 - 2026-01-20

### Bug fixes

- Properly handle the callback when the user did not accept the terms

## 0.5.0 - 2026-01-05

### Bug fixes

- apt and yum packages now properly support install, upgrade, remove and purge
  (deb)
- Always include the device id in API calls when available
- Avoid caching HTTP headers
- No longer migrates the old `.remotive` config automatically

## 0.5.0-a4 - 2025-12-17

### Features

- Initialize a RemotiveTopology workspace

## 0.5.0-a3 - 2025-12-15

No user-facing changes.

## 0.5.0-a2 - 2025-12-12

### Bug fixes

- Use correct POSIX error codes

### Features

- deb and rpm packages for amd64 and arm64

## 0.4.3 - 2025-12-09

### Bug fixes

- Exit the playback status stream with exit code 0
- The topology command is not supported in docker
- Print a hint instead of an error when a web browser cannot be opened, which
  happens at least on WSL

### Features

- Set the topology workspace to the current directory when running topology
  commands

## 0.5.0a1 - 2025-12-02

### Features

- Support for specifying docker or podman when running topology commands

## 0.5.0a0 - 2025-12-02

### Features

- Support for invoking remotive-topology commands from the CLI

## 0.4.2 - 2025-12-01

No user-facing changes.

## 0.4.1 - 2025-12-01

### Bug fixes

- Fix broken dependencies

## 0.4.0 - 2025-11-20

> **Danger: Breaking changes**
>
> - Playback v2 replaces the old playback commands.

### Features

- Support both stream and one-off when getting the playback status
- Playback support

  Python 3.9 is no longer supported, and Python 3.14 is validated.
- Playback v2 release, dropping the old playback

## 0.3.6b1 - 2025-10-15

### Features

- Support for topology playback `open`, `play`, `pause`, `seek`, `repeat`,
  `list-files` and `close` (feature toggled)

## 0.3.5 - 2025-09-24

### Bug fixes

- Default broker URL was missing for the frame-distribution command
- Align the access token environment variable name with topology-cli

## 0.3.4 - 2025-08-28

### Features

- Improved topology `start-trial` to make it easier to understand what is
  happening

  A confirmation makes clear that the trial is for an organization.

## 0.3.3 - 2025-08-21

### Bug fixes

- Fix a regression in suggesting activation when existing accounts exist

## 0.3.2 - 2025-08-20

### Bug fixes

- Use soft wrap to avoid inserting newlines in output

## 0.3.1 - 2025-08-14

### Bug fixes

- Fix subscribe, which stopped working after a protobuf library update

## 0.2.3 - 2025-08-01

### Features

- Add platform info to the user agent and version

## 0.2.2 - 2025-07-31

### Features

- Check for a new version on PyPI and print an upgrade hint

## 0.2.1 - 2025-07-30

No user-facing changes.

## 0.2.0 - 2025-07-29

### Bug fixes

- Print migration status to stderr instead of stdout

  Prevents issues when printing JSON that should be processed further.

### Features

- Return broker info as JSON after mount

  This makes scripting simpler, since the broker info is available regardless
  of whether a personal or a specific broker was mounted.
- Topology `start-trial` from the CLI

## 0.1.1 - 2025-06-25

### Bug fixes

- Prompt the user for a default organization after login

## 0.1.0 - 2025-06-24

> **Danger: Breaking changes**
>
> - Login and activate now use personal tokens. Older CLI versions stop working
>   and get a 426 response from the cloud to force an update. `logout` and
>   `tokens create` are removed.

### Bug fixes

- Removed `remotive config`
- Do not prompt for an organization when the user specified which token to
  activate
- Only look for known file prefixes when loading tokens
- Prompt for organizations when using a service account
- Validate that token files contain valid JSON when listing, and filter out
  failing ones
- Improved login flow to either choose activate or login again
  - Also handles the callback from the cloud when the user does not exist
- Renamed organisation to organizations
- Never prompt for an organization when using a service account
- Fix URLs printed to the terminal not working when spanning more than one line
- Two personal tokens were created when the browser could not be opened and
  the code fallback was used

### Features

- Login and activate use personal tokens automatically; no short-lived tokens
  are used
  - `config.yaml` contains each available account, the current active one and
    the default organization for each account
- Support for the `REMOTIVE_CLOUD_ACCESS_TOKEN` environment variable

  Also an improved error message on 401.

## 0.0.42 - 2025-04-28

### Bug fixes

- Fix a bug when listing organisations

## 0.0.41 - 2025-04-02

### Bug fixes

- Play only enabled recording files when using the mount and playback commands

## 0.0.40 - 2025-01-03

### Features

- Show help when no argument is given

## 0.0.39 - 2024-12-20

### Features

- `--url` defaults to `http://localhost:50051`

## 0.0.38 - 2024-12-12

### Features

- Option to subscribe to changed values only for ProtoPie

## 0.0.37 - 2024-12-11

### Bug fixes

- Fix a None type error when neither `--script` nor `--signal` is given

### Features

- Simple text-based frame distribution output

## 0.0.36 - 2024-12-10

### Features

- Show signal database metadata for a specified file

## 0.0.35 - 2024-12-09

### Bug fixes

- Add a maximum supported Python version
- Proper error message when a local file does not exist
- The short-lived token file was stored as a personal file and could not be
  overwritten

## 0.0.34 - 2024-12-05

### Features

- Removed the maximum supported Python version

## 0.0.33 - 2024-12-04

### Features

- More metadata in `signals list`, and simple prefix and suffix filtering on
  signal names

## 0.0.32 - 2024-10-31

### Bug fixes

- Fix a bug in signal database upload where an object was not expected

### Features

- Add a custom URI type for CLI arguments

## 0.0.31 - 2024-10-01

### Features

- Choose whether to overwrite on storage uploads, with upload progress

## 0.0.30 - 2024-09-26

### Bug fixes

- Filter out non-running or failed uploads

### Features

- Support for the new import-as-recording feature in cloud storage

## 0.0.29 - 2024-09-19

### Bug fixes

- Fix saving a token when the config directory is missing

## 0.0.28 - 2024-09-13

### Bug fixes

- Updated for new changes in the storage API

## 0.0.27 - 2024-08-14

### Bug fixes

- Force `--directory` to be a directory
- `cloud auth tokens describe` takes the file as an argument instead of `--file`
- `revoke` takes a name or file as an argument instead of an option
- Add help text for the signal database commands
- `create` and `delete` project take the project as an argument instead of an
  option
- Add a separate organisations group with a `list` command
- Make from/to project clearer, and drop the project environment variable since
  it was not obvious
- Rename the download and delete broker config commands to make them clearer

### Features

- Add senders, receivers and cycle time to frames in `signals list`

## 0.0.26 - 2024-07-26

No user-facing changes.

## 0.0.25 - 2024-07-08

### Features

- Support for `ls`, `cp` and `rm` against RemotiveCloud storage

## 0.0.24 - 2024-06-14

### Bug fixes

- Removed accidental output on stdout

## 0.0.23 - 2024-06-14

### Bug fixes

- Properly read the ProtoPie config file given with `--config`

## 0.0.21 - 2024-05-22

### Bug fixes

- Fix a Windows permission issue on playback

## 0.0.20 - 2024-05-15

### Bug fixes

- Fix a subscribe issue with ProtoPie connect

## 0.0.19 - 2024-04-24

### Bug fixes

- Signal database upload failed for files in another directory

## 0.0.18 - 2024-04-24

### Bug fixes

- Improve the Lua scripting sample

## 0.0.17 - 2024-04-08

### Features

- Support for licensing a broker with the CLI
- Support for subscribing to signals from a recording without knowing the URL

## 0.0.16 - 2024-04-04

### Bug fixes

- Fix export to influx line protocol, broken after the subscription API changes

## 0.0.15 - 2024-03-25

### Bug fixes

- Properly check the `--show-progress` option on play

### Features

- Keep repeating a recording with `--repeat`

## 0.0.14 - 2024-03-22

### Features

- Move the recording playback commands to the `recording playback` subcommand

## 0.0.13 - 2024-03-21

### Features

- Show the playback status of a recording being played

## 0.0.12 - 2024-03-18

### Bug fixes

- Add the default value "None" for the ProtoPie connect path

### Features

- Add the missing support for uploading a signal database to a project

## 0.0.11 - 2024-03-13

### Bug fixes

- Remove unintended listen and print on messages

## 0.0.10 - 2024-03-12

### Features

- Support for timer frequency when generating a Lua script

## 0.0.9 - 2024-03-12

### Features

- The ProtoPie bridge works with `--signal ns:signal_name` and not only
  `--config`

  Simple expressions to modify signal names are also supported.

## 0.0.8 - 2024-02-28

### Bug fixes

- Consistently use the `REMOTIVE_CLOUD_RECORDING_SESSION` environment variable
- Clean up the progress indicators for recordings to make them easier to
  understand
- Fix a regression that broke the login callback

### Features

- `subscribe` and `new-script` take long signal names that include the
  namespace

  `--namespace` is removed and replaced by `--signal ns:signal`.

## 0.0.7 - 2024-02-21

### Features

- Better progress when uploading recordings

## 0.0.6 - 2024-02-21

### Bug fixes

- Fix a bug that required a namespace and signal even though `--script` was
  used

## 0.0.5 - 2024-02-16

### Bug fixes

- Fix the download recording file bug
- Create the `.remotivelabs` directory if it does not exist
- Removed output that made jq fail
- Properly fixed upload and reload-configuration
- Add protocol and port to the result when listing brokers
- Remove the empty file that remained after a failed download
- Fix wrong instructions when activating a token
- Rename `timestamp_nanos` to `timestamp_us`, with improved error handling
- Check both None and empty string for the API key
- Skip plotting non-numeric values
- Verify that the file to upload exists and that the upload succeeded
- Validate file arguments and options
- Subscribing to multiple namespaces now works as expected, and requested
  signals are validated against the broker
- Fix a bug where an extra line prevented keys from being created properly
- Fix starting a personal broker, and check that the recording exists on mount
- Removed python-can and the tools module for now
- Properly check the error message for all playback commands
- Read the auth token from disk for ProtoPie
- Describe the ProtoPie config option, with improved terminal messages
- Fix `pkg_resources` not working on Python 3.12
- Verify that at least one namespace and signal is used when subscribing
- Validate that the specified namespaces exist
- Check the status of the recording on the broker before attempting to play
- Separate progress output from other output, which was swallowed before
- Fix a bug where candumps could not be uploaded

### Features

- Support for login with a web browser
- Support for personal access keys
- Support for deleting projects
- Support for listing user organisations
- Support for listing, downloading and deleting signal databases
- Support for broker log history and tail
- Download a file from a broker
- Upload custom configurations to the cloud
- Broker lifecycle: start, stop, pause, refresh-config, upload, download,
  delete, record and stop-record
- `--all-namespaces` when running diagnose
- Support for running with docker
- Seek to a target second in a recording
- Activate a token directly on creation
- Export signal values as influx line protocol
- First version of `new-script`
- Multiple plots, one for each signal
- A TUI exploration app
- Upload raw candumps
- Sample recordings (import, list), and copy a recording to a project
- Convert between different CAN formats
- Start, stop, pause and seek work with cloud brokers using only the recording
  session id, and with personal brokers
- Act as a ProtoPie connect bridge
- Convert between log, asc and blf with cantools
