Failed to generate commit message: [resource_exhausted] Error
i keep this isse all the time disregards version upgrade with random breaks when its really working.
Also when this occasionally works the rules have set that it should follow the semantics of the branch name are not honored
Hey @Mati_Kepa, this one’s on our side. On teams where the admin restricts some models, Generate Commit Message is sent to a substitute model, and that route is failing on and off at the moment. It’s a known issue the team is aware of, and I’ve added your report to it.
For now, the most reliable option is to ask Agent in chat to write the commit message for your staged changes. Clicking the button again sometimes works, but it’s hit or miss right now.
On the branch name: the button only sees the staged diff, the last few commit messages in the repo, and a legacy .cursorrules file in the repo root. Rules in .cursor/rules and User Rules aren’t applied there, and the branch name isn’t sent, so that rule can’t take effect yet. Agent does follow your rules and can read the branch name. There’s an open feature request for this if you’d like to add your vote.