Knowing you coded 5 hours today is useful. Knowing you spent 3 hours on the API rewrite, 1.5 hours on bug fixes in the dashboard, and 30 minutes context-switching between three other repos — that is actionable. The Projects page provides this granularity automatically.
Automatic Project Detection
xeve extracts project names from window titles without any manual configuration. The parsing logic handles multiple editor formats:
- VS Code / Cursor — parses "filename — ProjectName" from the title bar
- Xcode — parses "ProjectName — filename" (reversed order)
- Terminal / iTerm / Warp — extracts the working directory path and uses the deepest folder as the project name
This means every coding session gets a project label automatically. No tags, no timers, no manual assignment.
The Projects Dashboard
Four stat cards summarize your project activity: total coding time, number of active projects, your most active project with hours, and average time per project. Below that:
- Projects by time — a ranked horizontal bar chart showing every project with percentage and duration. Your top project is immediately visible.
- Daily breakdown — a stacked bar chart showing your top 5 projects by day, with an "Other" bucket for the rest. This reveals whether you are focused on one project or scattered across many.
- Recent sessions — a table of recent coding sessions with the app used, window title, start time, and duration.
What This Reveals
The most common insight is that developers underestimate how fragmented their project time is. You think you spent the day on one project, but the data shows 6 different repos each getting 30-60 minutes. That fragmentation is invisible without tracking — you feel busy but cannot point to deep progress on any single thing.
The daily breakdown chart is especially revealing for sprint planning. If your team estimated 3 days for a feature but the project data shows you only averaged 2 hours per day on that repo (because meetings, reviews, and other projects consumed the rest), the estimate was never realistic.
Combining with GitHub
Project time data becomes even more powerful when combined with GitHub activity. The Overview page shows both side by side — you can see whether the projects consuming the most editor time are also producing the most commits and PRs. A project with 20 hours of coding and 3 commits might indicate an exploration phase. One with 5 hours and 40 commits is clearly in shipping mode.
View your project breakdown at xeve.io/dashboard/projects.