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.
If your goal is to start using NextClaw rather than study project status first, start here instead:
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-05-26Production LOC trend
A running signal of implementation scope, not a quality score by itself.
168,021
Latest
168,021LOC
Recent production source snapshot window-7.5Kvs previous snapshot+146.3KSince start189.9KPeak
Test LOC trend
A separate signal for verification investment so tests do not inflate production scope.
44,631
Latest
44,631LOC
Recent test source snapshot window-3.8Kvs previous snapshot-14.7KSince start59.3KPeak
Commit rhythm
Switch between daily and weekly views to read short-term execution and broader delivery cadence.
455
Latest
22commits
30-day daily commit rhythm+8vs previous day+22Since start59Peak
Monthly release rhythm
Release batches grouped by tag days instead of raw tag count.
63
Latest
15batches
12-month release rhythm-2vs previous month+15Since start28Peak
Current Shape
sourceTop scopes by code volume
Where the current implementation footprint is concentrated.
Benchmark snapshot
We compare production source LOC against OpenClaw to keep complexity visible.
11.51%
NextClaw is 11.51% of openclaw production source LOC.
88.49% lighter by production source LOC.
Recent release batches
Latest tag days and how many packages moved together.
2026-05-2692 packages
@nextclaw/[email protected] · @nextclaw/[email protected] · @nextclaw/[email protected]
2026-05-2459 packages
@nextclaw/[email protected] · @nextclaw/[email protected] · @nextclaw/[email protected]
2026-05-23150 packages
@nextclaw/[email protected] · @nextclaw/[email protected] · @nextclaw/[email protected]
2026-05-2262 packages
v0.19.18-desktop-beta.1 · v0.19.19-desktop-beta.1 · v0.19.20-desktop-beta.1
2026-05-214 packages
v0.19.17-desktop-beta.1 · v0.19.17-desktop-beta.2 · v0.19.17-desktop-beta.3
2026-05-19110 packages
v0.19.10-desktop-beta.1 · v0.19.10-desktop-beta.2 · v0.19.12-desktop-beta.1
Product Timeline
5 notesRecent product notes
Public milestones that matter to users, not just internal diffs.
2026-05-062026-05-06 · Auto Updates and Long-Context Awareness
NextClaw now supports auto updates, context window usage, and automatic long-session compaction so daily use feels easier and long tasks stay more continuous.
2026-04-262026-04-26 · NextClaw Feels Better on MobileNextClaw recently shipped a mobile experience update. Once deployed, opening NextClaw from a mobile browser now shows a cleaner chat, session, and input experience for small screens.
2026-04-032026-04-03 · Sessions Now Actually Stay Project-AwareNew 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-05-26- 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.
- Production source LOC is tracked as a maintainability trend, while test LOC is shown separately so coverage work is not misread as product complexity.