You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After OpenClaw commits the sender to its owner allowlist, NemoClaw verifies the mutable config permissions and automatically restarts the managed gateway.
182
+
An exit status of `0` means activation completed, so the sender's next message should receive a reply without another manual restart.
183
+
If permission cleanup or gateway restart fails after the approval commits, `exec` exits with status `1`, reports that the approval was not rolled back, and prints the recovery command.
184
+
Correct any reported permission problem, then run `nemoclaw my-assistant gateway restart` before testing the next message; do not submit the pairing code again unless OpenClaw reports that it was not accepted.
185
+
175
186
If the webhook returns an error, verify that the public endpoint still ends in `/googlechat`, the dedicated tunnel and webhook proxy are running, and the Google Chat API configuration contains the exact same URL.
176
187
177
188
Refer to [Manage Messaging Channels](manage-messaging-channels) to stop, start, or remove Google Chat after setup.
Copy file name to clipboardExpand all lines: docs/reference/commands.mdx
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1321,6 +1321,11 @@ When cleanup succeeds, `exec` returns the remote command's exit code.
1321
1321
If cleanup cannot inspect, restore, or verify that contract, it fails closed and prints `OpenClaw permission cleanup failed (...)` to `stderr`.
1322
1322
In that case, `exec` returns the cleanup failure instead of the remote command's status.
1323
1323
1324
+
For a registered OpenClaw sandbox, a successful direct `openclaw pairing approve googlechat <code>` command also restarts the managed gateway after cleanup so the new sender allowlist applies to the next message.
1325
+
If cleanup or restart fails after the approval commits, `exec` exits with status `1` and reports that the approval was not rolled back.
1326
+
Correct any reported cleanup problem, then run `$$nemoclaw <name> gateway restart` before testing the next message.
1327
+
NemoClaw does not apply this automatic restart to unregistered or non-OpenClaw sandboxes.
1328
+
1324
1329
</AgentOnly>
1325
1330
<AgentOnlyvariant="hermes">
1326
1331
@@ -2148,6 +2153,10 @@ After the remote command exits, NemoClaw verifies and, when needed, restores the
2148
2153
When cleanup succeeds, `exec` preserves the remote command's exit code.
2149
2154
When cleanup fails closed, `exec` returns the cleanup failure and reports both statuses on `stderr`.
2150
2155
2156
+
A successful direct `openclaw pairing approve googlechat <code>` command in a registered OpenClaw sandbox restarts the managed gateway after cleanup, so the new sender allowlist applies to the next message.
2157
+
If the approval commits but cleanup or restart fails, `exec` exits with status `1`, reports that the approval was not rolled back, and directs you to run `$$nemoclaw <name> gateway restart` after correcting any cleanup problem.
2158
+
Unregistered and non-OpenClaw sandboxes do not receive this automatic restart.
0 commit comments