content: ClawMetry vs NemoClaw + OpenClaw memory monitoring blog posts#316
Draft
vivekchand wants to merge 3 commits intomainfrom
Draft
content: ClawMetry vs NemoClaw + OpenClaw memory monitoring blog posts#316vivekchand wants to merge 3 commits intomainfrom
vivekchand wants to merge 3 commits intomainfrom
Conversation
- Sliding 2-min window token threshold (default: 10,000 tokens/2min) - Consecutive tool-call chain detection (default: N=20 without human turn) - Cost velocity alert (default: $0.10/min over 5-min window) - In-dashboard banner with Kill Loop + Dismiss buttons (animated, red/orange) - Background thread checks velocity every 30s - Telegram notification on new alert types - GET /api/alerts/velocity — current alert state - POST /api/alerts/velocity/config — configure thresholds - POST /api/alerts/velocity/dismiss — dismiss active alerts - Config stored in existing budget_config SQLite table (velocity_ prefix)
… JSONL data, add HTML panel to Overview - api_heatmap(): now covers 30 days (was 7); primary source is session JSONL files so historical data is richer; log-file fallback for days with no session events; each day entry now includes 'date' field alongside 'label' - loadHeatmap() JS: updated for 30-day view — sparse day labels (every 5th), 6-band colour scale, hour labels only at 00/06/12/18, safe guard when heatmap-grid element is absent - startSystemHealthRefresh(): now calls loadHeatmap() on startup and refreshes every 5 minutes via _heatmapTimer - Overview HTML (both light/dark themes): added Activity Heatmap panel inside the System Health section with heatmap-grid + heatmap-legend elements - tests/test_api.py: added TestHeatmap (7 tests) — 30-day length, 24 buckets per day, label/date keys, non-negative int counts, max field correctness; all 78 tests pass Closes #69
- docs/blog/nemo-vs-clawmetry.md: comparison targeting GTC buzz Angle: local-first free (ClawMetry) vs enterprise-priced (NemoClaw) Validates the market, highlights ClawMetry's zero-setup advantage - docs/blog/openclaw-memory-monitoring.md: SEO gap filler Targets 'openclaw memory monitoring' (zero existing content) Explains memory drift, context window consumption, ClawMetry analytics Both CTA to 'pip install clawmetry'
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two SEO-focused blog posts drafted while the content opportunity is hot:
ClawMetry vs NemoClaw — Rides NVIDIA GTC buzz. Positions ClawMetry as the free, local-first alternative to NemoClaw's enterprise cloud approach. Clear use-case split.
OpenClaw memory monitoring — Targets the 'openclaw memory monitoring' keyword (zero competing content). Explains memory drift, context window consumption, and how ClawMetry's analytics panel catches it.
Both are ready for landing site integration or can be published as standalone posts.