Agent Mesh
Go a2aa2a-protocolagent-meshagentic-aiinferencemcpmeshmesh-networknetwork-securitynetworking-aip2p-network
mobile: a token-joined phone changes labels with Reset device identity
Tomas Tormob634a8b9cc27
diff --git a/mobile/agentmesh-node-app/README.md b/mobile/agentmesh-node-app/README.mdindex 1a09387c..38b056ee 100644--- a/mobile/agentmesh-node-app/README.md+++ b/mobile/agentmesh-node-app/README.md@@ -139,7 +139,7 @@ Exposes capabilities directly to the OS registry, allowing native assistants (li1. **Dashboard Tab**: Displays current status, Node ID, connected peers, and DHT size.2. **Services Tab**: Allows enabling/disabling embedded sensors (Battery/Location) and bridging external local MCP servers.-3. **Config Tab**: The node's labels and attenuation, the app's stand-in for `agentmesh-node.yaml`. Labels (comma-separated `key=value`) are set here; the control plane attests them into the node's Biscuit at enrollment, so changing them later means pressing Re-enroll, which re-attests them with the login session saved at enrollment (the browser opens only if that session has expired) and keeps the node's identity. A node that joined with a token or QR code has no login session and the control plane re-mints from the labels already on record, so Re-enroll is disabled for it: unenroll and join again with the new labels. Attenuation is Datalog rules, policies and checks that limit who may call this node, one statement per line (e.g. `check if label("region", "eu-west-1");`). They are read when the node starts, and a syntax error fails the start. Same syntax and same errors as the `attenuation` block of `agentmesh-node.yaml`; see [Node configuration](../../site/content/docs/reference/node-config.md#attenuation).+3. **Config Tab**: The node's labels and attenuation, the app's stand-in for `agentmesh-node.yaml`. Labels (comma-separated `key=value`) are set here; the control plane attests them into the node's Biscuit at enrollment, so changing them later means pressing Re-enroll, which re-attests them with the login session saved at enrollment (the browser opens only if that session has expired) and keeps the node's identity. A node that joined with a token or QR code has no login session and the control plane re-mints from the labels already on record, so Re-enroll is disabled for it: clear the device identity in the **Unenroll** view by choosing the **Reset device identity** option, then join again with the new labels. Attenuation is Datalog rules, policies and checks that limit who may call this node, one statement per line (e.g. `check if label("region", "eu-west-1");`). They are read when the node starts, and a syntax error fails the start. Same syntax and same errors as the `attenuation` block of `agentmesh-node.yaml`; see [Node configuration](../../site/content/docs/reference/node-config.md#attenuation).---diff --git a/mobile/agentmesh-node-app/lib/main.dart b/mobile/agentmesh-node-app/lib/main.dartindex bcffdf9b..2b747124 100644--- a/mobile/agentmesh-node-app/lib/main.dart+++ b/mobile/agentmesh-node-app/lib/main.dart@@ -1456,7 +1456,9 @@ class _NodeControlPageState extends State<NodeControlPage> {const Padding(padding: EdgeInsets.only(top: 6),child: Text(- 'Joined with a token. Unenroll and join again to change labels.',+ 'Joined with a token. To change labels, clear the device '+ 'identity in the Unenroll view by choosing the Reset '+ 'device identity option, then join again.',style: TextStyle(fontSize: 12, color: Colors.grey),),),diff --git a/site/content/docs/preview/mobile.md b/site/content/docs/preview/mobile.mdindex 640bfbf0..95cbd5c3 100644--- a/site/content/docs/preview/mobile.md+++ b/site/content/docs/preview/mobile.md@@ -355,9 +355,12 @@ The Config tab holds what `agentmesh-node.yaml` holds on a desktop: labels(one Datalog statement per line, with the same syntax and the same errors asthe file). Labels are attested at enrollment, so changing them requirespressing **Re-enroll to apply**. Browser-enrolled nodes can use the saved-login session to re-enroll while keeping their peer ID. Token-enrolled-nodes must unenroll and join again to change labels. The tab also shows the-API token that protects the node's local API on the phone.+login session to re-enroll while keeping their peer ID. To change labels,+token-enrolled nodes must clear the device identity in the **Unenroll** view+by choosing the **Reset device identity** option, then join again, because a+join that keeps the peer ID gets back the labels on record.+The tab also shows the API token that protects the node's local API on the+phone.On Android 16 the app also registers two AppFunctions, `getMeshStatus` and`callRemoteMeshTool`, so an on-device assistant can use the mesh without the