Harumi

Changelog

What changed in each release of the harumi CLI, newest first.

Always run the newest version — older ones aren't supported. This page lists what changed in each release. You can read the same notes from your terminal, offline, with harumi whats-new (the installed version) or harumi whats-new --all (every release).

Staying up to date

harumi tells you when a newer version is out. In an interactive terminal it prints a one-line notice after a command, with the upgrade command for the way you installed it, and a short "updated to X, see what changed" note once after you upgrade. It looks for a new version at most once a day and repeats the same notice at most once a day.

pipx upgrade harumi                          # installed with pipx
uv tool upgrade harumi                       # installed with uv
python3 -m pip install --upgrade harumi      # installed with pip

The notice is never printed when output is piped or redirected, in CI, or for harumi --version. To turn it off entirely, set HARUMI_NO_UPDATE_CHECK=1.

0.11.0 — 2026-10-13

A smaller, more consistent command set, real skills commands, and update notices.

New

  • harumi skills library lists the preset skills from the Harumi skill library; harumi skills add <slug> installs one into your clone as skills/<slug>/SKILL.md. Commit and push it so the project's assistant can use it.
  • harumi check reports everything blocking a project from running (the old repo readiness).
  • harumi runs download [RUN_ID] downloads a run's output (the latest run by default).
  • harumi whats-new shows these release notes.
  • harumi org use <ORG_ID> sets the organization sent with every request.
  • harumi new <NAME> --no-clone creates a project without cloning it.
  • harumi share update <LINK_ID> --password / --no-password sets or removes a share link's password.
  • harumi whoami now also shows your name, bio and active organization.
  • harumi tells you when a newer version is available.

Changed

  • push is now import. It always creates a new project; to send edits to an existing one, use git push harumi <branch> from your clone.
  • Every delete command is now rm: projects rm, share rm, datasources rm, schedules rm, org rm. Removing an organization member is org rm-member.
  • skill install is now agent-skills install (use --dry-run instead of skill path).

Removed

These still work in 0.11.x, hidden and with a warning that names the replacement, and are removed in 0.12.0. The full table is in Commands → Renamed in 0.11.

  • harumi repo ...: a project's repo is a plain git repo, so use git in your clone. harumi clone already sets up a harumi remote with your token.
  • projects create, outputs, run --output-dir, config set-org, profile show, env current, skill install / skill path, share set-password / rm-password, and the old remove / delete verbs.

0.10.0 — 2026-10-13

  • harumi compare <RUN_ID>... compares 2–4 runs: KPIs, the winner, and whether they used the same inputs.
  • harumi memories list|add|edit|rm manages the notes a project's assistant remembers.

On this page