feat(flutter_runtime_mcp): include full logs in flutterStop response #33
+1
−18
Conversation
This file contains hidden or 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
When stopping a Flutter instance, the tool now returns all buffered stdout and stderr output from the session. This helps agents see what might have failed during build or runtime errors.
Simplify flutterStart success response to show only essential info (instance ID, working directory, command, VM Service URI). Full logs are only included when startup fails, helping agents debug issues without cluttering successful responses. Reverts the flutterStop changes from the previous commit as those were not intended.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When stopping a Flutter instance, the tool now returns all buffered
stdout and stderr output from the session. This helps agents see what
might have failed during build or runtime errors.