added tool build_get_logs_zip #193
Conversation
7c9d924 to
c923743
Compare
|
@raujaiswal we need to put together some prompts on how this would work. Ideally a video as well so people can follow along. My concern with adding this tool is that we don't have anyone else asking for it. And once the tool is out there, it is harder to take away. |
danhellem
left a comment
There was a problem hiding this comment.
We should also be adding and updating tests
|
Thanks for the contribution! In this case, though, I think the approach is too complex and introduces significant local side effects in the tool calls. The MCP server is intended to run reliably in any environment, but this solution would fail if VS Code isn't installed, among other potential issues. Maintaining this setup would likely be costly. It's better to keep things simple. If the goal is for the agent to analyze logs, we should equip it with MCP tools designed to get these logs (in parts) and provide tailored MCP prompts for this use case so they can be used effectively. |
🚀 What's New
🚀 Automated Build Failure Investigation
One-click workflow: Download → Extract → Analyze in a single command
Eliminates manual steps: No need to manually download, save, and extract ZIP files
Instant access: Build logs ready for investigation within seconds
MCP Tools Added
Build Tools
build_get_logs_zip- Enhanced build logs with ZIP extraction and VS Code integrationTool Description:
Downloads build logs as ZIP, extracts with nested archive support, creates analysis guide, and opens in VS Code for comprehensive build failure investigation.
GitHub issue number
Associated Risks
Replace by possible risks this pull request can bring you might have thought of
✅ PR Checklist
🧪 How did you test it?
Replace with use cases tested and models used