Claude Code uses ~/.claude/ as its config directory by default, which includes your login credentials in .claude.json. You can override this with the CLAUDE_CONFIG_DIR environment variable to point at a different config directory, enabling automatic account switching based on where you run claude.
1. Create a separate config directory for your second account:
mkdir ~/.claude-personal
This document describes the workflow and tooling used to manage a Home Assistant (HAOS) instance through Claude Code, Anthropic's AI-powered CLI assistant. It covers the integration architecture, documentation practices, the types of work achieved, established patterns, and a worked example.
The core integration is ha-mcp, a Docker container deployed via Ansible that exposes the Home Assistant API as an MCP (Model Context Protocol) server. MCP is a protocol that lets AI assistants call external tools — in this case, it exposes the HA REST API as discrete operations (read entity state, create automation, update script, etc.) that Claude Code can invoke directly during a conversation.
Major PostgreSQL upgrades (e.g., 14→18) require a full dump and restore — the data files are not compatible across major versions.
Note: Immich requires vector extensions, and they supply an image with them bundled in as
ghcr.io/immich-app/postgres:18-vectorchord0.5.3-pgvector0.8.1
docker exec -t <container> pg_dumpall --clean --if-exists --username=<user> | gzip > dump.sql.gzdocker compose down
Update (2026-03-20): This workaround is no longer needed as of Immich v2.6.0+
Immich v2.6.0 (PR #26178) ships with ROCm 7.2 and replaces the old ROCM ONNX Runtime provider with the MIGraphX backend. ROCm 7.2 natively supports gfx1150/gfx1151 (RDNA 3.5), so the custom Dockerfile and
HSA_OVERRIDE_GFX_VERSIONhack are no longer necessary. See the v2.6.0+ instructions below.