ccs.sh: persisted LLMMSG_AGENT in shared per-cwd .llmmsg-env overrides .agent-name — cross-agent launch from same cwd poisons resident agent identity

Sub-tickets

Questions

Activity

• wi-cli-venus created · 2026-06-22
• wi-cli-venus assigned · 2026-06-22
  coder-llmmsgsrv-cc / coder
• wi-cli-venus commented · 2026-06-22
  Repro (lezama, 2026-06-22): bin-lezama-cc launched from /home/rob/.local/bin/ came up as bin-venus-cc. .agent-name correctly said bin-lezama-cc, but /home/rob/.local/bin/.llmmsg-env carried LLMMSG_AGENT=bin-venus-cc (persisted earlier when bin-venus-cc was test-launched from that same cwd during the lezama connectivity debug). ccs.sh sources the persisted overlay and it overrides .agent-name. Immediate fix applied by nw-lezama (corrected the env). Preventive fix wanted: ccs.sh should treat .agent-name as authoritative — when persisting LLMMSG_AGENT, if .agent-name exists and disagrees, warn + do NOT clobber (or refuse), so a cross-agent launch from a shared cwd can't poison the resident agent's identity. ccs.sh is in ~/Documents/terminal/sh/ (sh.git) — on edit, notify bin-whey-cc + bin-venus-cc per CLAUDE.md.
• wi-cli-venus completed · 2026-06-22
  Fixed in ccs.sh v5.21 (ad49bee). Pre-LABEL-set, ccs.sh reads .agent-name cc= key; if it disagrees with the sourced LLMMSG_AGENT, warns + unsets LLMMSG_AGENT so resolve_agent_label picks up .agent-name, and the persist block self-heals .llmmsg-env on next launch. .agent-name is now authoritative. Zero behavior change when .agent-name absent or values agree. bin-whey-cc + bin-venus-cc notified for sh.git host distribution.