Hard time getting it to create more complex tasks #96
Description
cc-sessions Version
v0.3.6
Installation Method
npm/npx (JavaScript)
Operating System
Linux (Ubuntu/Debian)
Shell/Terminal
Zsh
IDE/Environment
Terminal/CLI only
Bug Description
I have a hard time getting it to create tasks using the "mek:" key phrase.
I have asked the agent previously when it failed why it didn't follow it and it told me that it did get the trigger phrase and got the automated text but it got "lost" in all the other text which it focused more on. I even tried this time to tell it explicitly "New task" after the trigger phrase in hopes it would help it.
I just had the following happen:
> mek: New task, i have created the table structure with just hardcoded values in @backend/templates/latex/sections/summary.tex though the hardcoded values has to be replaced with Jinja2 so the correct values gets inserted automatically on generation. Now you should
reference the old apps template located at old_app/report/Punktfundament/template_terzaghi_punkt_mGK_detailed.docx you can use "doxx -help" as i have installed doxx to help you read word documents. Now the docuemnt is very large so ideally you should read from page 7
of 34 then continue from there. Now the context does not exactly match the old app you can see in my test context in @latex-dev/test_context.json how the new structure is. Remeber to keep the code clean and maintainble in the template file. I dont think we need
multiple tables like the word template does. You can refernece @backend/templates/latex/report.tex to see how i did it with others.
⎿ Read backend/templates/latex/sections/summary.tex (42 lines)
⎿ Read latex-dev/test_context.json (313 lines)
⎿ Read backend/templates/latex/report.tex (14 lines)
● I'll help you replace the hardcoded values in the summary table with Jinja2 template variables. Let me first explore the old Word template to understand the structure.
● Bash(doxx --help)
⎿ Beautiful .docx viewing in your terminal
Usage: doxx [OPTIONS] [FILE] [COMMAND]
… +73 lines (ctrl+o to expand)
● Bash(doxx old_app/report/Punktfundament/template_terzaghi_punkt_mGK_detailed.docx --export markdown -p 7 2>/dev/null | head -500)
⎿ # template_terzaghi_punkt_mGK_detailed
## Document Information
… +503 lines (ctrl+o to expand)
● Bash(doxx old_app/report/Punktfundament/template_terzaghi_punkt_mGK_detailed.docx --export markdown -p 7 2>/dev/null | tail -n +500 | head -300)
⎿ {%- endif %}
## Vandret bæreevne
… +297 lines (ctrl+o to expand)
⎿ Interrupted · What should Claude do instead?
> i wrote "mek:" why did you not create a task?
● You're right, I apologize. Let me follow the task creation protocol.
Steps to Reproduce
Give it just a bit complex task to create then it will just start trying to fix whatever you asked instead of creating a task. This has happend multiple times for me.
Expected Behavior
The agent creates a task based on the "mek:" trigger phrase.
Error Messages
Additional Context
No response