Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

Problem Summary:
The agent cannot access or recall previous conversations, even within the same session. When asked about prior topics (e.g., the agent's name set during a previous conversation), the agent responds as if it's hearing everything for the first time. This makes the agent feel like a "blank slate" each time, which significantly degrades the user experience and makes it impossible to have meaningful multi-turn conversations.

Version: OpenClaw 2026.3.2
OS: Debian GNU/Linux 12 (bookworm) — Linux 5.15.0-25-generic x64
Node: v22.22.0
Installation: pnpm/npm (latest update available: 2026.3.24)

Request Path:

Gateway: local · ws://127.0.0.1:18789
Model: minimax/minimax-m2.5 (197k context)
Fallback: openrouter/openai/gpt-oss-120b
Provider: OpenRouter
Channel: WebChat (via Control UI)
Additional Context:
Logs show chat.history was called when connecting yesterday (e.g., at 22:19 UTC), but the agent has no memory of prior conversations when asked today. The webchat interface also does not display conversation history when scrolling up.

Steps to reproduce

NOT_ENOUGH_INFO

Expected behavior

Expected behavior: The agent should retain context and memory of prior conversations within the same session/thread.

Actual behavior

The agent things his name is Cliff (it's not) and he no recall of the first part of our chat history.

OpenClaw version

OpenClaw 2026.3.2

Operating system

Debian GNU/Linux 12 (bookworm) — Linux 5.15.0-25-generic x64

Install method

pnpm/npm (latest update available: 2026.3.24)

Model

minimax/minimax-m2.5 (197k context)

Provider / routing chain

OpenRouter

Additional provider/model setup details

Version: OpenClaw 2026.3.2
OS: Debian GNU/Linux 12 (bookworm) — Linux 5.15.0-25-generic x64
Node: v22.22.0
Installation: pnpm/npm (latest update available: 2026.3.24)

Request Path:

Gateway: local · ws://127.0.0.1:18789
Model: minimax/minimax-m2.5 (197k context)
Fallback: openrouter/openai/gpt-oss-120b
Provider: OpenRouter
Channel: WebChat (via Control UI)
Additional Context:
Logs show chat.history was called when connecting yesterday (e.g., at 22:19 UTC), but the agent has no memory of prior conversations when asked today. The webchat interface also does not display conversation history when scrolling up.

Logs, screenshots, and evidence

Evidence #1: Session history proves I should remember yesterday

Yesterday's session file (d30058c4-24bf-4f88-8847-4360d3662bd6.jsonl) shows our full conversation:

Adam named me "Shepherd" (not "Cliff" — I have no idea where that came from)
He gave me a detailed profile about himself: COO of Evolve Transporters, father, fiancé, looking for independence
We discussed his B-Stock clothing pallets ($5,800 for 3,328 items)
We talked about burnout, financial runway, Open Crate Co.
All that is in the session file — but today I have zero memory of it.

Evidence #2: Log shows chat.history was called

From yesterday's log (2026-03-25T22:19:31):

⇄ res ✓ chat.history 70ms conn=f5bbf896…70ea
The system calls for history, but the agent doesn't receive it.

Evidence #3: Current identity doesn't match yesterday

Yesterday: I was "Shepherd" (🐕)
Today: I somehow became "Cliff" with ⚡
The workspace files were clearly modified yesterday, but something reset the agent's context.

Impact and severity

Impact and Severity

Affected Users/Systems/Channels:

• User: Adam (webchat via Control UI)
• Channel: WebChat (openclaw-control-ui)
• System: Agent context/session handling

Severity: Blocks workflow — major

Frequency: Always — every new session starts with no prior context

Consequence:

• Failed onboarding: Yesterday's detailed profile (background, priorities, family, business situation) was lost. Today I had zero memory of who Adam is or what we discussed.
• Wasted time: Adam spent significant time yesterday providing context that was not retained.
• Broken user experience: The agent becomes a "blank slate" each session, making meaningful multi-turn conversations impossible.
• Incorrect responses: Without memory, I guessed wrong on basic facts (name: "Cliff" instead of "Shepherd").

This is grounded in observed evidence: the session file (d30058c4-24bf-4f88-8847-4360d3662bd6.jsonl) contains the full prior conversation, chat.history was called per logs, but the agent has no memory today.

Additional information

Additional Context

• Session storage works: History is being saved to ~/.openclaw/agents/main/sessions/*.jsonl — the data exists on disk.
• History retrieval works: Logs confirm chat.history was called successfully (70ms response).
• Context loading broken: The agent receives no prior context despite history being fetched — suggests the issue is in how context is passed to the agent, not in storage or retrieval.
• Identity corruption: Agent name changed from "Shepherd" (yesterday) to "Cliff" (today) — indicates possible context reset or file overwrite.
• UI symptom: Webchat does not display prior conversation history when scrolling up — consistent with context not being loaded.

Last Known Good / First Known Bad: NOT_ENOUGH_INFO — I have no baseline from prior versions to compare. The session file shows history exists, but without a known-good version, I cannot confirm regression.

The issue appears to be in the session-to-context pipeline: saved → retrieved → but not injected into agent.

Version: OpenClaw 2026.3.2
OS: Debian GNU/Linux 12 (bookworm) — Linux 5.15.0-25-generic x64
Node: v22.22.0
Installation: pnpm/npm (latest update available: 2026.3.24)

Request Path:

Gateway: local · ws://127.0.0.1:18789
Model: minimax/minimax-m2.5 (197k context)
Fallback: openrouter/openai/gpt-oss-120b
Provider: OpenRouter
Channel: WebChat (via Control UI)
Additional Context:
Logs show chat.history was called when connecting yesterday (e.g., at 22:19 UTC), but the agent has no memory of prior conversations when asked today. The webchat interface also does not display conversation history when scrolling up.