ProcessLens logo ProcessLens BETA

Developer productivity visibility.

You can't improve what you don't measure. ProcessLens tracks builds, tests, and process times — locally and privately — so you can spot slowdowns before they hurt your flow.

📦 Install on VS Code Marketplace ⭐ Star on GitHub ☕ Buy me a coffee
Local-first • Private • Open source
Currently in beta — your feedback helps shape the future of ProcessLens
* Screenshots from v0.1.2 — UI subject to change.

Current Features (v1)

⚡

Zero-config timing

Run any script or command. We capture start/end, duration, and status.

📊

Dashboard in VS Code

See recent runs, averages, and simple history charts.

📈

Status bar insights

Know instantly how long the last run took.

🔒

Local-first

Data stays on your machine. JSON/SQLite, no telemetry, no lock-in.

Why ProcessLens?

Developers everywhere lose time waiting on builds and tests. Without measurement, teams only feel slowdowns — ProcessLens makes them visible.

Why it matters

  • ⏱ Every dev waits — seconds add up into hours.
  • 📊 Evidence, not feelings — real data, not guesses.
  • 📈 Trends over time — catch creeping slowdowns early.
  • 👥 Team value — justify infra improvements with data.
  • 🔍 Personal utility — catch regressions early.

What makes it different

  • 🌍 General-purpose — measure any process, not just JS builds.
  • 📉 Trend-focused — not just “this run took 9s,” but what changed over time.
  • 💻 Developer-first — lives in VS Code, zero-config, instant insight.

Think of it as time tracking for machines, not humans.

Humans log hours worked. ProcessLens logs seconds wasted waiting on computers.

Coming Soon

⏱

Watch-mode rebuild timings

Vite, Webpack, Jest

🗄

SQLite backend

For faster queries

☁️

Cloud sync (opt-in)

Team dashboards & history

📊

Advanced analytics

p50/p95, regressions, trends

Privacy First

ProcessLens is local-first. Your data never leaves your machine unless you opt-in to sync.