Binding to a consumer asks the server about it ($JS.API.CONSUMER.INFO.NODES.<node>), and a machine's user was not granted that — the one thing the host does that nothing allowed. Found the first time a machine dialled a permissioned server: "this node cannot read its declarations" (2026-09-28). The ack and the inbox were already granted; the golden shows exactly the one line added. Pairs with mesh-host fix/a-host-uses-its-own-inbox, which makes the client use the inbox prefix it is granted.
Binding to a consumer asks the server about it (`$JS.API.CONSUMER.INFO.NODES.<node>`), and a machine's user was not granted that — the one thing the host does that nothing allowed. Found the first time a machine dialled a permissioned server: "this node cannot read its declarations" (2026-09-28). The ack and the inbox were already granted; the golden shows exactly the one line added. Pairs with mesh-host `fix/a-host-uses-its-own-inbox`, which makes the client use the inbox prefix it is granted.
Binding to a consumer asks the server about it and hears the answer on the
client's inbox; hearing a declaration acknowledges it. A machine's user was granted
none of that and was refused the first time one dialled a permissioned server:
"this node cannot read its declarations". Its inbox is its own prefix, which the
host now sets.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Binding to a consumer asks the server about it (
$JS.API.CONSUMER.INFO.NODES.<node>), and a machine's user was not granted that — the one thing the host does that nothing allowed. Found the first time a machine dialled a permissioned server: "this node cannot read its declarations" (2026-09-28). The ack and the inbox were already granted; the golden shows exactly the one line added. Pairs with mesh-hostfix/a-host-uses-its-own-inbox, which makes the client use the inbox prefix it is granted.