Best target repo
{"spark-intelligence-builder" => "runtime routing and provider roles"}
Page, command, module, or repo
Telegram commands: /remember, /recall, /about
What got confusing?
Memory or domain chips
What did you expect to happen?
I expected /about to reflect the latest or most relevant saved identity details consistently with /recall.
What actually happened?
After saving a new memory with /remember, the /recall command returned the correct latest memory ("BTC"), but the /about command still showed an older saved identity detail ("blue").
This created inconsistent memory/context behavior between /recall and /about.
Safe details
Tested on GitHub Codespaces with Spark Telegram bot connected. The issue appeared during normal use of /remember, /recall, and /about commands.
Suggested improvement or PR link
No response
Best target repo
{"spark-intelligence-builder" => "runtime routing and provider roles"}
Page, command, module, or repo
Telegram commands: /remember, /recall, /about
What got confusing?
Memory or domain chips
What did you expect to happen?
I expected /about to reflect the latest or most relevant saved identity details consistently with /recall.
What actually happened?
After saving a new memory with /remember, the /recall command returned the correct latest memory ("BTC"), but the /about command still showed an older saved identity detail ("blue").
This created inconsistent memory/context behavior between /recall and /about.
Safe details
Tested on GitHub Codespaces with Spark Telegram bot connected. The issue appeared during normal use of /remember, /recall, and /about commands.
Suggested improvement or PR link
No response