Codex for Home Assistant 0.3.8

0.3.8

• Codex CLI 0.169.0.
• The agent's instructions say that from Supervisor 2026.12 tools needing raw sockets (nmap, tcpdump) do not work, and point to curl and the Home Assistant API.

Codex for Home Assistant 0.3.7

0.3.7

• Built on ha-agent-core 0.14.0 (release notes).
• Codex CLI 0.167.2.
• Home Assistant CLI 5.7.0 (release notes).
• A skill installed from the console (under /data/home/.agents/skills) no longer reaches requests from Assist,
  automations and the Prompt API, even when the request names it with $name: each such request runs with an
  empty home directory of its own. This closes the known limit stated for 0.3.6. The console keeps every skill.
• When Codex refuses a request's sign-in, the add-on now says which one was refused: the API key set in the
  add-on's options, or the console's ChatGPT sign-in. Home Assistant can then advise checking or replacing the key
  instead of suggesting to set one.
• The health check and the morning briefing ask Codex their question the same way: in an empty home of its own,
  and with none of the Supervisor or Home Assistant credentials and addresses in its environment. Before this
  version the question ran in the console's home and saw the Home Assistant addresses.
• Codex's background service now runs the same version as the Codex CLI the add-on installed. Before this
  version the service kept its own copy of the CLI and updated it on its own schedule, so after an update the
  console showed "A background Codex service is running …, older than your Codex CLI …", and after a rollback
  the service stayed on the newer version. The first console start after the CLI version changes (the update
  button, Auto-Update, update-codex <version>, or npm install / codex update in a shell tab) now gives the
  service the installed CLI and keeps it there. Requests from Assist, automations and the Prompt API do not use
  this service.
• When the stored Codex CLI cannot run, the add-on's start now logs "Could not determine the Codex CLI version
  for the image sync" and carries on, as intended. Before this version reading the CLI's version ended the start.
• Every pull request now builds the add-on image for each architecture and checks that the bundled Codex CLI
  runs, accepts each command line the Prompt API builds, and that start-up, the console launcher, both update
  paths, provisioning, the secrets guard, the health check and the morning digest behave as recorded.

Codex for Home Assistant 0.3.6

0.3.6

• Built on ha-agent-core 0.13.1 (release notes).
• An answer from Assist, automations and the Prompt API is returned as soon as Codex reports its result, no
  longer after the Codex process has finished shutting down; anything Codex writes after its result is dropped.
• The core's warm-session option is not offered by this add-on: every request still starts a fresh Codex
  process, as before.
• A device assigned to an area is no longer refused as ambiguous when it is off: asking for the light in an
  area acts on that device whether it is on or off.
• When the agent cannot act on a request, the reason is now stated in full instead of being cut short.
• A long secret no longer starts streaming to the screen before it is hidden.
• Signing in with an API key did not work before this version: the add-on handed the key to Codex under a
  name Codex does not read, so every request from Assist, automations and the Prompt API failed with an
  authentication error. The key is now handed over under the name Codex reads. The console itself is not covered
  by this: it still needs codex login (or codex login --with-api-key), as before.
• Requests from Assist, automations and the Prompt API no longer see Codex's own built-in skills. Before this
  version every such request carried a list of the available skills, and a $name in the request text (such
  as $imagegen) put that skill's full instructions into the request. The console is unchanged and keeps
  every skill. Known limit: a skill installed under /data/home/.agents/skills is still put into such a
  request when the request text names it with $name; a later version closes this.
• A program that runs the test command by name gets the system one again. The bundled hass-mcp package
  installed a development launcher under that name ahead of it on the path; the launcher is no longer
  installed, and the image is not built if a bundled command hides a system command.
• Node.js 26.13.1, Codex CLI 0.167.1, yq 4.54.3 and Playwright MCP 0.0.85.

Codex for Home Assistant 0.3.5

0.3.5

