The agent records every commit a developer makes on their own machine, including the ones that are later squashed, rebased or never pushed at all. You see how work really moves, not only what lands in the shared branch.
Git Activity · Local commits
Remote commits from GitHub, GitLab or Bitbucket are matched to the local commits behind them. Each one shows how many local commits it contains and how long the work took from the first local commit to the merge.
Git Activity · Remote commits
Merge PR #418: retries for failed card payments
a91c3f2payments-api · main+611 −40
Built from 5 local commits
Each commit, local or remote, gets a short AI summary of what changed and why. It is linked to the ticket, prompts and sessions behind it, so you can see what each commit contributed to the request it belongs to.
Commit 5c81e07
feat(PAY-471): add idempotency keys to charge requests
by Priya
Adds an idempotency key to every charge request, built from the invoice and attempt number, so a retried payment can never bill a customer twice. Covers the case where the bank times out after accepting the charge.
PAY-471: Retry failed card payments safely
Covers 2 of 3 acceptance criteria
Files changed
Here is how one change on payments-api moved from a ticket to production. Local commits show the two days of work that a pull request alone would hide.
PAY-471 moved to In progress.
Retry schedule for soft declines, written in an AI session.
Five local commits pushed as one branch.
PR #418 reviewed and merged to main.
Released to production.
Lead time for this change: 2 days 7 hours from the first local commit, not five and a half hours from the pull request.
Collected by the agent
Local commits come from the same agent that captures prompts, with no webhooks, repo setup or branch rules to change.
Linked end to end
Every commit is tied to its ticket, the AI sessions behind it and the remote commit it ended up in.
Real timestamps
Work is timed from the first local commit, so lead time includes the coding that pull request tools never see.
Diffs kept short-term
Diffs are stored for 5 days. Commit metadata and AI summaries are kept, so history stays useful without holding your code.
How local and remote commits are tracked and summarized.
Local commits are made on a developer machine, before anything is pushed. Remote commits are the ones that reach GitHub, GitLab or Bitbucket. CloudByte AI tracks both and matches them, so you see the full path from the first commit to the merge.
Because most of the work happens there. Commits are often squashed or rebased before they are pushed, so tools that only read the remote miss how long the work took and how it progressed. Local commits give the real start time for lead time.
No. Local commits are collected by the agent already installed for prompt capture. Remote commits come from your Git provider, connected once from the dashboard.
Two or three plain sentences about what the commit changed and why, plus the ticket it belongs to, the AI sessions and prompts behind it, and what it contributed to that ticket.
Diffs are stored for 5 days so summaries can be written and reviewed. After that only commit metadata and the AI summary are kept.
Matching local commits to remote commits gives the true start of each change, so lead time for changes is measured from the first local commit instead of from when a pull request was opened. See the DORA Metrics page for the full picture.
Install the agent once per laptop and local commits start showing up with their AI summaries within minutes.
