Area
src/everos
What happened?
The interactive everos demo flow should use the values entered by the user as the active demo story. In particular, the recall step should treat the user's second answer as the query and the demo should display that user-entered query back to the user.
Reported example:
EverOS demo Give it one memory, then ask for it back.
Give EverOS one thing to remember [I love climbing in Yosemite every spring.]: 我喜欢吃杨梅
Ask EverOS to recall it [Where do I like to climb?]: 我喜欢吃什么
In this flow, 我喜欢吃杨梅 is the memory the user wants EverOS to remember, and 我喜欢吃什么 is the recall query. The later demo UI/output should show the user's memory and query, not continue to present the hard-coded Yosemite/climbing default as the active content.
Expected behavior:
- The prompt asks the user what they want EverOS to remember.
- The prompt asks the user what they want EverOS to recall.
- The demo uses and displays the user's actual answers.
- For the example above, the displayed recall query should be
我喜欢吃什么, and the remembered content/result should be based on 我喜欢吃杨梅.
Actual behavior:
The demo still appears to surface the default Yosemite/climbing example in the user-facing flow, which makes it look like the hard-coded sample is being used instead of the user's query/content.
Steps to reproduce
- Run the interactive demo:
- At the memory prompt, enter:
- At the recall prompt, enter:
- Continue through the demo and observe whether the displayed query/content reflects the user-entered values or the default Yosemite/climbing sample.
Environment
OS: macOS
EverOS demo mode: interactive everos demo
Relevant files:
src/everos/entrypoints/cli/commands/demo.py
src/everos/entrypoints/tui/demo/data.py
Logs or screenshots
EverOS demo Give it one memory, then ask for it back.
Give EverOS one thing to remember [I love climbing in Yosemite every spring.]: 我喜欢吃杨梅
Ask EverOS to recall it [Where do I like to climb?]: 我喜欢吃什么
Area
src/everos
What happened?
The interactive
everos demoflow should use the values entered by the user as the active demo story. In particular, the recall step should treat the user's second answer as the query and the demo should display that user-entered query back to the user.Reported example:
In this flow,
我喜欢吃杨梅is the memory the user wants EverOS to remember, and我喜欢吃什么is the recall query. The later demo UI/output should show the user's memory and query, not continue to present the hard-coded Yosemite/climbing default as the active content.Expected behavior:
我喜欢吃什么, and the remembered content/result should be based on我喜欢吃杨梅.Actual behavior:
The demo still appears to surface the default Yosemite/climbing example in the user-facing flow, which makes it look like the hard-coded sample is being used instead of the user's query/content.
Steps to reproduce
Environment
OS: macOS
EverOS demo mode: interactive
everos demoRelevant files:
src/everos/entrypoints/cli/commands/demo.pysrc/everos/entrypoints/tui/demo/data.pyLogs or screenshots