Hey, I think tutorial() has conflicting prompt instructions right now.
Steps to reproduce
- Use
99 and trigger tutorial()
- Give it a normal prompt that should produce a Markdown tutorial
- The request completes, but the tutorial window is empty
Expected behavior
tutorial() should write a Markdown tutorial to TEMP_FILE, and the opened tutorial window should show that content.
Actual behavior
Sometimes TEMP_FILE ends up empty, and tutorial() still opens a blank window.
Cause
tutorial() asks for a tutorial in Markdown, but 99 also reuses the generic temp-file rule that says things like:
Return only the code.
ONLY provide requested changes by writing the change to TEMP_FILE
|
never provide the requested changes as conversational output. Return only the code. |
That seems fine for visual/search-style code edits, but not for tutorials. A tutorial is not code, so the instructions conflict.
What fixed it for me
I patched my local config so that tutorial() uses a tutorial-specific temp-file rule instead, f.e.:
NEVER alter any file other than TEMP_FILE.
never provide the tutorial as conversational output.
ONLY provide the tutorial by writing valid Markdown to TEMP_FILE.
After that, tutorial() stopped opening empty windows on my machine.
Suggested fix
Use a tutorial-specific temp-file rule instead of the shared code-edit rule.
Thanks for this nice plugin.
Hey, I think
tutorial()has conflicting prompt instructions right now.Steps to reproduce
99and triggertutorial()Expected behavior
tutorial()should write a Markdown tutorial toTEMP_FILE, and the opened tutorial window should show that content.Actual behavior
Sometimes
TEMP_FILEends up empty, andtutorial()still opens a blank window.Cause
tutorial()asks for a tutorial in Markdown, but99also reuses the generic temp-file rule that says things like:Return only the code.ONLY provide requested changes by writing the change to TEMP_FILE99/lua/99/prompt-settings.lua
Line 114 in ec9872f
That seems fine for visual/search-style code edits, but not for tutorials. A tutorial is not code, so the instructions conflict.
What fixed it for me
I patched my local config so that
tutorial()uses a tutorial-specific temp-file rule instead, f.e.:After that, tutorial() stopped opening empty windows on my machine.
Suggested fix
Use a tutorial-specific temp-file rule instead of the shared code-edit rule.
Thanks for this nice plugin.