forked from ErikBjare/gptme
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add issue ErikBjare#348 details to Current Understanding
- Loading branch information
Jamesb
committed
Dec 19, 2024
1 parent
e0807b6
commit 64fecfa
Showing
1 changed file
with
8 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,8 +1,10 @@ | ||
# Current Understanding | ||
## Issue Overview | ||
- Issue #348: Add a way for agents to monitor and optionally interrupt long-running commands | ||
- The problem involves debugging commands that may hang | ||
- An autonomous agent needs to monitor and potentially interrupt these commands | ||
- After running a shell command, the system should provide updates every 10 seconds | ||
- Updates should include context about the command's status and ask if it should be terminated | ||
## Issue #348: Add a way for agents to monitor and optionally interrupt long-running commands | ||
|
||
- The issue is about implementing a mechanism for agents to monitor and potentially interrupt long-running shell commands. | ||
- This is particularly important for debugging commands that might hang. | ||
- The proposed solution involves adding a message to the conversation log every 10 seconds, providing: | ||
- Context about what the command is doing | ||
- Whether the command is still running | ||
- An option to kill the command | ||
# Questions to Investigate |