Sometimes mycoder will quit (and even give a performance summary), but not return to shell

[bhouston]

This means it is stuck waiting for a promise or something similar.

I just had this happen:

...
🤖 ```bash
🤖 cd mycoder-docs
🤖 yarn
🤖 yarn start
🤖 ```
🤖 
🤖 This will launch the development server at http://localhost:3000/

📊 Performance Profile Results
=======================
Label                                         Time  Duration
Module initialization                       0.01ms    0.01ms
After imports                               0.01ms    0.00ms
Before sourceMapSupport install             0.01ms    0.00ms
After sourceMapSupport install              0.06ms    0.05ms
Main function start                         0.09ms    0.03ms
After dotenv config                         0.20ms    0.11ms
After Sentry init                          27.53ms   27.33ms
Before package.json load                   27.53ms    0.00ms
After package.json load                    27.84ms    0.31ms
Before yargs setup                         27.84ms    0.00ms
After yargs setup                       1233053.39ms1233025.55ms
Total startup time: 1233053.39ms
=======================


^C%  <--- here I hit control-C to kill it.      

[bhouston]

/mycoder can you have a look at the logic in the cli to see what could be causing this? If it is challenging to determine the unresolved promise by looking at the code, is there some type of debugging strategy or npm library we can integrate in order to help debug this?

[github-actions]

This issue has been fixed in commit d33e729 with the implementation of a resource cleanup utility. The fix includes:

1. A cleanup utility that ensures all browser sessions and shell processes are terminated before exit
2. A force exit failsafe that ensures the process will exit even if there are lingering handles
3. Integration with the main CLI code to run cleanup operations before exit

The fix addresses the root cause by:

• Properly closing browser sessions
• Terminating any running shell processes
• Adding a force exit mechanism as a failsafe

This should resolve the issue where the CLI hangs and doesn't return to the shell even after showing a performance summary.

[github-actions]

Closing as fixed in commit d33e729

[github-actions]

@bhouston I've investigated the CLI hanging issue and found that it has already been fixed in commit d33e729 with the implementation of a resource cleanup utility.

The fix addresses the issue by:

1. Properly closing browser sessions when the CLI exits
2. Terminating any running shell processes
3. Adding a force exit mechanism as a failsafe to ensure the process terminates even if there are lingering handles

The implementation includes:

• A cleanup utility in packages/cli/src/utils/cleanup.ts to handle resource cleanup
• Integration with the main CLI code to run cleanup operations before exit
• A force exit failsafe that ensures the process will exit even if there are lingering handles

I've closed issue #141 as it appears to be resolved. If you continue to experience this issue after updating to the latest version, please let us know and we can investigate further.

[github-actions]

🎉 This issue has been resolved in version mycoder-agent-v1.1.0 🎉

The release is available on:

• pnpm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This issue has been resolved in version mycoder-v1.1.0 🎉

The release is available on:

• pnpm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