v0.1.33

A finished answer is no longer thrown away. When Claude Code had answered a job and
then failed while closing, humanikd reported the whole job as failed. One example: a
plugin's end-of-session hook could not find node. An office then answered with its
backup model instead, and that answer was charged to your credits. humanikd now keeps
the answer and writes the error to its log. A job you or Humanik stopped is still
reported as stopped.

Claude Code hooks can find your programs. humanikd runs as a background service, and
a service gets a short PATH (/usr/bin:/bin:/usr/sbin:/sbin on a Mac). Plugin hooks that
run node or another program installed with Homebrew failed with "command not found".
Jobs now get the same extra folders humanikd already searches: Homebrew,
/usr/local/bin, ~/.local/bin and npm's global folder.

Everything means every tool. With allowed_tools: ["*"], a job that did not list its
tools was refused. It now gets every built-in tool plus every MCP server and connector
your Claude Code setup has.

Files between this computer and Humanik. An office tool can upload a file from this
computer straight to storage, or save a file here, but only in the folders you allow
(local_files in the config; Folders jobs may use in the app). humanikd's and
Claude Code's own files are always refused.

Optional file scope. You can limit file tools and commands to set folders. Both are
off by default. See CONFIG.md.

Large output no longer ends a job. One output event can be up to 64 MB. A larger one
is skipped and the job continues.

---

Install

macOS / Linux

curl -fsSL https://github.com/humanikio/humanikd-dist/releases/latest/download/install.sh | sh

Windows

irm https://github.com/humanikio/humanikd-dist/releases/latest/download/install.ps1 | iex

The installer also installs the Humanik OS desktop app on macOS and Windows
(skip it with HUMANIKD_NO_APP=1). Then humanikd setup.

Verify a download

Both installers check each file against its .sha256. To check by hand:

sha256sum -c humanikd-linux-amd64.sha256

To confirm a file was built by our release workflow, with cosign:

cosign verify-blob humanikd-linux-amd64 \
  --bundle humanikd-linux-amd64.sigstore.json \
  --certificate-identity-regexp '^https://github.com/humanikio/humanikd/\.github/workflows/release\.yml@' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

v0.1.32

Chat notifications use one request for every workspace. Before, the app asked Humanik
for your chats once per workspace, every few minutes and each time you switched back to it,
which slowed chat lists for everyone. It now asks once. Switching back to the app refreshes
your chats and notifications at most once a minute. A failed refresh keeps what you already
have.

Notifications cover your chats with AI employees. Chats your Nova has with them are no longer
included, because you are not a member of those chats.

---

Install

macOS / Linux

curl -fsSL https://github.com/humanikio/humanikd-dist/releases/latest/download/install.sh | sh

Windows

irm https://github.com/humanikio/humanikd-dist/releases/latest/download/install.ps1 | iex

The installer also installs the Humanik OS desktop app on macOS and Windows
(skip it with HUMANIKD_NO_APP=1). Then humanikd setup.

Verify a download

Both installers check each file against its .sha256. To check by hand:

sha256sum -c humanikd-linux-amd64.sha256

To confirm a file was built by our release workflow, with cosign:

cosign verify-blob humanikd-linux-amd64 \
  --bundle humanikd-linux-amd64.sigstore.json \
  --certificate-identity-regexp '^https://github.com/humanikio/humanikd/\.github/workflows/release\.yml@' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

v0.1.31

No visible changes. The app no longer carries code for a HumaChat request that
Humanik has retired. Nothing in the app used it.

---

Install

macOS / Linux

curl -fsSL https://github.com/humanikio/humanikd-dist/releases/latest/download/install.sh | sh

Windows

irm https://github.com/humanikio/humanikd-dist/releases/latest/download/install.ps1 | iex

The installer also installs the Humanik OS desktop app on macOS and Windows
(skip it with HUMANIKD_NO_APP=1). Then humanikd setup.

