rob
60957ae4af
The driver interpreted each utterance in isolation (schemas + scene + utterance only), so when WoodShop asked a clarifying question and the user replied "yes", the next turn had no record of what was proposed and fell back to "not sure what you'd like me to do". - driver.interpret/handle now accept a rolling (utterance, reply) history; SYSTEM prompt gains a "Recent conversation" section instructing the model to execute the previously-proposed calls on affirmation. - CLI main() keeps a history list across the loop. - GUI Controller keeps a bounded self._history and threads it through run_command, appending each turn. - tests: history render/window, prompt inclusion, handle + controller append. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| test_bom_window.py | ||
| test_cutlist.py | ||
| test_cutplan.py | ||
| test_driver.py | ||
| test_geometry.py | ||
| test_gui_controller.py | ||
| test_instructions.py | ||
| test_jigs.py | ||
| test_layout.py | ||
| test_scene.py | ||