Momentum — workflow intelligence
Home
Integrations
Pricing
All integrations
+
Code & development integration

Momentum + SonarQube

Bring SonarQube quality metrics alongside activity to see how focus affects code health.

Book a demo Start free trial

What you can do

Quality-metric context
Trend-vs-focus view
Project rollups
// Code & development

How Momentum reads code & development time

SonarQube time is captured by the desktop agent like any other app — here's how it flows into classification, scores, and dashboards.

01
Deep work, measured honestly

Engineering is where Momentum's capture model shines: IDEs, terminals, and local build tools are offline desktop apps that browser-based trackers miss entirely. The agent records them all — active window, duration, keyboard and mouse counts — so a three-hour uninterrupted stretch in an editor shows up as exactly that on the Timeline, not as a blank spot between browser sessions.

02
Protecting the conditions that ship

With dev tools marked Productive for engineering departments, the Activity module's productivity score reflects real maker time, and the Workforce Dashboard's top-performer and department views reveal which teams get long focus blocks and which are fragmented. Leaders use the expected-vs-actual trend to defend focus time with evidence rather than anecdotes.

// Classification guidance

Where SonarQube should land in your app rules

Dev tools are the textbook override case: Productive for Engineering, QA, and DevOps departments, but usually Unmarked globally — an IDE open on an HR machine is unusual, not productive. Global App Rules set the neutral default; department overrides grant Productive status only where writing code is actually the job.

PRODUCTIVENON-PRODUCTIVEUNMARKED
app rules — code & developmentLIVE
VS CodePRODUCTIVE
91% of dept time
TerminalPRODUCTIVE
74% of dept time
GitHub DesktopUNMARKED
33% of dept time
global rule + department overrides · sample data
// FAQ

SonarQube + Momentum, answered

Are offline tools like IDEs and terminals really tracked?+

Yes. Momentum's Windows, macOS, and Linux agents capture active-window time for any desktop application, online or offline — no browser extension or network activity required.

Does Momentum capture code or keystrokes?+

No. Input tracking is count-based — how many keystrokes and clicks, never which keys. Source code, file contents, and clipboard data are never collected.

How heavy is the agent on a developer machine?+

The agent is built to stay out of the way, and admins can verify it: the Resource Usage view in the console shows the agent's own CPU and memory footprint per machine.

Other integrations

Connect Momentum and SonarQube

Book a demo and we'll show you the integration live.

Book a demo Browse integrations