The https://cursor.com/dashboard/analytics won’t count ipynb files generated by Agent. So Agent Lines of Code won’t be updated if the agent only generate ipynb files.
Whether any files patched/generated by Agent should be counted?
The https://cursor.com/dashboard/analytics won’t count ipynb files generated by Agent. So Agent Lines of Code won’t be updated if the agent only generate ipynb files.
Whether any files patched/generated by Agent should be counted?
Hey, thanks for the report, I can reproduce it. This is a known gap in tracking: in some cases, edits to .ipynb made by Agent don’t show up in Agent Lines of Code on the dashboard. They should count, notebook edits are the same kind of changes as regular files.
I’ve reported this internally. No ETA for a fix yet, I’ll post an update here when I have one.
It no longer counts generated MD files any more. In last month it still counted.
Documents, prompts, SKILLs etc. all should be counted as agent generated lines, right?
Hey, thanks for coming back to the thread.
On scope, yes, basically all text files that the Agent edits or generates, including .md, docs, prompt files, and SKILLs, should count toward Agent Lines of Code. There are no file extension exclusions on the dashboard side.
About .ipynb, that’s a known gap in client-side tracking.
About .md, this sounds like a regression. It used to be counted, and now it isn’t. To reproduce it and file a separate report, we need a bit more detail:
Cursor > About during the last time tracking worked, and your current version.md, plus a screenshot of the dashboard for that day (you can filter by date)