When we get CTRL+C even from /hive command to solve command, we should be able to do soft or graceful interruption. For that we should pass some option to solve command, so when CTRL+C is received and that option is enabled, we carefully wait for solve command to complete as soon as AI agent stop working, we finish the working session, but don't wait for CI/CD, and show warning, that stopped by hive command. So we don't abruptly stop it and also provide nice user friendly comment (separate from working session finish + logs).
Here is the example how it worked at the moment:
xlabtg/teleton-agent-v2#204 (comment)
https://gist.githubusercontent.com/konard/3fe8e8d111486eb1665e951f03ec5ccd/raw/65dc7be3bc32702a6a7940614995b4b94a9f93db/solution-draft-log-pr-1782214688948.txt
May be we already have that logic, and it should enhanced in by default behavior. So we can later continue to work in the same repository by restarting /hive command.
We need to download all logs and data related about the issue to this repository, make sure we compile that data to ./docs/case-studies/issue-{id} folder, and use it to do deep case study analysis (also make sure to search online for additional facts and data), in which we will reconstruct timeline/sequence of events, list of each and all requirements from the issue, find root causes of the each problem, and propose possible solutions and solution plans for each requirement (we should also check known existing components/libraries, that solve similar problem or can help in solutions).
If there is not enough data to find actual root cause, add debug output and verbose mode if not present, that will allow us to find root cause on next iteration.
If issue related to any other repository/project, where we can report issues on GitHub, please do so. Each issue must contain reproducible examples, workarounds and suggestions for fix the issue in code. Also double check to fully apply requirements to entire codebase, so if we have issue in multiple places, it should be fixed in all them.
Please plan and execute everything in this single pull request, you have unlimited time and context, as context auto-compacts and you can continue indefinitely, until it is each and every requirement fully addressed, and everything is totally done.
When we get CTRL+C even from /hive command to solve command, we should be able to do soft or graceful interruption. For that we should pass some option to solve command, so when CTRL+C is received and that option is enabled, we carefully wait for solve command to complete as soon as AI agent stop working, we finish the working session, but don't wait for CI/CD, and show warning, that stopped by hive command. So we don't abruptly stop it and also provide nice user friendly comment (separate from working session finish + logs).
Here is the example how it worked at the moment:
xlabtg/teleton-agent-v2#204 (comment)
https://gist.githubusercontent.com/konard/3fe8e8d111486eb1665e951f03ec5ccd/raw/65dc7be3bc32702a6a7940614995b4b94a9f93db/solution-draft-log-pr-1782214688948.txt
May be we already have that logic, and it should enhanced in by default behavior. So we can later continue to work in the same repository by restarting /hive command.
We need to download all logs and data related about the issue to this repository, make sure we compile that data to
./docs/case-studies/issue-{id}folder, and use it to do deep case study analysis (also make sure to search online for additional facts and data), in which we will reconstruct timeline/sequence of events, list of each and all requirements from the issue, find root causes of the each problem, and propose possible solutions and solution plans for each requirement (we should also check known existing components/libraries, that solve similar problem or can help in solutions).If there is not enough data to find actual root cause, add debug output and verbose mode if not present, that will allow us to find root cause on next iteration.
If issue related to any other repository/project, where we can report issues on GitHub, please do so. Each issue must contain reproducible examples, workarounds and suggestions for fix the issue in code. Also double check to fully apply requirements to entire codebase, so if we have issue in multiple places, it should be fixed in all them.
Please plan and execute everything in this single pull request, you have unlimited time and context, as context auto-compacts and you can continue indefinitely, until it is each and every requirement fully addressed, and everything is totally done.