Provide a loop option and loop termination condition setting for each mode.

[nokaka]

Provide a loop option and loop termination condition setting for each mode.

Problems that can be solved:

• Sometimes, In the early stages of the project, the AI-generated code contained numerous syntax and compilation errors. A single task could not completely fix these issues; multiple runs with the same task were required to achieve a complete fix.
• In the early stages of the project, the AI-generated code contained numerous syntax and compilation errors. A single task could not completely fix these issues; multiple runs with the same task were required to achieve a complete fix.
• Sometimes adding or modifying a shared component involves a large amount of code changes, which often cannot be completed in one go and requires multiple executions of the task message to complete.

Necessity:

• This implementation allows the same task to be executed continuously for 24 hours, significantly reducing the required time.
• Without this implementation, the task might need to be restarted every one or two hours, wasting nighttime hours.
• I had to keep the computer next to my head, and every time a notification sound came on, I had to get up and restart the task.

Suggestions for implementation

• Provide a loop option and loop termination condition setting for each mode, such as what effect was achieved, how many times it looped, how long it took, etc.