HA Editor

A minimal Home Assistant add-on for editing your configuration: a file tree and the Monaco editor, with no accounts, extensions, Git integration, terminal, or debugger. It is a lightweight alternative to the Studio Code Server add-on.

Installation

Or add it manually:

1. In Home Assistant, go to Settings → Add-ons → Add-on store.
2. Open the ⋮ menu, select Repositories, and add https://github.com/j4n-e4t/ha-editor.
3. Find HA Editor, select Install, then Start. Turn on Show in sidebar.
4. Open Editor from the sidebar.

Requires Home Assistant OS or a Supervised installation on amd64 or aarch64 (for example a Raspberry Pi 4/5 or Home Assistant Green). Installation downloads a prebuilt image from GitHub Container Registry; nothing is compiled on your device.

See the add-on documentation for usage details.

Development

The add-on lives in ha_editor/. It requires Node.js 24+. The UI is React + Tailwind CSS with shadcn/ui components and Lucide icons; the server is Express on Node.js.

cd ha_editor
npm ci
npm run dev

Open the Vite URL printed in the terminal. Development edits the bundled ha_editor/.example/ files, never your actual Home Assistant configuration. The API listens on localhost:8099.

npm run check
npm test
npm run build
CONFIG_ROOT=/absolute/path/to/config HOST=127.0.0.1 npm start

The standalone server has no login. Keep it on localhost; the add-on uses Home Assistant authentication through ingress.

For a standalone container (local access only):

docker build -t ha-editor ha_editor
docker run --rm -p 127.0.0.1:8099:8099 -e INGRESS_ONLY=false -v /absolute/path/to/config:/config ha-editor

Releasing

Bump version in ha_editor/config.yaml and add an entry to ha_editor/CHANGELOG.md, then push to main. CI builds ghcr.io/j4n-e4t/amd64-addon-ha_editor and ghcr.io/j4n-e4t/aarch64-addon-ha_editor on native runners and tags them with that version. Home Assistant may notice the new version before CI finishes; an update started in that window fails to pull and succeeds once the images are published, usually a few minutes later.

To test the image without publishing, remove the image: line from config.yaml in a local add-on copy; the Supervisor then builds the Dockerfile on the device.

Verification

npm run check type-checks the project and npm run build bundles the editor and workers; the add-on image runs only the build, so installation stays light on low-memory devices. npm test exercises the real HTTP API against temporary directories, including conflicts and access restrictions, plus the file-icon classification. CI runs the type check, tests, and image builds for amd64 and aarch64 on every push. The React UI and installation on Home Assistant OS still need manual testing on a running instance.