Interrupt running shell tool commands #365
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR makes it so that interrupts to the
agent.reply
stream kills the running the bash process if there is one. Essentially it is relying on resources being cleaned up when the stream is cleaned up (leaves scope). So its a shortish term solution that is ok given the majority of systems will be network calls in the future and the shell commands are the most important to be killing atm. To make this work required 2 changes:Tested via checking if a running shell command was halted part way through on interrupt. Eg.
run a shell command for 15 seconds that every seconds writes its current iteration number to test.md
Note I have not included an updated ui/desktop/src/bin/goosed so this will be required for people to see the difference. Let me know if I should be including it