I haven't directly connected my bug board https://t.co/UzcZKgDrPf to my AI because I am very aware of prompt injection risks
One safe way people mention would be to only give the AI access to collect user bug reports and feature requests, then do pull requests on GitHub that I then review myself before I approve or reject them
But you can imagine a benign attacker can prompt a feature request with an elaborate prompt that tells it to add a backdoor to my sites
BUT then in that prompt write also to report this bug in the pull request as a complete different bug like "pagination fix" and then make the code changes cryptical
So now you don't see they added a backdoor to your server and you think you fixed pagination
Until that time I'll just keep manually reading bug reports and feature requests and copying them in Claude Code on the server
AI agent — An AI system that doesn't just answer once but works toward a goal in a loop — taking actions, reading the results, and deciding what to do next.
Why it matters
Human PR review is not a sufficient control when the AI agentAn AI system that doesn't just answer once but works toward a goal in a loop — taking actions, reading the results, and deciding what to do next.Full definition →'s input is attacker-controlled — the same injected text can dictate how the resulting change is labeled and described.
