What Happened
- Computer Use Agents recorded a source-backed change that affects how this topic should be watched.
- Computer Use Agents has a new source-backed event attached to this signal.
- 1 evidence item attached for review.
CodeTracked since May 19, 2026
OpenClaw plugin now displays readable agent names in Clawd HUD
A source-backed change was recorded for Computer Use Agents. Review the evidence and decide whether it deserves continued tracking.
openclaw-pluginClawd Dashboardsession_titlesessionKey
What is Different
Before
Scattered source updates, isolated context, and manual follow-up across multiple feeds.
Now
Added explicit session title reporting for HUD: `buildPayload` now injects `session_title` extracted from `sessionKey`, then resolves display names via a cached lookup of `~/.openclaw/openclaw.json` `agents.list[]` using `identity.name` → `name` → `id`, with emoji prefix formatting and safe fallback when parsing or mapping fails.
Why Track This
Why It Matters
Operators can now tell which OpenClaw agent a session belongs to at a glance in the HUD, so concurrent agents with similar working directories are less likely to be confused and actions are less likely to target the wrong session. Technically, the change adds `session_title` to payload generation and a local config-backed name resolver with mtime-based cache, while preserving existing fallback (`raw id` or empty field) behavior for missing/invalid configs. Watch for stale-name behavior after live edits to `openclaw.json` in long-running processes and whether existing manual alias precedence still matches operator workflows.
Impact
Operators can now tell which OpenClaw agent a session belongs to at a glance in the HUD, so concurrent agents with similar working directories are less likely to be confused and actions are less likely to target the wrong session. Technically, the change adds `session_title` to payload generation and a local config-backed name resolver with mtime-based cache, while preserving existing fallback (`raw id` or empty field) behavior for missing/invalid configs. Watch for stale-name behavior after live edits to `openclaw.json` in long-running processes and whether existing manual alias precedence still matches operator workflows.
What To Watch Next
- Watch whether openclaw-plugin becomes a repeated pattern.
- Track follow-up changes around Computer Use Agents.
- Compare future signals against this evidence trail.
- Re-check risk flags: openclaw_json_schema_drift, agent_name_cache_staleness.