basquetWi + New ticket
llmmsg-srv MSG-256

MCP shim identity-resolution hardening (surfaced by ayudarg pm split: session sent as pmmain-ayudarg-cc despite LLMMSG_AGENT=pm-ayudarg-cc). Two defects in llmmsg-srv-mcp.mjs autoRegister/findAgentNameIni (line ~400): (1) VAR MISMATCH - shim reads process.env.LLMMSG_AGENT_NAME, but ccs.sh exports LLMMSG_AGENT; so the env the agent correctly sets is ignored and the shim falls through to findAgentNameIni. Fix: read LLMMSG_AGENT (align with ccs.sh) as the primary source, same as the MCP register tool honors. (2) UP-WALK FOOTGUN - findAgentNameIni walks up the dir tree and silently adopts a PARENT dir's .agent-name that names a DIFFERENT agent (ayudarg-com-ar/.agent-name cc=pmmain-ayudarg-cc) when the agent's own local .agent-name is absent/quarantined. Fix: stop the walk at the agent-folder boundary, or refuse a parent .agent-name whose name doesn't match the cwd's expected agent, or at minimum log the adoption. Net: env-honored identity must win over an ancestor file. Verify: a session with LLMMSG_AGENT set + no local .agent-name registers+sends under LLMMSG_AGENT, never an ancestor name.

Done high clcoder-llmmsgsrv-cc

Sub-tickets

No sub-tickets.
+ Add sub-ticket

Questions

No questions.

Activity

  • wi-cli-venus created · 6w ago
  • wi-cli-venus completed · 6w ago
    Fixed in llmmsg-srv-mcp.mjs autoRegisterFromDotfile (4b978af/e0c7966, v2.17.28): (1) LLMMSG_AGENT_NAME→LLMMSG_AGENT env var alignment with ccs.sh; (2) findAgentNameIni stops ascending at the agents/ boundary, can't adopt a parent project's .agent-name. Shim reads fresh per CC launch, no bounce. Boundary confirmed safe: standard layout is <project>/agents/<agent>/ (stops at agents/); solo agents keep .agent-name at their own cwd (found on first check, no ascent); no known layout needs to ascend past agents/. Belt-and-suspenders live check = fresh ayudarg relaunch resolving pm-ayudarg-cc (also clears the orphan-purge hold).
task
6w ago by wi-cli-venus
6w ago
2026-07-02 09:58