{"version":"2.1.267","anchor":"own-endpoint-shadowed-detection-for-list-agents-gated-by-t","canonical_anchor":"own-endpoint-shadowed-detection-for-list-agents-gated-by-t","heading":"Own-endpoint-shadowed detection for \/list-agents, gated by tengu_session_stable_address","tier":"soon","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/own-endpoint-shadowed-detection-for-list-agents-gated-by-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### Own-endpoint-shadowed detection for \/list-agents, gated by tengu_session_stable_address\n\n\/list-agents can now detect when another process is already using this session's own address\n\n**Unclear.** Nothing has been read yet about whether the `tengu_session_stable_address` flag that controls this is on or off by default.\n\n**What**\n\nA new check detects when another live process on the same machine is already listening on the socket that represents this session's \"stable address\" (its identity), even though it's a different process. When that happens, the `\/list-agents` (also `\/peers`) output changes which address token it displays for this session's own entry, to reflect that its usual address is shadowed by the other process.\n\n**Why**\n\nWithout this, a session could display an address for itself that's actually claimed by a different, unrelated process, making it confusing or unreliable for another session to message it correctly.\n\n- Area: Sessions\n- Names: `\/list-agents`, `\/peers`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}