nearai/ironclaw ironclaw-v1.4.1-rc.2

1.4.1-rc.2 - 2026-09-24

on GitHub

Release Notes

Second patch candidate over 1.4.0, carrying the same fix as RC1.

Fixed

• Google extensions (Gmail, Google Calendar) can now be activated on a
  deployment whose operator supplies the Google OAuth client through the
  Web UI rather than environment variables. Authorization completed and then
  activation failed, and the terminal failure revoked the credential that had
  just been issued, so every retry re-consented and failed again. Two sources
  answered "is this vendor's OAuth client configured": the auth engine
  resolved client material live from administrator configuration, while the
  extension activation gate and the first-party tool-dispatch backstop read a
  map captured at process start from environment variables alone, which the
  Web UI cannot write. Readiness is now resolved per activation and per
  dispatch through the same credential chain the auth engine uses, and it
  requires a composed OAuth engine, so a vendor whose flow cannot be started
  is never reported ready.

  Within that chain, administrator configuration now takes precedence over
  deployment (environment / config.toml) client material. Deployments that
  bake client credentials and never open the administrator form are
  unaffected — they resolve through the same path as before.

Install ironclaw 1.4.1-rc.2

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/nearai/ironclaw/releases/download/ironclaw-v1.4.1-rc.2/ironclaw-installer.sh | sh

Install prebuilt binaries via powershell script

powershell -ExecutionPolicy Bypass -c "irm https://github.com/nearai/ironclaw/releases/download/ironclaw-v1.4.1-rc.2/ironclaw-installer.ps1 | iex"

Download ironclaw 1.4.1-rc.2