Spaces:

---

smolagents

/

ml-intern

like 387

Running on CPU Upgrade

Description

The ML Intern space occasionally reverts to a previous point in conversation history, showing an older message as the latest one with no visible error on screen. All messages sent after that checkpoint appear lost. When the agent is asked what it last remembers, it confirms the old message shown in the UI, meaning its context has rolled back too, not just the display.

I've experienced this more than once. Strangely, returning to the chat after a few days sometimes restores the missing messages, which makes the root cause harder to pin down.

Steps to reproduce

1. Have a long, ongoing conversation in the ML Intern space
2. Continue working (in my case, I was on v38 of a project)
3. The page refreshes (or is revisited)
4. The conversation appears reset to an earlier checkpoint and recent messages are gone, with the agent's context matching the old state

What I see in the browser console (DevTools)

Two errors appear that are likely related:

Failed to load resource: the server responded with a status of 404 ()
/api/session/a65b23f6-aa70-44de-95b7-4dc4716dc1f0/messages

Failed to persist backend messages: QuotaExceededError: Failed to execute 'setItem' on 'Storage': 
Setting the value of 'hf-agent-backend-messages' exceeded the quota.
    at Bb (index-CTDlGvua.js:248:61489)
    at Rf (index-CTDlGvua.js:248:61748)
    at index-CTDlGvua.js:304:3898

Analysis

The QuotaExceededError could suggest localStorage is being used to persist conversation history, and the storage limit is being hit as conversations grow long, but the devs will be able to better address this. I thought this was a foreseeable edge case for long sessions.

The 404 on the messages endpoint is a separate issue, likely a stale or expired session ID, but both failures appear to be silent, giving the user no feedback.

Expected behavior

• Users should be notified when conversation history is approaching storage limits, with a clear prompt to start a new conversation
• In either case, messages already sent should not be silently lost. At minimum, the user should know they were