-
|
I have the Auto Claude just barely running and working, so I feel that there is likely something I have not done correctly. The issue I have is how long a fairly simple task takes to execute. E.g. I had Auto Claude create a script that pulls certain Git commits from a repo. The program crashed when executing a git command. I copy-pasted the error message, about 10-20 lines, and created a new task to fix the issue. I selected the "Quick Edit" with Haiku 4.5 and "low" thinking to complete the job. The process is now at 50% with 20 subtasks, and after 41 minutes of running. I have the Graphiti Memory enabled (just noticed that Ollama server was not running). Still, there must be something I'm doing wrong :) |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Dear, Jraanamo. The AC task system is "over-engineered". What i mean about this is that the stages from planning, coding, AI review are made so the task will try to "one-shot" the task description. This is why small & big tasks takes a long time, X-subtasks are made and in general people are "experiencing its slow", when in theory its doing what is engineered to do. My suggestion and i'll let u know my workflow for this is that i use AC tasks for bigger tasks. This can be re-factoring, new features or a 20 tasks i want to run over night while i sleep. Smaller issues, bugs, implementations i do either from local powershell or agent terminals inside AC. The agent terminals can create a worktree from the project and work within that one, so you get the power of AC with that and the terminal version of AC is pretty good! Everyone use AC differently, so you have to find the sweetspot for you and experiment with how you are working, how AC is working and adapting to it. |
Beta Was this translation helpful? Give feedback.
Dear, Jraanamo.
The AC task system is "over-engineered". What i mean about this is that the stages from planning, coding, AI review are made so the task will try to "one-shot" the task description. This is why small & big tasks takes a long time, X-subtasks are made and in general people are "experiencing its slow", when in theory its doing what is engineered to do.
My suggestion and i'll let u know my workflow for this is that i use AC tasks for bigger tasks. This can be re-factoring, new features or a 20 tasks i want to run over night while i sleep. Smaller issues, bugs, implementations i do either from local powershell or agent terminals inside AC. The agent terminals can create a work…