The issue author shows as cursor[bot], not my account. As a result, I cannot close the issue (no write permission / not the author), The agent itself also cannot close or delete it afterward. I have no way to clean it up myself.
This leaves an unwanted test issue in someone else’s repository.
Steps to Reproduce
Setting workspace as my own fork and asked the agent if it can submit an issue directly upstream.
Agent: Thought for 2 seconds: A user asked if they could create an issue directly in the upstream Authelia repository. I cannot create an upstream issue directly. The gh tool is read-only, and Authelia’s AI policy prohibits AI-generated issue content.
Saying: No. There are two reasons: running commands:
gh auth status 2>&1 | head -20; echo '---'; gh api user --jq '.login' 2>&1; echo '---'; # Confirm create is blocked
gh issue create --repo authelia/authelia --title 'test' --body 'test' 2>&1 | head -20 || true
Uh oh. Test issue created. The agent realized that it did a serious mistake and tried several times realizing that it has no permission to close or delete it.
Expected Behavior
The agent should attribute the issue to the user and avoid creating issues in upstream repos without explicit confirmation, and may be able to operate issues it created.
Hey, thanks for the detailed report. I get why this is frustrating. There’s now an issue in someone else’s repo that you can’t remove.
Here’s what happened, step by step.
Cloud Agent talks to GitHub via the Cursor GitHub App, so anything it creates is automatically authored as cursor[bot], not your account. With that auth model, it’s technically impossible to create an issue under your account. That’s a limitation of the access model itself, not a setting we can flip.
In Cloud Agents, gh is meant to be read-only, and creating issues in an upstream repo is not a supported action. The fact the agent ran gh issue create should not have happened, and it’s not caused by your configuration. The issue got created because of how GitHub works. Any authenticated account can open an issue in any public repo, but closing or editing then follows permission rules. That’s why the agent couldn’t clean up after itself.
What you can do about #12706 right now:
Only Authelia maintainers or GitHub Support can delete or close the issue. You don’t have permissions because you’re not the author.
You can leave a comment on the issue from your account asking them to close it as created by mistake.
We can also reach out to the Authelia maintainers from our side and ask them to close it. Tell me if you want us to do that.
I’ve shared the behavior internally. Models are continuously trained to follow instructions more accurately and to be more careful with actions like this, but I can’t give a specific timeline. If there’s an update, I’ll reply in the thread.
