Project Pulse
Project Pulse is the public dashboard for how NextClaw keeps evolving as an AI operating layer.
It combines engineering movement and product signals into one page: code volume trend, commit rhythm, release cadence, recent product notes, and current automated screenshots.
Project Pulse
A public view into how NextClaw keeps shipping.
This page turns engineering movement into a product signal: how the codebase grows, how often we ship, what we are improving, and what the product looks like right now.
Not a metrics wall. A product pulse for a unified AI operating layer.
Rhythm
Updated 2026-04-16Source LOC trend
A running signal of implementation scope, not a quality score by itself.
182,759
Latest
182,759LOC
Recent source snapshot window0vs previous snapshot+161.1KSince start182.8KPeak
Commit rhythm
Switch between daily and weekly views to read short-term execution and broader delivery cadence.
607
Latest
7commits
30-day daily commit rhythm-10vs previous day+1Since start60Peak
Monthly release rhythm
Release batches grouped by tag days instead of raw tag count.
52
Latest
8batches
12-month release rhythm-19vs previous month+8Since start27Peak
Current Shape
sourceTop scopes by code volume
Where the current implementation footprint is concentrated.
Benchmark snapshot
We compare source LOC against OpenClaw to keep complexity visible.
9.92%
NextClaw is 9.92% of openclaw source LOC.
90.08% lighter by source LOC.
Recent release batches
Latest tag days and how many packages moved together.
2026-04-1438 packages
v0.17.11-desktop.1 · @nextclaw/[email protected] · @nextclaw/[email protected]
2026-04-1359 packages
@nextclaw/[email protected] · @nextclaw/[email protected] · @nextclaw/[email protected]
2026-04-125 packages
v0.17.6-desktop-beta.2 · v0.17.6-desktop-beta.3 · v0.17.6-desktop-beta.4
2026-04-1031 packages
v0.15.62-desktop-beta.3 · v0.15.73-desktop-beta.1 · @nextclaw/[email protected]
2026-04-0934 packages
@nextclaw/[email protected] · @nextclaw/[email protected] · @nextclaw/[email protected]
2026-04-0856 packages
@nextclaw/[email protected] · @nextclaw/[email protected] · @nextclaw/[email protected]
Product Timeline
3 notesRecent product notes
Public milestones that matter to users, not just internal diffs.
2026-04-032026-04-03 · Sessions Now Actually Stay Project-Aware
New sessions can bind a project before the first message, project skills now load per session, the project badge is actionable, and this ships in one unified npm patch release.
2026-03-312026-03-31 · Cron Is Clearer Now, and One-Shot Jobs Finally Feel One-ShotCron now lists disabled jobs by default, separates disable from remove, and improves one-shot scheduling plus AI prompting clarity.
2026-03-112026-03-11 · Bocha Search Integration + Runtime AlignmentBocha search integration, configurable search providers, UI activation controls, and runtime package alignment.
Current Screens
Latest screenshot refresh 2026-04-16Automated screenshot gallery
These images are refreshed through our existing screenshot automation.
Sessions, project context, model selection, and tool execution in one surface.
Switch models and providers without fragmenting the user experience.
Operate multiple external channels through one consistent management model.
Skill discovery and documentation stay close to the product instead of living in separate tools.
Product documentation and workflows remain within the same operating surface.
How To Read This
2026-04-14- We intentionally expose a small set of metrics with product meaning instead of publishing every internal engineering signal.
- Release rhythm is grouped by release days, because raw tag counts would mostly reflect monorepo package count rather than product cadence.
- Source LOC is tracked as a maintainability trend, not as a vanity metric. We use it together with scope distribution and note timelines.