Verify a download

Both installers check each file against its .sha256. To check by hand:

sha256sum -c humanikd-linux-amd64.sha256

To confirm a file was built by our release workflow, with cosign:

cosign verify-blob humanikd-linux-amd64 \
  --bundle humanikd-linux-amd64.sigstore.json \
  --certificate-identity-regexp '^https://github.com/humanikio/humanikd/\.github/workflows/release\.yml@' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

v0.1.30

The app updates itself. Before, Update now replaced humanikd only, and
nothing said the app was out of date, so a Mac could run the newest humanikd with
an app several versions old (missing the Frameworks and Models pages). Now the
app checks its own version too. When it is older than the newest release,
Update now replaces it after humanikd: it downloads the app, checks it against
its published checksum, then the app closes and opens again on the new version.
The tray, the update button at the top of the window, Overview and the Updates tab
all count an out-of-date app.

An app older than v0.1.30 cannot update itself. Run the install command once:

curl -fsSL https://github.com/humanikio/humanikd-dist/releases/latest/download/install.sh | sh

irm https://github.com/humanikio/humanikd-dist/releases/latest/download/install.ps1 | iex

---

Install

macOS / Linux

curl -fsSL https://github.com/humanikio/humanikd-dist/releases/latest/download/install.sh | sh

Windows

irm https://github.com/humanikio/humanikd-dist/releases/latest/download/install.ps1 | iex

The installer also installs the Humanik OS desktop app on macOS and Windows
(skip it with HUMANIKD_NO_APP=1). Then humanikd setup.

Verify a download

Both installers check each file against its .sha256. To check by hand:

sha256sum -c humanikd-linux-amd64.sha256

To confirm a file was built by our release workflow, with cosign:

cosign verify-blob humanikd-linux-amd64 \
  --bundle humanikd-linux-amd64.sigstore.json \
  --certificate-identity-regexp '^https://github.com/humanikio/humanikd/\.github/workflows/release\.yml@' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

v0.1.29

Every screen says why Claude Code was not found, and how to fix it. Before, a
binary: line in config.yaml naming a Claude Code that had been moved showed as
"Claude Code is not installed", with the install command. Installing again could not
fix that. Now the message names the line and where Claude Code actually is. The
Claude Code page has Remove the line, which shows the change to config.yaml
before saving it, and humanikd fix claude does the same in a terminal. The Chrome
checklist starts with "Claude Code is installed", and Overview lists the problem under
Needs you.

---

Install

macOS / Linux

curl -fsSL https://github.com/humanikio/humanikd-dist/releases/latest/download/install.sh | sh

Windows

irm https://github.com/humanikio/humanikd-dist/releases/latest/download/install.ps1 | iex

The installer also installs the Humanik OS desktop app on macOS and Windows
(skip it with HUMANIKD_NO_APP=1). Then humanikd setup.

Verify a download

Both installers check each file against its .sha256. To check by hand:

sha256sum -c humanikd-linux-amd64.sha256

To confirm a file was built by our release workflow, with cosign:

cosign verify-blob humanikd-linux-amd64 \
  --bundle humanikd-linux-amd64.sigstore.json \
  --certificate-identity-regexp '^https://github.com/humanikio/humanikd/\.github/workflows/release\.yml@' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

v0.1.28

Windows: the log no longer grows without limit. humanikd starts a new log file
once serve.log passes 8 MiB. On Windows the app kept serve.log open in a way that
blocked this, so while the app was open the log kept growing. macOS and Linux were
not affected.

Windows: Docker is found in more places. humanikd now also looks for docker.exe
in Docker Desktop's folder and in System32.

Tested on Windows before every release. Each release now runs the tests on
Windows, macOS and Linux first. On Windows this includes the Chrome checks from
v0.1.26: finding the Claude extension's registry entry and seeing that Chrome is open.

---

Install

macOS / Linux

