Cellaxon DevPulse

Understand how a Git repository changes—directly inside VS Code, without sending repository history to a server.

Cellaxon DevPulse adds a graph action to every Git repository in Source Control. Open it to explore activity over time, focus on one contributor, or compare multiple contributors in the same repository.

DevPulse visualizes activity recorded in Git history. Commit and line counts do not measure working time, code quality, or individual productivity.

Explore repository activity

• Start with an overall view of the repository, then select one contributor for an individual view.
• Select two or more contributors to compare their activity, with an option to include your resolved Git identity.
• Build one simple participant tree per repository. Drag identities into a person or team group, nest groups, and select a group to combine every descendant identity into one series.
• Switch between hour, day, ISO week, month, and calendar-year views without rerunning Git when only the presentation changes.
• See when commits are most often recorded with a weekday-by-hour heatmap, and expand the hour-of-day and weekday charts when you need the marginal distributions. All time patterns use the selected report time zone.
• Review the same results in charts and a paginated data table.
• Export a one-page PDF summary with high-resolution charts, or use CSV when you need every detailed row and time-distribution value. Markdown remains available for text-based sharing.
• Reopen the same analysis faster with an optional local cache that you can inspect and clear at any time.
• Follow the VS Code display language across commands, settings, the dashboard, accessibility labels, Markdown, and PDF output. English, Korean, Japanese, Simplified Chinese, Traditional Chinese, and Spanish are included.

Get started

1. Open a trusted workspace that contains one or more Git repositories.
2. Open Source Control and select the graph icon on a repository row. At narrow widths, the action may appear in the repository ... menu.
3. Use the participant list on the left:
   • no selection shows overall repository activity;
   • one selection shows that contributor;
   • two or more selections compare contributors or groups;
   • select Add to create a group, then drag participants into it or use each row's move menu;
   • select a group to combine all participants and nested groups below it.
   • drag the divider beside the list to resize it, or focus the divider and use the arrow, Home, and End keys.
4. Choose a date range, time bucket, revision scope, and merge policy. To keep charts readable, hour supports up to 14 days, day up to 365 days, week up to 1,825 days, month up to 7,300 days, and whole history is available in the annual view. Select Refresh when you want to bypass the cache and analyze Git again.
5. Select Export and choose the output for the job:
   • PDF summary (1 page) keeps the key metrics and up to four decision-useful charts;
   • CSV detailed data includes every table row plus hour-of-day, weekday, and weekday-by-hour distributions;
   • Markdown provides a readable text report.

You can also run DevPulse: Open Repository Statistics from the Command Palette.

Your repository data stays local

DevPulse processes Git history on your machine. It does not require a DevPulse account or application server, and it does not transmit analyzed repository history.

Exports remain on your local filesystem until you move or share them. The optional cache is stored in VS Code extension global storage as devpulse-cache.sqlite3. It contains aggregate statistics and display metadata—not commit subjects, raw file events, or author email addresses.

Your participant tree is stored separately from the statistics cache in VS Code extension global state. DevPulse saves one versioned tree per repository, containing group names and opaque author IDs rather than email addresses. Clearing statistics cache data does not remove this tree. The tree is local to the current VS Code profile and machine; DevPulse does not sync or publish it.

By default, DevPulse removes cache snapshots that have not been used for 30 days and limits compressed cache data to 512 MB. Use the DevPulse Cache view in Source Control to:

• review the repositories currently using cache space;
• remove expired or least-recently-used data;
• delete cached data for one repository;
• clear all DevPulse cache data after confirmation.

Search for Cellaxon DevPulse in VS Code Settings to enable or disable the cache and change its retention limits. If the cache is unavailable or damaged, DevPulse treats it as a cache miss and analyzes Git again.

Requirements and known limitations

• VS Code 1.106 or later
• Git available on PATH
• A trusted, file-backed workspace running in a desktop/workspace Extension Host
• Virtual workspaces and vscode.dev are not supported
• Windows is currently the verified platform; macOS, Linux, Remote SSH, and Dev Containers have not yet completed the same validation
• The first analysis of a very large history can use significant CPU and memory; later identical analyses can reuse the local cache
• Contributor grouping follows Git mailmap behavior, so aliases must be represented by repository or configured mailmaps to resolve together
• The participant tree is a display-time grouping layer: it does not modify .mailmap or Git history, and it provides one local configuration rather than shared team profiles
• Time-pattern charts use each commit's authored timestamp converted to the selected report time zone. The heatmap combines selected participants and automatically groups sparse samples into three-hour buckets; these views show Git activity patterns, not attendance or working hours
• The built-in translations cover English, Korean, Japanese, Simplified Chinese, Traditional Chinese, and Spanish. Other VS Code display languages fall back to English.
• One-page PDFs fully embed Pretendard GOV for English, Korean, and Spanish, and automatically use the bundled Noto Sans CJK fallback for Japanese, Chinese, or mixed-script repository and participant names. Complete embedding prevents viewer-specific missing glyphs, but CJK reports can be larger. Both fonts are distributed under the SIL Open Font License; font files and license notices stay inside the VSIX.