• Built on ha-agent-core 0.12.0 (release notes).
• Home Assistant cuts a single tool call off after 60 seconds, however long the action would take. The agent
  now reads that as a clear message (the tool was cut off at its limit and the action may not have
  finished) instead of a bare timeout, and the call is recorded as failed. The agent's own tool time limit is
  raised above Home Assistant's, so the message always comes from Home Assistant's side.
• A very large answer from Home Assistant, from many devices that were each large, could run the add-on out
  of memory; it now has its own memory budget. Asking Assist for a device on an install too large for that
  now says Home Assistant's answer is too large, instead of asking you to try again.
• The console page reloads its stylesheets and scripts by itself, up to five times over about 30 seconds,
  when they do not arrive, and then says the console could not load.
• The console's menus stay on the screen on a narrow window.
• Stopping the add-on cancels a tool call that is still running, for example a script in the middle of its
  delay. This corrects the 0.3.4 note below: a script with a delay runs to its end when the agent finishes or
  disconnects, but not when the add-on itself is stopped or restarted.

Codex for Home Assistant 0.3.4

0.3.4

• Built on ha-agent-core 0.11.5 (release notes):
  a Home Assistant action that is still running when the agent finishes or disconnects is no longer cancelled
  halfway; for example a script with a delay now runs to its end. A request nobody is waiting for is closed
  after one hour at the latest.

Codex for Home Assistant 0.3.3

0.3.3

• Built on ha-agent-core 0.11.4 (release notes):
  on an installation with a large list of entity states, every confirmed action through Assist failed; the list
  is now read as it arrives and large tool catalogs, live context and tool answers no longer fail either.
  An answer past its bound is refused and named as too large instead of reported as success or silence.
• Codex CLI 0.166.0, Playwright MCP 0.0.84 and base image 9.5.2.

Codex for Home Assistant 0.3.2

0.3.2

• Built on ha-agent-core 0.11.3 (release notes):
  changing the personal skills repository option now replaces the cached clone with a fresh clone of the new
  repository; before, the old repository kept being pulled.

Codex for Home Assistant 0.3.1

0.3.1

• The configuration folder is declared with the map type app_config; the Supervisor deprecated addon_config
  and logged a warning at every start. The folder is the same one, mounted at the same path.
  Needs Supervisor 2026.07.1 or newer (older ones skip the store entry; the installed version keeps running).
• Built on ha-agent-core 0.11.2 (release notes):
  the hass-mcp registration follows the current Home Assistant URL and token at every start, so a
  changed token replaces it and a removed token unregisters it.
• Codex CLI 0.164.0 → 0.165.0 (release notes)
• Node.js 26.12.1 → 26.13.0, now Long Term Support (release notes)

Codex for Home Assistant 0.3.0

0.3.0

• New option protect_secrets, on by default: Codex can no longer read or
  change the files where Home Assistant keeps credentials — secrets.yaml,
  .storage/auth, .storage/auth_provider.homeassistant,
  .storage/core.config_entries, .storage/application_credentials,
  .cloud/, the TLS private keys in /ssl — nor open the archives in
  /backup. The app now ships its own AppArmor profile: the console, every
  tab, the prompt API and everything Codex runs are confined so that the
  kernel refuses these files, and Codex checks each command first so it gets
  a clear reason instead of an error.
  The documentation's new "Security and privacy" section lists what is
  protected and what is not. On a host without AppArmor only the command
  check is on, and the start-up log says so. Turn the option off to give
  Codex the files. Whenever the app starts with less protection than before
  (the option turned off, or the kernel half lost), Home Assistant shows a
  notification with the reason.
• The ha-debug skill lists integrations through the Home Assistant API
  instead of reading .storage/core.config_entries.
• hass-mcp 0.6.1.

Codex for Home Assistant 0.2.1

0.2.1

• The image is built on Debian base 9.5.1 (curl, xz-utils and ca-certificates
  security updates), Node.js 26.12.1, Codex CLI 0.164.0, Home Assistant CLI
  5.6.0 and Pillow 13.0.0.
• A pin that falls behind its upstream now fails the build of the commit that
  would release it, so a release cannot ship a stale base image or tool.