-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/iss 198 sub process #90
base: main
Are you sure you want to change the base?
Conversation
@@ -134,3 +149,49 @@ export async function browse_url(args: { url: string }) { | |||
${md.replace(/\s+/g, '')} | |||
`; | |||
} | |||
|
|||
export async function check_process_status( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For now this check_process_status
function is unused, I'm thinking about keeping it or not since it can help the agent to retrieve the info faster 🤔
.split('\n') | ||
.find((line) => line.includes(`export UNIQUE_PROCESS_ID=${uniqueID}`)); | ||
if (!line) { | ||
throw new Error('Child process not found'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not sure we should throw an error, or simply return a shellProcess with a 'terminated' status, to inform that the process has been terminated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think for now I would rather have the CLI send an error in some edge cases, than having a silent error and having to dig the code to find why some shellprocesses would be terminated unexpectedly
must be tested |
🚀 Pull Request Overview
What does this PR do? 🤔
This PR allows an AI agent to start and check the status and logs of a background process.
For ex, you can start a docker build, and check the status a few minutes later, the agent will have all the info (Process ID, Logs etc.)
Related Issues 📝
💻 Changes Summary
sync
argument for the run_shell command. This way AI Agents less tend to create commands that run in the background by themselves. See Engine for more details..2501/logs
directory. This might be subject to change✅ Checklist
📈 Impact Analysis