chore(sync): mirror docs from openclaw/openclaw@a126a9013d
This commit is contained in:
parent
d5ec67d11a
commit
c9ac3e979a
@ -1,5 +1,5 @@
|
||||
{
|
||||
"repository": "openclaw/openclaw",
|
||||
"sha": "7920f8d4fdeb6e000795cf53751b341cc5776fb4",
|
||||
"syncedAt": "2026-04-25T03:04:01.448Z"
|
||||
"sha": "a126a9013d9ff597de8c4a5824e7f675a651df53",
|
||||
"syncedAt": "2026-04-25T03:13:50.790Z"
|
||||
}
|
||||
|
||||
@ -931,7 +931,8 @@ openclaw googlemeet recover-tab https://meet.google.com/abc-defg-hij
|
||||
The equivalent tool action is `recover_current_tab`. It focuses and inspects an
|
||||
existing Meet tab on the configured Chrome node. It does not open a new tab or
|
||||
create a new session; it reports the current blocker, such as login, admission,
|
||||
permissions, or audio-choice state.
|
||||
permissions, or audio-choice state. The CLI command talks to the configured
|
||||
Gateway, so the Gateway must be running and the Chrome node must be connected.
|
||||
|
||||
### Twilio setup checks fail
|
||||
|
||||
|
||||
@ -122,8 +122,8 @@ await api.runtime.subagent.deleteSession({
|
||||
### `api.runtime.nodes`
|
||||
|
||||
List connected nodes and invoke a node-host command from Gateway-loaded plugin
|
||||
code. Use this when a plugin owns local work on a paired device, for example a
|
||||
browser or audio bridge on another Mac.
|
||||
code or from plugin CLI commands. Use this when a plugin owns local work on a
|
||||
paired device, for example a browser or audio bridge on another Mac.
|
||||
|
||||
```typescript
|
||||
const { nodes } = await api.runtime.nodes.list({ connected: true });
|
||||
@ -136,7 +136,9 @@ const result = await api.runtime.nodes.invoke({
|
||||
});
|
||||
```
|
||||
|
||||
This runtime is only available inside the Gateway. Node commands still go
|
||||
Inside the Gateway this runtime is in-process. In plugin CLI commands it calls
|
||||
the configured Gateway over RPC, so commands such as `openclaw googlemeet
|
||||
recover-tab` can inspect paired nodes from the terminal. Node commands still go
|
||||
through normal Gateway node pairing, command allowlists, and node-local command
|
||||
handling.
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user