docs: snapshot of the project's Claude Code memory

Decisions, environment quirks and pitfalls learned while working on AgentHub
(docs/claude-memory/, indexed by MEMORY.md). Notes holding personal account
details are left out.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

docs/claude-memory/agy-auto-updates-on-run.md

@@ -0,0 +1,16 @@
+---
+name: agy-auto-updates-on-run
+description: "Running `agy` (Antigravity CLI) even with an isolated HOME auto-updates the real ~/.local/bin/agy binary"
+metadata:
+  node_type: memory
+  type: feedback
+  originSessionId: c4043107-b649-4aaa-915a-0dd4a0a169cd
+  modified: 2026-09-29T04:39:33.876Z
+---
+
+Any `agy` run spawns a background self-updater that replaces `~/.local/bin/agy` in place (keeps `agy.<n>.old`), even with `HOME=/tmp/...`. Login is in the OS keyring, so an isolated HOME still runs as the user's account. On 2026-09-29 a spike run updated the user's agy 1.0.0 → 1.2.13 unintentionally.
+
+**Why:** a spike is not supposed to change the user's installed tools.
+**How to apply:** before running agy in a spike, tell the user it will self-update, or find/disable the updater setting first; always report it if it happened.
+
+2026-10-08: one `agy --print /usage --output-format json` (user approved) updated 1.2.17 → 1.3.1 ~2 s after it exited. AgentHub v2.5.12 now runs that command for the Usage panel (every 5 min while a tab polls), so agy on a user's machine may self-update from AgentHub; `AGENTHUB_AGY_USAGE=0` turns it off. Tests never run the real agy (quota.test.js + scripts/test-server.js set it to 0).