Counting does not work at all

[cwikio]

Just installed the app and got this:

The only caveat:

1. I dont use cursor at all
2. I am coding now, but with codex model
3. I am in zed IDE
4. I am not debugging but creating new feature

So this whole thing could not be more wrong than it is. Had great hopes but looks useless so far.

[iamtoruk]

On it

[iamtoruk]

Thanks for reporting this and for being specific about what's wrong. Looking into it now.

Two things are likely happening:

1. Activity classification is too aggressive with "Debugging"

The classifier checks debug keywords (fix, error, issue, bug) before feature keywords (add, create, implement, new). So if your prompt says something like "add error handling" or "create an issue tracker" or "fix the layout for the new feature", it gets tagged as Debugging instead of Feature Dev. These words show up all the time in normal feature work. We need to either reorder the priority or add context awareness so "error" in "error handling" doesn't trigger the debug path.

2. Provider misattribution

If you ever had Cursor installed, there may be leftover files in ~/.cursor/projects/ that our cursor-agent provider picks up. It scans that directory without checking whether Cursor is actually installed. Even residual transcript files get attributed as Cursor sessions.

Can you check:

• Does ~/.cursor/ exist on your machine even though you don't use Cursor?
• What does codeburn status show for provider breakdown?
• Can you share what your first prompt to Codex was in that session? (so I can trace why the classifier got it wrong)

Working on fixes for both. The classifier one is the more impactful issue.

[iamtoruk]

One more thing - we don't have Zed support yet. If you're using Zed's built-in AI assistant (even with a Codex/OpenAI model), codeburn can't see that usage. Zed stores AI sessions in its own format and location that we don't read.

So the data you're seeing is likely either stale sessions from a previous tool, or the Codex CLI sessions being misclassified. If you're running Codex CLI separately from Zed, those sessions should show up under the Codex provider. But if you're using Zed's AI panel directly, that's the gap.

Zed provider support is on the roadmap. In the meantime, codeburn status will show you which providers are actually contributing data so you can see what's being picked up.

[iamtoruk]

Can you run these and paste the output?

codeburn status
codeburn today --json | head -100
ls -la ~/.cursor/projects/ 2>&1 | head -20
ls -la ~/.codex/ 2>&1 | head -10

This will tell us exactly which providers are feeding data and whether there's a stale ~/.cursor directory on your machine.