CELLAXON DevPulse

Local-first Git analytics and AI agent activity tracing for Visual Studio Code.

CELLAXON DevPulse helps you understand how a repository changed and how an approved local Codex or Claude session reached its result. Repository statistics, agent sessions, execution traces, and available evidence stay on your machine. No DevPulse account or application server is required.

DevPulse reports observed activity and evidence. Commit counts, changed lines, elapsed time, tokens, and tool calls are descriptive signals—not measures of working time, code quality, or individual productivity.

What you can do

Analyze repository activity by period, participant, group, revision scope, and time zone.
Compare contributors and explore trends with charts, heatmaps, and accessible data tables.
Review approved Codex or Claude sessions in Overview, Sessions, Trace, Phases, or Linear views.
Inspect available file, test, diff, and commit evidence without treating uncertain relationships as facts.
Check provider compatibility and partial data in Source Health.
Export local Markdown, CSV, or two-page PDF reports with an exact weekday-by-hour heatmap and totals.

Requirements

Visual Studio Code 1.106 or later
Git available on PATH
Visual Studio Code Desktop with a trusted, file-backed workspace

Windows desktop is the currently verified environment. Virtual workspaces and vscode.dev are not supported. macOS, Linux, WSL, Remote SSH, and Dev Containers have not yet completed the same release validation.

Install

Visual Studio Marketplace

Open Extensions in Visual Studio Code.
Search for CELLAXON DevPulse.
Select Install.

VSIX package

Open Extensions.
Open the ... menu and select Install from VSIX....
Choose the provided cellaxon-devpulse-<version>.vsix file.
Reload Visual Studio Code if prompted.

Quick start

Explore repository activity

Open a trusted workspace containing a Git repository.
Open Source Control.
Select the graph action on the repository row. At narrow widths, use the repository ... menu.
Choose the participants, period, time bucket, revision scope, merge policy, and report time zone you want to inspect.
Use the chart, heatmap, and table views or export a Markdown, CSV, or PDF report.

Each Git repository is analyzed independently. Selecting Agent sessions from Repository Statistics opens matching local agent sessions when repository evidence is available.

Review local Codex or Claude activity

Open the DevPulse icon in the Activity Bar.
Expand Data & Privacy and select Add agent source.
Review the detected provider, version, and masked source location, then approve a preview containing only counts and compatibility information. DevPulse does not inspect provider records before this approval.
Review the previewed file count, record count, compatibility, and coverage, then confirm the import. The original provider history remains read-only.
Use Overview for trends, Sessions for individual runs, and Source Health for compatibility or coverage issues.
Open a session and switch between Trace, Phases, and Linear as needed.

You can also use the Command Palette:

DevPulse: Open Repository Statistics
DevPulse: Open Agent Activity Overview
DevPulse: Open Agent Sessions
DevPulse: Open Source Health

Understand evidence

DevPulse keeps uncertainty visible:

State	Meaning
`exact`	Structured provider or Git evidence directly identifies the target.
`correlated`	Repository and time evidence supports the relationship, but does not prove it directly.
`conflict`	Multiple candidates or inconsistent evidence prevent safe attribution.
`unresolved`	No safe relationship can be established.

A supported capability with no observed records is shown as 0. A capability that the source format cannot establish is shown as unavailable (—) with a reason.

File, diff, Source Control, and commit actions appear only when DevPulse can revalidate the target in the current workspace. Stale, missing, ambiguous, or out-of-workspace targets remain unavailable instead of opening a guessed location.

Privacy and local data

Repository analysis and approved agent history are processed locally.
DevPulse does not upload analyzed repository or agent data.
Provider history is imported read-only after explicit preview and confirmation.
Approved provider source locations are stored locally so refresh, removal, and reveal actions can work. A full source location is shown only after confirmation.
Agent activity storage excludes raw prompts, responses, reasoning, command arguments, tool input/output, file contents, commit messages, author identities, and full repository paths.
Full repository paths are kept out of the visual interface; file and Git actions are validated by the extension before they open.
Agent-activity exports redact project, model, and source-location labels by default unless you explicitly include them for a trusted destination.
Exports remain local until you move or share them.

To remove local data:

Run DevPulse: Clear All Agent Activity to remove approved sources and imported agent metadata. This does not delete the original Codex or Claude history.
Run Clear All Cache from the DevPulse Cache view to remove stored Git-analysis snapshots.

If local data must be removed, use these actions before uninstalling the extension. Visual Studio Code and operating-system backup retention are outside DevPulse control.

Settings

Search for CELLAXON DevPulse in Visual Studio Code Settings.

Setting	Default	Purpose
`cellaxonDevPulse.cache.enabled`	`true`	Reuse compatible local Git-analysis snapshots.
`cellaxonDevPulse.cache.autoPrune`	`true`	Automatically remove old and least-recently-used snapshots.
`cellaxonDevPulse.cache.maxAgeDays`	`30`	Set the unused age after which a snapshot can be removed.
`cellaxonDevPulse.cache.maxSizeMb`	`512`	Limit the compressed Git-cache size.

Agent-source approval, refresh, removal, and clear-all actions are managed from Data & Privacy.

Accessibility and languages

Trace information has an equivalent searchable Linear view.
Charts have equivalent data tables.
Keyboard navigation, narrow editors, high-contrast themes, reduced motion, and 200% zoom are supported.
English, Korean, Japanese, Simplified Chinese, Traditional Chinese, and Spanish are included. Other display languages fall back to English.

Troubleshooting

Problem	What to check
Repository Statistics does not open	Confirm that Git is installed, the workspace is trusted and file-backed, and the repository appears in Source Control.
No agent source is detected	Confirm that local Codex or Claude history exists, then run DevPulse: Add Agent Source again.
Session totals are partial or unavailable	Open Source Health and review compatibility, unsupported records, and capability coverage.
A file, diff, or commit action is unavailable	Reopen the matching repository and confirm that the target still exists. DevPulse will not guess stale or ambiguous targets.
The first analysis or import is slow	Large Git or agent histories can require significant CPU, memory, disk space, and disk I/O on the first run.
Local activity storage cannot be read	Reload the Visual Studio Code window. If the issue continues, review Data & Privacy before clearing local data.

Current limitations

Codex and Claude history formats change over time; Source Health reports unsupported or partially supported records.
Historical uncommitted diffs cannot be reconstructed unless matching evidence was captured at the time.
Shell command text is not converted into exact file, test, or commit evidence.
Git time charts use commit timestamps in the selected report time zone and do not represent attendance or working hours.

Website and license

Product information and company contact: cellaxon.com