Background Agent sets commit time to the past

Support Bug Reports
1

Describe the Bug

We’re seeing commits on GitHub PRs have a timestamp 1 hour earlier than when the commit was synced to GitHub. For instance, if we add a comment on the PR at 1:00, the agent responds to the comment at 1:10, the commit timestamp is 12:10. That effectively places the response to feedback before the comment initiating the commit in the GitHub timeline.

Steps to Reproduce

  • Queue background agent
  • Add @cursor comment on the PR
  • Wait(?) for time travel

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Background Agent w/ GPT-5

Does this stop you from using Cursor

No - Cursor works, but with this issue

2

hi @neals could you share more so we can look more detailed into the cause?

  • Please post the Background Agent Request ID.
  • What is your local machine timezone?
  • Does this occur only when running @cursor command in GitHub?
3

@condor Here is a request ID of an instance of this today: bc-8047ef30-fc07-4552-beed-885b60a33779

The last commit on that background agent was timestamped at 8:53 MDT today August 19th, though the feedback that prompted that commit was at 9:03 AM, and it responded with the written follow up at 9:28 AM, so it may not be related to timezones. Is it possible the agent is hallucinating the timestamp in the commit / request to GitHub?

My local machine timezone is US Mountain, though I’ve only seen this by using @cursor in a GitHub comment. It’s possible responding with feedback in Linear has had the same effect but I don’t have examples similar to using GitHub.

4

I have sent it to our team to investigate.

Commit time is not submitted but automatic. If the time is in a comment text it would be different.

1 Like
5

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.

6

This issue is resolved with new clock updates.

1 Like