Coding Report: Hours, Commits, and Cursor in One View
Dev agencies bill by the hour but deliver in commits. Corcava’s Coding Report puts tracked time, GitHub activity, and Cursor usage on the same row per developer — so you can spot mismatches before the invoice goes out.
No credit card required · GitHub supported today

The dev-shop problem: hours logged, output unclear
Project managers see 40 billable hours on a sprint. GitHub shows a handful of commits. Was the team blocked, doing non-commit work, or is time mis-attributed? Without one report, you export Harvest, open GitHub Insights, and still guess.
Tracked time
Billable and non-billable hours from Corcava’s time tracker, per user and date range.
GitHub commits
Commit count, lines changed, files touched, and derived metrics (hours per commit, lines per hour).
Cursor usage
Lines, requests, and spend when you connect the Cursor integration.
How it works
- 1
Connect GitHub
Settings → Integrations → GitHub. Select repos to include. See GitHub integration.
- 2
Map Git users to your team
Link GitHub identities to Corcava users so commits and hours align on one row.
- 3
Open Reports → Coding Report
Pick a date range. Review team, org, and repo tabs. Optional red-flag analysis highlights outliers.
- 4
Add Cursor (optional)
Connect Cursor Admin API to see AI usage and spend alongside Git and time. Cursor columns hide when you filter by org/repo.
Worked example: 8-person shop, one client sprint
Stackline Dev runs a two-week sprint for a fintech client. The PM pulls Coding Report for the sprint window:
Senior dev (Alex): 36 tracked hours, 28 commits, strong lines/hour — healthy delivery pace.
Mid dev (Jordan): 32 tracked hours, 4 commits — red flag. Conversation reveals most time on code review and pairing (legitimate, but invoice narrative needs updating).
Cursor spend: Visible for the team; PM sees AI-assisted work without a separate Cursor export.
Outcome: Client status report cites hours and shipped commits from one export. No second tool, no “trust us” spreadsheet.
Full agency stack: agency management · software development teams
FAQ
Does Coding Report support GitLab?
Not yet. GitHub is fully supported today. GitLab connect UI exists in the app but sync is not available — do not plan workflows around GitLab until it ships.
Is this the same as time tracking?
Time tracking logs hours. Coding Report combines those hours with Git (and optionally Cursor) for output comparison. You still track time in Corcava as usual.
Can clients see the Coding Report?
The report is internal. Share summaries via the client portal time reports if clients need transparency.
See hours and commits together
Connect GitHub and open Coding Report on your next sprint review.
Start free trial →