Long Running Prompts via Github do not trigger new commits. As you can see on the screenshot, there are no commits in between my message and cursor’s response.
Steps to Reproduce
Start a long running agent via the web dashboard. Then follow up with a github comment on the PR to update something
I took a look at those Request IDs. Both hit a known issue where the PR body generation step was timing out (exceeding a 60-second deadline). This is the step that runs after the agent finishes processing your follow-up.
The error rate was relatively high this week, but decreased significantly yesterday. Could you let me know if you’re still seeing this with new runs? If so, happy to dig in further with fresh request IDs.
Sorry for the delay! I looked into both of those runs. The background agent is instructed via its system prompt to commit and push, but it looks like you have a rule in your .cursor/rules/ that says “Do not commit anything on your own” which is overriding the push behavior. The agent sees conflicting instructions and follows your rule.
If you remove or update that rule, the agent should commit and push as expected. You could also add a rule specifically telling the agent to always push after completing work.
