openclaw - 💡(How to fix) Fix UI/UX: Distinguish “New session” from “Reset context” [1 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#60832Fetched 2026-04-08 02:46:39
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Participants
Timeline (top)
labeled ×1

UI/UX: Distinguish “New session” from “Reset context”:

  • When I used the “new session” ("+" on the composer/ prompt box) from the control UI on April 4, 2026, I expected a second session entry to appear in the Sessions tab.
  • Instead, the existing session appeared to continue as a single session record while the agent’s active context had been reset.
  • This is confusing because “new session” implies a new conversation container/ history entry rather than a deletion of context already created; whereas “reset context” would more correctly imply clearing the working memory/ chat context within the current session.

Recommendation:

  • Change the description for "+" on chat dash from "New session" to "Reset context " so that it is more clear from the user perspective.
  • The UI should make this distinction explicit so users understand whether they are creating a separate session or wiping context in place.

Root Cause

UI/UX: Distinguish “New session” from “Reset context”:

  • When I used the “new session” ("+" on the composer/ prompt box) from the control UI on April 4, 2026, I expected a second session entry to appear in the Sessions tab.
  • Instead, the existing session appeared to continue as a single session record while the agent’s active context had been reset.
  • This is confusing because “new session” implies a new conversation container/ history entry rather than a deletion of context already created; whereas “reset context” would more correctly imply clearing the working memory/ chat context within the current session.
RAW_BUFFERClick to expand / collapse

Summary

UI/UX: Distinguish “New session” from “Reset context”:

  • When I used the “new session” ("+" on the composer/ prompt box) from the control UI on April 4, 2026, I expected a second session entry to appear in the Sessions tab.
  • Instead, the existing session appeared to continue as a single session record while the agent’s active context had been reset.
  • This is confusing because “new session” implies a new conversation container/ history entry rather than a deletion of context already created; whereas “reset context” would more correctly imply clearing the working memory/ chat context within the current session.

Recommendation:

  • Change the description for "+" on chat dash from "New session" to "Reset context " so that it is more clear from the user perspective.
  • The UI should make this distinction explicit so users understand whether they are creating a separate session or wiping context in place.

Problem to solve

The UI definition for "+" on the composer/ prompt box is confusing from a user perspective because “New session” implies a new conversation container/ history entry rather than a deletion of context already created; whereas “Reset context” would more correctly imply clearing the working memory/ chat context within the current session.

Proposed solution

  • Change the description for "+" on chat dash from "New session" to "Reset context " so that it is more clear from the user perspective.
  • The UI should make this distinction explicit so users understand whether they are creating a separate session or wiping context in place.

Alternatives considered

None.

Impact

Affected: User experience Severity: Low Frequency: The issue is consistent but you probably remember how it functions after the first occurrence. Consequence: Confusing to new users.

Evidence/examples

<img width="1607" height="214" alt="Image" src="https://github.com/user-attachments/assets/5ce22fec-e450-4a6c-864a-4e73dac736c0" />

Additional information

This is not critical, it's just a simple recommendation based on our observations.

extent analysis

TL;DR

Update the description for the "+" button on the chat dashboard from "New session" to "Reset context" to clarify its functionality for users.

Guidance

  • Review the current UI implementation for the "+" button to understand how it interacts with session management and context reset.
  • Consider adding a tooltip or brief description to the "+" button to provide immediate clarity on its function, in addition to updating the button's text.
  • Evaluate the Sessions tab's behavior when the "+" button is used, to ensure it aligns with the updated description and user expectations.
  • Test the updated UI with new users to verify that the change improves the user experience and reduces confusion.

Example

No code snippet is provided as the issue focuses on UI labeling and user experience rather than code implementation.

Notes

The proposed solution is straightforward and targets the user experience. However, it's essential to consider any potential downstream effects on user behavior or expectations, especially if the current functionality has been in place for some time.

Recommendation

Apply the workaround by updating the button's description to "Reset context" as this directly addresses the confusion identified and improves the user interface's clarity without requiring significant changes to the underlying functionality.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING