Primary project
CursorLens
An open-source dashboard for Cursor.sh IDE. Log AI code generations, track usage, and control AI models (including local ones). Run locally or use upcoming hosted version.
Layer thesis
How to read this branch of the ecosystem
This is the shortest explanation of what this layer is for and why it matters.
Observability is the practical sign that the ecosystem is maturing from novelty to operations.
Key artifacts
Best entry points in this layer
These projects explain this branch of the ecosystem fastest.
Key artifact
specstory
SpecStory automatically saves every Cursor chat and composer session to your local project's .specstory directory.
Key artifact
Cursor Stats
A Cursor extension that displays your Cursor Subscription usage statistics in the status bar.
Key artifact
Chrome Debug Monitor
A powerful integration between Chrome's DevTools Protocol and Cursor Composer for real-time debugging and monitoring.
Work patterns
What people actually do here
These workflow slices connect the layer to real usage patterns.
Workflow pattern
Instrument the agent once the work gets real
Logs, saved sessions, stats bars, dashboards, and browser-debug surfaces show up when teams start trusting Cursor for real development work and need to understand behavior, cost, and history.
Guardrails
What to remember while exploring
Layer-specific best-practice reminders that keep this branch legible.
Best practice
Add observability before you add more autonomy
The presence of chat archives, usage stats, dashboards, and debugging tools suggests a practical pattern: once Cursor starts doing real work, users want logging, replay, and visibility before they scale complexity further.