curl -fsSL https://github.com/humanikio/humanikd-dist/releases/latest/download/install.sh | sh

Windows

irm https://github.com/humanikio/humanikd-dist/releases/latest/download/install.ps1 | iex

The installer also installs the Humanik OS desktop app on macOS and Windows
(skip it with HUMANIKD_NO_APP=1). Then humanikd setup.

Verify a download

Both installers check each file against its .sha256. To check by hand:

sha256sum -c humanikd-linux-amd64.sha256

To confirm a file was built by our release workflow, with cosign:

cosign verify-blob humanikd-linux-amd64 \
  --bundle humanikd-linux-amd64.sigstore.json \
  --certificate-identity-regexp '^https://github.com/humanikio/humanikd/\.github/workflows/release\.yml@' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

v0.1.27

Windows: the app no longer crashes while a command runs. Pressing Update
Claude Code crashed the page with "u is not a function" once the command printed
its second line. Update now, the service buttons and linking use the same output
panel, so they could crash the same way. The command itself kept running. macOS was
not affected.

---

Install

macOS / Linux

curl -fsSL https://github.com/humanikio/humanikd-dist/releases/latest/download/install.sh | sh

Windows

irm https://github.com/humanikio/humanikd-dist/releases/latest/download/install.ps1 | iex

The installer also installs the Humanik OS desktop app on macOS and Windows
(skip it with HUMANIKD_NO_APP=1). Then humanikd setup.

Verify a download

Both installers check each file against its .sha256. To check by hand:

sha256sum -c humanikd-linux-amd64.sha256

To confirm a file was built by our release workflow, with cosign:

cosign verify-blob humanikd-linux-amd64 \
  --bundle humanikd-linux-amd64.sigstore.json \
  --certificate-identity-regexp '^https://github.com/humanikio/humanikd/\.github/workflows/release\.yml@' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

v0.1.26

Claude Code 2.1.300 or newer is needed for the browser. Each release now names
the oldest version of each framework it works with. When this computer uses Claude
Code, OpenClaw or Ollama and its version is too old, the app says so on the
framework's page, on This machine › Overview, Agent and Updates.
Update Claude Code runs Claude Code's own claude update. Until Claude Code is
updated, browser jobs are refused with the reason and linking Chrome does not
start; other jobs still run. See Claude Code.

Windows: the Chrome checklist. "Chrome is open" is now checked on Windows.
"Chrome can reach Claude Code" is read from the registry; when it cannot be
confirmed, the page says it could not check, instead of "not yet". In v0.1.25 both
lines always showed "not yet" on Windows, even when jobs could use Chrome.

Linking Chrome says what went wrong. When Claude Code does not reach Chrome,
the message now includes the Claude Code version and what it answered.

---

Install

macOS / Linux

curl -fsSL https://github.com/humanikio/humanikd-dist/releases/latest/download/install.sh | sh

Windows

irm https://github.com/humanikio/humanikd-dist/releases/latest/download/install.ps1 | iex

The installer also installs the Humanik OS desktop app on macOS and Windows
(skip it with HUMANIKD_NO_APP=1). Then humanikd setup.

Verify a download

Both installers check each file against its .sha256. To check by hand:

sha256sum -c humanikd-linux-amd64.sha256

To confirm a file was built by our release workflow, with cosign:

cosign verify-blob humanikd-linux-amd64 \
  --bundle humanikd-linux-amd64.sigstore.json \
  --certificate-identity-regexp '^https://github.com/humanikio/humanikd/\.github/workflows/release\.yml@' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

v0.1.25

Check this if jobs on your computer use Gmail, Drive or other connectors. With
My Claude Code (the default), which connectors and MCP servers jobs may use is
now decided by Claude Code's own settings: the permissions.allow list in
~/.claude/settings.json. Claude Code already added that list to every job, so a
setting in humanikd could only ever add to it. Connector rules you had in
allowed_tools are kept for the separate setup and no longer used with My Claude
Code. The app shows a warning for each one and a Turn on here button. See
Claude Code.

