Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix [Feature]: Show node name in exec tool call transparency message [3 pull requests, 1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#77719•Fetched 2026-05-06 06:22:29
View on GitHub
Comments
1
Participants
2
Timeline
8
Reactions
2
Author
civiltoxciviltox
Participants
civiltoxciviltoxclawsweeper[bot]clawsweeper[bot]
Timeline (top)
cross-referenced ×3referenced ×3commented ×1renamed ×1

Fix Action

Fixed

PR fix notes

PR #77743: feat(tool-display): show node name in exec tool call transparency message

Description (problem / solution / changelog)

What

Adds node name to exec tool transparency messages when a command runs on a remote or paired node.

Before: 🛠 Exec: docker pull pihole/pihole:latest

After: 🛠 Exec (raspberrypi): docker pull pihole/pihole:latest

Why

  • Essential for users with multiple nodes (Raspberry Pi, servers, etc.)
  • Removes ambiguity about where the command actually executed

Changes

  • Updated resolveExecDetail() in src/agents/tool-display-exec.ts
  • Added node/nodeId to exec detailKeys in config
  • Added regression tests
  • Updated tool display snapshot
  • Formatted with oxfmt

Closes #77719

Changed files

  • apps/shared/OpenClawKit/Sources/OpenClawKit/Resources/tool-display.json (modified, +5/-1)
  • src/agents/bash-tools.exec-runtime.ts (modified, +120/-42)
  • src/agents/tool-display-config.ts (modified, +1/-1)
  • src/agents/tool-display-exec.ts (modified, +16/-2)
  • src/agents/tool-display.test.ts (modified, +32/-0)
  • src/infra/heartbeat-runner.ts (modified, +23/-117)
  • src/security/dm-policy-shared.ts (modified, +20/-0)

PR #77796: feat(tool-display): show node name in exec tool transparency message

Description (problem / solution / changelog)

What

Adds node name to exec tool transparency messages when a command runs on a remote/paired node.

Before: 🛠 Exec: docker pull pihole/pihole:latest

After: 🛠 Exec (raspberrypi): docker pull pihole/pihole:latest

Why

  • Very useful for users with multiple nodes (Raspberry Pi, remote servers, etc.)
  • Makes it clear where the command actually executed

Closes #77719

Changed files

  • apps/shared/OpenClawKit/Sources/OpenClawKit/Resources/tool-display.json (modified, +5/-1)
  • src/agents/tool-display-config.ts (modified, +1/-1)
  • src/agents/tool-display-exec.ts (modified, +16/-2)
  • src/agents/tool-display.test.ts (modified, +32/-0)

PR #78288: Agents/exec: show target node name in exec tool transparency messages

Description (problem / solution / changelog)

Summary

When the exec tool runs on a remote node (host=node, node=<name>), the tool-call transparency message currently shows only the command — there's no indication of which node the command ran on. This makes it hard to tell whether a command executed locally on the gateway or remotely on a paired device (e.g. a Raspberry Pi).

This PR surfaces the node parameter in the exec detail string:

Before:

🛠️ Exec: docker pull pihole/pihole:latest

After:

🛠️ Exec: docker pull pihole/pihole:latest, node: raspberrypi

The node label is appended only when the node parameter is a non-empty string. It composes naturally with the existing workdir/cwd context suffix and raw-command appendix patterns.

Fixes #77719

Changes

  • src/agents/tool-display-exec.ts: Extract node from args in resolveExecDetail(); append · node: <name> fragment (becomes , node: <name> after formatToolDetailText normalization).
  • src/agents/tool-display.test.ts: Three new cases — node-only, node+cwd for a known command, and absent-node (no label).
  • CHANGELOG.md: Entry under ### Fixes in the Unreleased block.

Test plan

  • pnpm test src/agents/tool-display.test.ts — all 23 tests pass (3 new)
  • pnpm check — 0 lint warnings, 0 type errors

🤖 Generated with Claude Code

Changed files

  • CHANGELOG.md (modified, +1/-0)
  • src/agents/tool-display-exec.ts (modified, +9/-3)
  • src/agents/tool-display.test.ts (modified, +43/-0)

Code Example

exec:{emoji:"🛠️",title:"Exec",detailKeys:["command"]}
RAW_BUFFERClick to expand / collapse

Feature Request

Problem

When the exec tool runs on a remote node (e.g. host=node, node=raspberrypi), the tool call transparency message shown to the user in chat only displays the command:

🛠 Exec: run docker pull pihole/pihole:latest

There is no indication of which node the command ran on. This makes it hard to tell whether a command executed locally on the gateway or remotely on a paired node.

Currently the exec tool display spec only includes command in its detailKeys:

exec:{emoji:"🛠️",title:"Exec",detailKeys:["command"]}

The node parameter is not surfaced.

Proposal

Add node to the exec tool display detail keys so that when a command runs on a node, the transparency message shows it:

🛠 Exec (raspberrypi): run docker pull pihole/pihole:latest

or equivalently as a detail line:

🛠 Exec: run docker pull pihole/pihole:latest · node: raspberrypi

The host parameter could also be shown but the user who requested this feels node is the most important one, since host is usually implied (auto → gateway).

Why

  • Users with paired nodes (Raspberry Pi, remote servers, etc.) need to know at a glance where a command ran
  • The information is already in the tool call args — it just needs to be surfaced in the display
  • Prevents confusion when commands like docker ps return different results depending on which host they ran on

Issue submitted by civil's clanker

extent analysis

TL;DR

Add the node parameter to the exec tool display detail keys to include the node information in the transparency message.

Guidance

  • Modify the exec display spec to include node in its detailKeys: exec:{emoji:"🛠️",title:"Exec",detailKeys:["command", "node"]}
  • Update the display logic to handle the new node detail key and format the transparency message accordingly
  • Consider adding a conditional check to only display the node information when the command is run on a remote node
  • Verify the change by running the exec tool on a remote node and checking the transparency message in the chat

Example

exec:{emoji:"🛠️",title:"Exec",detailKeys:["command", "node"]}
// Example transparency message:
// 🛠 Exec (raspberrypi): run docker pull pihole/pihole:latest

Notes

This solution assumes that the node parameter is already available in the tool call args and can be accessed in the display logic.

Recommendation

Apply workaround: Add the node parameter to the exec tool display detail keys, as this is a straightforward solution that addresses the user's request and provides the necessary information in the transparency message.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#request error#file not found#serialization error#model compatibility#GPU setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - ✅(Solved) Fix [Feature]: Show node name in exec tool call transparency message [3 pull requests, 1 comments, 2 participants]