A member's Reason CLI on the network long-polls here for the next Reason Network call (list_team, send_message, networkWho, networkAsk) routed to it: the workspace's, when its engine is on the workspace's network, and its own user's calls from connector grants on the engine team whose team_id it reports, from any workspace. A claim that reports the hosted sessions the computer registered (hosted) is answered with those it carries now (hosted): its own user's hosted assistants' sessions on that network, each carried by one of their computers on it. Only the Reason CLI may: any other sign-in gets 403 agent_network_cli_only.

_{Scope: run}