### Fixes

- Nodes/CLI: add `openclaw nodes remove --node <id|name|ip>` and `node.pair.remove` so stale gateway-owned node pairing records can be cleaned without hand-editing state files. Thanks @openclaw.

- Local models: default custom providers with only `baseUrl` to the Chat Completions adapter and trust loopback model requests automatically, so local OpenAI-compatible proxies receive `/v1/chat/completions` without timing out. Fixes #40024. Thanks @parachuteshe.

- Channels/message tool: surface Discord, Slack, and Mattermost `user:`/`channel:` target syntax in the shared message target schema and Discord ambiguity errors, so DM sends by numeric id stop burning retries before finding `user:<id>`. Fixes #72401. Thanks @garyd9, @hclsys, and @praveen9354.

- Agents/tools: scope tool-loop detection history to the active run when available, so scheduled heartbeat cycles no longer inherit stale repeated-call counts from previous runs. Fixes #40144. Thanks @mattbrown319.

### Notes

- The legacy `node.pair.*` API (CLI: `openclaw nodes pending|approve|reject|rename`) is a

- The legacy `node.pair.*` API (CLI: `openclaw nodes pending|approve|reject|remove|rename`) is a

separate gateway-owned pairing store. WS nodes still require device pairing.

- The pairing record is the durable source of truth for approved roles. Active

device tokens stay bounded to that approved role set; a stray token entry

openclaw nodes pending

openclaw nodes approve <requestId>

openclaw nodes reject <requestId>

openclaw nodes remove --node <id|name|ip>

openclaw nodes rename --node <id|name|ip> --name <displayName>

openclaw nodes status

openclaw nodes status --connected

`nodes list` prints pending/paired tables. Paired rows include the most recent connect age (Last Connect).

Use `--connected` to only show currently-connected nodes. Use `--last-connected <duration>` to

filter to nodes that connected within a duration (e.g. `24h`, `7d`).

Use `nodes remove --node <id|name|ip>` to delete a stale gateway-owned node pairing record.

Approval note:

openclaw nodes approve <requestId>

openclaw nodes reject <requestId>

openclaw nodes status

openclaw nodes remove --node <id|name|ip>

openclaw nodes rename --node <id|name|ip> --name "Living Room iPad"

```

- `node.pair.list` — list pending + paired nodes (`operator.pairing`).

- `node.pair.approve` — approve a pending request (issues token).

- `node.pair.reject` — reject a pending request.

- `node.pair.remove` — remove a stale paired node entry.

- `node.pair.verify` — verify `{ nodeId, token }`.

Notes:

</Accordion>

<Accordion title="Node pairing, invoke, and pending work">

- `node.pair.request`, `node.pair.list`, `node.pair.approve`, `node.pair.reject`, and `node.pair.verify` cover node pairing and bootstrap verification.

- `node.pair.request`, `node.pair.list`, `node.pair.approve`, `node.pair.reject`, `node.pair.remove`, and `node.pair.verify` cover node pairing and bootstrap verification.

- `node.list` and `node.describe` return known/connected node state.

- `node.rename` updates a paired node label.

- `node.invoke` forwards a command to a connected node.

- The device pairing record is the durable approved-role contract. Token

rotation stays inside that contract; it cannot upgrade a paired node into a

different role that pairing approval never granted.

- `node.pair.*` (CLI: `openclaw nodes pending/approve/reject/rename`) is a separate gateway-owned

- `node.pair.*` (CLI: `openclaw nodes pending/approve/reject/remove/rename`) is a separate gateway-owned

node pairing store; it does **not** gate the WS `connect` handshake.

- `openclaw nodes remove --node <id|name|ip>` deletes stale entries from that

separate gateway-owned node pairing store.

- Approval scope follows the pending request's declared commands:

- commandless request: `operator.pairing`

- non-exec node commands: `operator.pairing` + `operator.write`

}),

);

nodesCallOpts(

nodes

.command("remove")

.description("Remove a paired node entry")

.requiredOption("--node <idOrNameOrIp>", "Node id, name, or IP")

.action(async (opts: NodesRpcOpts) => {

await runNodesCommand("remove", async () => {

const nodeId = await resolveNodeId(opts, normalizeOptionalString(opts.node) ?? "");

if (!nodeId) {

defaultRuntime.error("--node required");

defaultRuntime.exit(1);

return;

}

const result = await callGatewayCli("node.pair.remove", opts, { nodeId });

if (opts.json) {

defaultRuntime.writeJson(result);

return;

}

const { warn } = getNodesTheme();

defaultRuntime.log(warn(`Removed paired node ${nodeId}`));

});

}),

);

nodesCallOpts(

nodes

.command("rename")

`\n${theme.heading("Examples:")}\n${formatHelpExamples([

["openclaw nodes status", "List known nodes with live status."],

["openclaw nodes pairing pending", "Show pending node pairing requests."],

["openclaw nodes remove --node <id|name|ip>", "Remove a stale paired node entry."],

[

'openclaw nodes invoke --node <id> --command system.which --params \'{"name":"uname"}\'',

"Invoke a node command directly.",

);

});

it("runs nodes remove and calls node.pair.remove", async () => {

callGateway.mockImplementation(async (...args: unknown[]) => {

const opts = (args[0] ?? {}) as { method?: string };

if (opts.method === "node.list") {

return {

nodes: [{ nodeId: "ios-node", displayName: "iOS Node", paired: true }],

};

}

if (opts.method === "node.pair.list") {

return {

pending: [],

paired: [{ nodeId: "ios-node", displayName: "iOS Node" }],

};

}

if (opts.method === "node.pair.remove") {

return { nodeId: "ios-node" };

}

return { ok: true };

});

await runProgram(["nodes", "remove", "--node", "iOS Node"]);

expect(callGateway).toHaveBeenCalledWith(

expect.objectContaining({

method: "node.pair.remove",

params: { nodeId: "ios-node" },

}),

);

});

it("runs nodes invoke and calls node.invoke", async () => {

mockGatewayWithIosNodeListAnd("node.invoke", {

ok: true,

"node.pair.request",

"node.pair.list",

"node.pair.reject",

"node.pair.remove",

"node.pair.verify",

"node.pair.approve",

"device.pair.list",