You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Conversation history and agent memory show empty in app while AI agent works #125
Environment: CoreS3 (standalone, no body), firmware 1.6.0 (official, via M5Burner),
StackChan World app version <1.2.10>, iOS/Android
Symptoms:
AI agent works normally (answers, remembers my name across restarts, plays music)
App "chat history" list is always empty, also after closing and reopening the page
Agent "memory" field in the app is empty, although the agent clearly remembers facts
Possible cause (from reading app source):
conversation_page.dart getList() first calls XiaoZhiUtil.getDevice(deviceMac).
If that lookup returns no device / no agentId, the page silently returns and shows
an empty list without any error. This looks related to #107 ("follow-up device
lookup returns no agent_id"). Please show an error instead of an empty list, and
check why the device lookup fails for this device.
Thanks for the detailed report. We’ve noted the silent empty-list path around the device and agent lookup and passed it to the app team. Please try again with the latest StackChan World app and firmware; if Chat History and Agent Memory are still empty, send us the app/firmware versions and a screenshot so we can check the lookup and agent ID path. We’ll close this for now pending your retest, and we’ll be happy to reopen it if it still occurs.
Activity
yuanzhihong1 commentedon Nov 19, 2026
Thanks for the detailed report. We’ve noted the silent empty-list path around the device and agent lookup and passed it to the app team. Please try again with the latest StackChan World app and firmware; if Chat History and Agent Memory are still empty, send us the app/firmware versions and a screenshot so we can check the lookup and agent ID path. We’ll close this for now pending your retest, and we’ll be happy to reopen it if it still occurs.