---
title: "Project Breakdown — See Exactly Where Your Coding Time Goes"
description: "xeve now breaks down coding time by project. See which codebases consume the most hours, track daily project allocation, and understand how your engineering effort distributes across repos."
date: "2026-03-21"
app: orma
category: "developer-productivity"
readingTime: "4 min read"
---

<p>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.</p>

<h2>Automatic Project Detection</h2>

<p>xeve extracts project names from window titles without any manual configuration. The parsing logic handles multiple editor formats:</p>

<ul>
<li><strong>VS Code / Cursor</strong> — parses "filename — ProjectName" from the title bar</li>
<li><strong>Xcode</strong> — parses "ProjectName — filename" (reversed order)</li>
<li><strong>Terminal / iTerm / Warp</strong> — extracts the working directory path and uses the deepest folder as the project name</li>
</ul>

<p>This means every coding session gets a project label automatically. No tags, no timers, no manual assignment.</p>

<h2>The Projects Dashboard</h2>

<p>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:</p>

<ul>
<li><strong>Projects by time</strong> — a ranked horizontal bar chart showing every project with percentage and duration. Your top project is immediately visible.</li>
<li><strong>Daily breakdown</strong> — 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.</li>
<li><strong>Recent sessions</strong> — a table of recent coding sessions with the app used, window title, start time, and duration.</li>
</ul>

<h2>What This Reveals</h2>

<p>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.</p>

<p>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.</p>

<h2>Combining with GitHub</h2>

<p>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.</p>

<p>View your project breakdown at <a href="https://orma.xeve.io/dashboard/projects">xeve.io/dashboard/projects</a>.</p>