Skip to content

Tool execution output not visible when running CLI #328

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.

Sign up for GitHub

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

Jump to bottom
Closed
bhouston opened this issue Mar 18, 2025 · 2 comments · Fixed by #329
Closed

Tool execution output not visible when running CLI #328

bhouston opened this issue Mar 18, 2025 · 2 comments · Fixed by #329
Labels
released

Comments

@bhouston
Copy link
Member

Issue: Tool execution output not visible when running CLI

When running the MyCoder CLI with pnpm build && pnpm cli -i and providing a task, the tool execution output that used to be visible by default (showing log, warn, and error messages) is no longer displayed.

Steps to Reproduce

  1. Run pnpm build && pnpm cli -i
  2. Enter a task prompt like "What is the weather at my location? You can not ask me any questions, just try to figure it out on your own."
  3. Observe that there is no output showing tool execution or thoughts

Expected Behavior

The CLI should show log messages from each tool being executed, including the agent's thoughts and reasoning, by default.

Current Behavior

After providing a task, the CLI shows no output until the final result is returned.

Possible Causes

  • Changes to the default log level setting
  • Changes to how console output is handled in the logger implementation
  • Configuration issue with the logger listeners

Possible Solutions

  • Verify the default log level in the configuration
  • Check if the console output logger is properly registered
  • Ensure tool execution messages are being properly logged at the appropriate level
bhouston added a commit that referenced this issue Mar 18, 2025
@bhouston
fix: restore visibility of tool execution output
0809694 
The CLI was no longer showing tool execution output by default. This change:
1. Fixed the logger's emitMessages method to properly respect log level
2. Changed the default log level to 'log' in the configuration
3. Updated tool execution logs to use info level instead of log level

Fixes #328
@bhouston bhouston mentioned this issue Mar 18, 2025
Merged
github-actions bot pushed a commit that referenced this issue Mar 20, 2025
@semantic-release-bot
chore(release): 1.5.0 [skip ci]
98f7764 
# [mycoder-agent-v1.5.0](mycoder-agent-v1.4.2...mycoder-agent-v1.5.0) (2025-03-20)

### Bug Fixes

* improve resource trackers and fix tests ([c31546e](c31546e))
* properly format agentDone tool completion message ([8d19c41](8d19c41))
* resolve build and test issues ([549f0c7](549f0c7))
* resolve TypeError in interactive mode ([6e5e191](6e5e191))
* restore visibility of tool execution output ([0809694](0809694)), closes [#328](#328)
* shell message should reset output on each read ([670a10b](670a10b))
* update CLI cleanup to use ShellTracker instead of processStates ([3dca767](3dca767))

### Features

* add colored console output for agent logs ([5f38b2d](5f38b2d))
* Add interactive correction feature to CLI mode ([de2861f](de2861f)), closes [#326](#326)
* add parent-to-subagent communication in agentMessage tool ([3b11db1](3b11db1))
* add stdinContent parameter to shell commands ([5342a0f](5342a0f)), closes [#301](#301)
* implement ShellTracker to decouple from backgroundTools ([65378e3](65378e3))
* remove respawn capability, it wasn't being used anyhow. ([8e086b4](8e086b4))
@github-actions GitHub Actions
Copy link

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

The release is available on:

Your semantic-release bot 📦🚀

github-actions bot pushed a commit that referenced this issue Mar 20, 2025
@semantic-release-bot
chore(release): 1.5.0 [skip ci]
cbd6e5e 
# [mycoder-v1.5.0](mycoder-v1.4.1...mycoder-v1.5.0) (2025-03-20)

### Bug Fixes

* list default model correctly in logging ([5b67b58](5b67b58))
* restore visibility of tool execution output ([0809694](0809694)), closes [#328](#328)
* update CLI cleanup to use ShellTracker instead of processStates ([3dca767](3dca767))

### Features

* Add interactive correction feature to CLI mode ([de2861f](de2861f)), closes [#326](#326)
* add stdinContent parameter to shell commands ([5342a0f](5342a0f)), closes [#301](#301)
@github-actions GitHub Actions
Copy link

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

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
released
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix: Restore visibility of tool execution output drivecore/mycoder
1 participant
@bhouston