broken view tools call native vs normal brovser view

[danilovmy]

sometimes agent calls tools and tell me about it. But i see - in native chat view the tools call is not same as in browser chat view.

Native

Browser:

It is not a big bug, but i see the difference.

Version: windows 10

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed August 8, 2026, 11:36 PM ET / August 9, 2026, 03:36 UTC.

Summary
Keep open. Current main fixes live native tool identity and event correlation, but the directly related open PR still targets native history-cache correlation, a plausible remaining path for the intermittent mismatch.

Reproducibility: unclear. Current source and the prepared UI proof show the live identity path is fixed, but the report does not isolate whether its intermittent case is the remaining history-cache path.

Ways to help us reproduce this

• Add a screenshot or short recording showing the behavior.
• Add expected vs actual behavior.

Next step
Do not start another repair: the directly related open PR already owns the bounded remaining history-cache path.

Review details

Best possible solution:

Rebase and complete the focused history-cache correlation follow-up, then verify native history reload preserves the same concrete tool rows and safe details as browser activity.

Do we have a high-confidence way to reproduce the issue?

Unclear. Current source and the prepared UI proof show the live identity path is fixed, but the report does not isolate whether its intermittent case is the remaining history-cache path.

Is this the best way to solve the issue?

Yes, conditionally. The merged reducer and projection work addresses the reported live path, while the narrow open history-cache follow-up is the appropriate remaining route rather than a parallel repair.

AGENTS.md: found and applied where relevant.

Remaining risk / open question:

• The linked follow-up is still a draft and its collision-specific visible proof is not yet shown from a current-main-based head.

Codex review notes: model internal, reasoning high; reviewed against 4712e227d110.

Label changes

Label changes:

• add issue-rating: 🦐 gold shrimp: Current issue advisory state selects this label.
• add clawsweeper:needs-info: Current issue advisory state selects this label.
• remove issue-rating: 🦞 diamond lobster: Current issue advisory state no longer selects this label.
• remove clawsweeper:source-repro: Current issue advisory state no longer selects this label.

Label justifications:

• P2: The report describes a bounded but visible native-chat consistency defect.
• impact:ux-friction: Inconsistent tool-call detail between chat surfaces causes confusion without blocking chat use.

Evidence reviewed

What I checked:

• Current live-event mapping: Current main maps tool, command, and patch item frames into correlated native tool presentation events, retaining canonical identity and allowlisted display arguments. (src/OpenClaw.Tray.WinUI/Chat/OpenClawChatDataProvider.cs:4674, 4712e227d110)
• Current reducer coverage: The reducer test confirms a late generic parent retains the stronger Bash child identity, both safe arguments, output, and successful terminal state. (tests/OpenClaw.Tray.Tests/ChatTimelineReducerTests.cs:823, 4712e227d110)
• Merged-fix provenance: The current implementation includes merged commit a1d933a, dated 2026-08-07T12:05:13-07:00, which corrected native tool event correlation. (src/OpenClaw.Tray.WinUI/Chat/OpenClawChatDataProvider.cs:4758, a1d933a3c7b7)
• Release boundary: The merged correlation fix is on origin/main but no local release tag contains it; latest supplied release v0.6.12 points to 4166e0f, which predates the fix. (a1d933a3c7b7)
• Remaining candidate: The supplied GitHub context identifies open PR fix(chat): preserve history cache correlation #1130 as related work for history-cache correlation and synthetic history identities, which current main does not contain. (e1be9dfe1406)

Likely related people:

• bkudiess: Authored the two merged native-tool identity and correlation fixes and the directly related open history-cache follow-up. (role: feature owner and recent area contributor; confidence: high; commits: ad472243bcb8, a1d933a3c7b7; files: src/OpenClaw.Tray.WinUI/Chat/NativeToolProjector.cs, src/OpenClaw.Tray.WinUI/Chat/OpenClawChatDataProvider.cs, src/OpenClaw.Chat/ChatTimelineReducer.cs)
• Caleb Eden: Recent history shows a compact and inspectable tool-activity change immediately adjacent to the merged identity work. (role: recent adjacent chat UI contributor; confidence: medium; commits: aac07abb1fbd; files: src/OpenClaw.Tray.WinUI/Chat/OpenClawChatDataProvider.cs)

How this review workflow works

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.