[Fix] Fast mode cannot explain GitHub Actions failures - #1438
Merged
Conversation
Contributor
daniel-lxs
marked this pull request as ready for review
August 28, 2026 22:49
daniel-lxs
requested review from
brunobergher,
daniel-lxs and
mrubens
as code owners
August 28, 2026 22:49
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What changed
actionstoolset to Fast mode's existing read-only GitHub proxy.actions_get,actions_list, andget_job_logs; mutating Actions tools remain unavailable.Why this change was made
Fast mode already uses the deployment GitHub App through a read-only MCP policy, but the policy filtered out Actions inspection tools. The existing GitHub App manifest already requests Actions access, so no permission UI, redirect flow, documentation, or prompt guidance is needed for this change.
Impact
Fast mode can inspect GitHub Actions runs, jobs, and logs without gaining workflow mutation capabilities. Targeted tests, type checks, changed-file lint and formatting checks, and the repository pre-push suite pass; the broader cloud-agents ESLint command still reports unrelated pre-existing warnings outside this diff.