Messages in the claw.so web interface display in reverse chronological order, making conversations impossible to follow.
Reproduction Steps
- Open claw.so in browser
- Send a message from user → agent responds
- User sends another message (newer)
- Observe message ordering in UI
Expected Behavior
Messages should appear in chronological order (oldest at top, newest at bottom), like standard chat interfaces.
Actual Behavior
Newer messages appear ABOVE older messages in the conversation view.
Concrete example (2026-02-17 05:41 UTC):
- Agent sent message ending with "but that's a bigger project" at 05:35 UTC
- User sent a screenshot at 05:39 UTC (newer)
- In claw.so UI: User's screenshot (newer) appeared ABOVE agent's older message
- Result: conversation flow is backwards
Impact
- Cannot follow conversation flow - impossible to understand sequence of events
- Debugging is impossible - can't tell what happened first
- Makes claw.so unusable for real-time monitoring - the primary use case
Environment
- OpenClaw version: 2026.2.15
- Platform: Web UI (claw.so)
This affects ALL message types: user messages, agent responses, system messages, tool call results, and subagent outputs.
Messages in the claw.so web interface display in reverse chronological order, making conversations impossible to follow.
Reproduction Steps
Expected Behavior
Messages should appear in chronological order (oldest at top, newest at bottom), like standard chat interfaces.
Actual Behavior
Newer messages appear ABOVE older messages in the conversation view.
Concrete example (2026-02-17 05:41 UTC):
Impact
Environment
This affects ALL message types: user messages, agent responses, system messages, tool call results, and subagent outputs.