Browser jobs use only this computer's Chrome. Claude in Chrome belongs to your
Claude account, so a job could see Chrome on your other computers, and asking to
switch browsers showed a "Connect?" prompt on all of them. Now humanikd links jobs
to the Chrome on this computer (Link this computer's Chrome in the app, or
humanikd chrome link), never lets a job switch browsers, and stops a job that
picks another one.

New pages in the app: Frameworks and Models. Frameworks > Claude Code shows
the account jobs run as, your connectors and MCP servers in three groups (from
your Claude account, added on this computer, from plugins), the browser, and the
exact command humanikd starts for each job, with a button to copy it.
Frameworks > OpenClaw and Models > Ollama show those programs. Each section
says whether humanikd sets it or the program itself does.

Choose which Claude Code setup jobs use. My Claude Code uses the Claude Code
you use in Terminal. Separate setup for jobs uses its own folder
(~/.humanikd/claude) with its own sign-in, so your hooks and CLAUDE.md stay out
of jobs. Each setup keeps its own browser switch, and the separate setup its own
MCP servers, so switching back and forth loses nothing.

Sign in to Claude Code from the app, with a Cancel button if you close the
browser tab. Links that open your browser now show an arrow.

For config.yaml: two new keys, backend.claude_agent.claude_dir and
backend.claude_agent.setups. Older humanikd refuses a file that has them, so the
app writes them only when your settings need them. See
Claude Code.

---

Install

macOS / Linux

curl -fsSL https://github.com/humanikio/humanikd-dist/releases/latest/download/install.sh | sh

Windows

irm https://github.com/humanikio/humanikd-dist/releases/latest/download/install.ps1 | iex

The installer also installs the Humanik OS desktop app on macOS and Windows
(skip it with HUMANIKD_NO_APP=1). Then humanikd setup.

Verify a download

Both installers check each file against its .sha256. To check by hand:

sha256sum -c humanikd-linux-amd64.sha256

To confirm a file was built by our release workflow, with cosign:

cosign verify-blob humanikd-linux-amd64 \
  --bundle humanikd-linux-amd64.sigstore.json \
  --certificate-identity-regexp '^https://github.com/humanikio/humanikd/\.github/workflows/release\.yml@' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com

v0.1.25-dev.1

Test build. This is a pre-release. The normal install command does not
install it. To try it:

curl -fsSL https://github.com/humanikio/humanikd-dist/releases/download/v0.1.25-dev.1/install.sh | HUMANIKD_VERSION=v0.1.25-dev.1 sh

$env:HUMANIKD_VERSION = 'v0.1.25-dev.1'; irm https://github.com/humanikio/humanikd-dist/releases/download/v0.1.25-dev.1/install.ps1 | iex

Binaries, the desktop app, checksums and cosign signatures for v0.1.25-dev.1.

Notes for this version were not written before the tag. See the
README for what changed.

---

Install

macOS / Linux

curl -fsSL https://github.com/humanikio/humanikd-dist/releases/latest/download/install.sh | sh

Windows

irm https://github.com/humanikio/humanikd-dist/releases/latest/download/install.ps1 | iex

The installer also installs the Humanik OS desktop app on macOS and Windows
(skip it with HUMANIKD_NO_APP=1). Then humanikd setup.

Verify a download

Both installers check each file against its .sha256. To check by hand:

sha256sum -c humanikd-linux-amd64.sha256

To confirm a file was built by our release workflow, with cosign:

cosign verify-blob humanikd-linux-amd64 \
  --bundle humanikd-linux-amd64.sigstore.json \
  --certificate-identity-regexp '^https://github.com/humanikio/humanikd/\.github/workflows/release\.yml@' \
  --certificate-oidc-issuer https://token.actions.githubusercontent.com