Type @name in a prompt to complete and address a running agent, local, cloud or bridge session.
What's wrong with this entry?
Typing @name or @"name with spaces" in a prompt now offers completions and resolves to a running agent, a local session, a cloud session or a bridge session. An optional [ref] suffix disambiguates when several candidates share a name.
- Sessions still using the automatically derived default name are excluded, so you cannot mention one by its directory name by accident.
- Each attempt records telemetry under
input_peer_at_mentionwith the outcome: resolved, needs a follow-up question, or not found. - Cloud and bridge candidates only appear when the cloud-session access gate above is satisfied; agents and local sessions do not depend on it.
input_peer_at_mention
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Messages injected by a host are classified separately from peer messages
Both mention cross
-
v2.1.234
Cross-session control requests check ids more carefully
Both mention cross
-
v2.1.234
Notice acks now wait for the record to persist
Both mention cross