acbridge 1.1.3 → 1.4.0

package/README.md

@@ -98,18 +98,20 @@ Link an ecosystem account, or connect open-protocol devices directly from a LAN
 |---|---|
 | **Home Assistant** | `acbridge link home-assistant --url http://homeassistant.local:8123 --token <token>` |
 | **Philips Hue** | `acbridge link hue --host <bridge-ip>` — then press the bridge's link button |
-| **MQTT** (Zigbee2MQTT, Tasmota, ESPresense…) | `acbridge link mqtt --host <broker[:port]>` — every Home Assistant Discovery device appears; no vendor account needed |
+| **MQTT** (Zigbee2MQTT, ESPresense, OpenMQTTGateway) | `acbridge link mqtt --host <broker[:port]>` — every Home Assistant Discovery device appears; no vendor account needed |
 | **SmartThings** | `acbridge link smartthings` — browser sign-in |
-| **Tuya / Smart Life** | `acbridge link tuya` — terminal wizard |
+| **Tuya / Smart Life** | `acbridge link tuya` — terminal wizard; add `--user-code` to sign in with just the Smart Life app's User Code, no developer account |
 | **Meross** | `acbridge link meross` — terminal wizard |
 | **eWeLink (Sonoff)** | `acbridge link ewelink` — terminal wizard |
 | **Govee** | `acbridge link govee` — API key |
 | **Nanoleaf** | `acbridge scan` → `acbridge connect <device>` while holding the panel's power button |
 | **TP-Link Kasa, WiZ, Yeelight, LIFX, Shelly, ESPHome…** | `acbridge scan` → `acbridge connect <device>` |
 
-Wizard secrets prompt with muted echo and are stored **only on this machine** — in your OS
-keychain where one is available, `0600` files otherwise. Every secret flag has a `--token-file` /
+Wizard secrets prompt with muted echo and are stored **only on this machine** — in `0600` files,
+mirrored into your OS keychain where one is available. Every secret flag has a `--token-file` /
 `--key-file` / `--password-file` twin for CI, which touches neither argv nor the environment.
+Moving machines? `acbridge backup export` writes a passphrase-encrypted bundle of your device
+credentials, and `acbridge backup import` merges it safely on the new box.
 
 ## Command reference
 
@@ -180,7 +182,7 @@ acbridge devices set heater thermostat.setSetpoint --param celsius=21
 |---|---|
 | `acbridge setup` | Once per machine: installs the Claude Code plugin and managed settings (merged, never overwritten), and — if Codex is installed — merges AC Bridge's session-state hooks into `~/.codex/hooks.json` (every foreign hook preserved). |
 | `acbridge doctor` | Diagnoses everything — agent installs, plugin, sign-in, account, LAN-scan capability, bridge reachability — and **each line prints its own fix**. |
-| `acbridge capture on/off/status` | The per-machine session-transcript capture switch. |
+| `acbridge backup export` / `import` | A passphrase-encrypted bundle of this machine's device credentials. Export is non-destructive and verified; import merges (never clobbers) and snapshots what it replaces. |
 | `acbridge uninstall` | The clean exit: unwires everything `setup` wired, asks about your account data (default: keep), then hands off to `npm uninstall -g acbridge`. `--purge` deletes everything AC Bridge stored so a future install starts fresh. |
 
 ### Voice (preview)
@@ -224,9 +226,9 @@ Settings resolve **environment variable → `~/.claude-bridge/config.json` → d
 
 ## Good to know
 
-- **Your credentials stay on your machine.** Device and provider secrets are written to your OS
-  keychain where one is available, and to `0600` files otherwise — they never leave the machine.
-  `acbridge logout` removes them.
+- **Your credentials stay on your machine.** Device and provider secrets are written to `0600`
+  files, mirrored into your OS keychain where one is available — they never leave the machine.
+  `acbridge logout` removes them; `acbridge backup export` is how they move with you.
 - **Your agent's tool policy is untouched.** AC Bridge installs no permission rules and never
   changes what your agents are allowed to do — it only listens to their state.
 - **Nothing lingers.** The bridge runs only while something is holding it — the app, a daemon, a