check out the new AI metrics

- AI Usage by Dev
- Lines of code generated vs written by humans
- Which devs are using which models
- How much those AI generated lines are costing in tokens

We're rolling out this dashboard to teams for Claude, Codex, Cursor, etc.

Your AI coding bill might surprise you. 👀

Crackboard shows the real, unsubsidized cost of your AI usage. See how your spend stacks up at crackboard.dev

I've been cranking so hard on the new Maestro website and the impending releases that I hit #3 in the world on Wakatime this week:

wakatime.com/leaders

But check out how slick the new website!

runmaestro.ai

Burning money on AI?

How much are you spending on AI compared to other devs?

See where you rank on the @WakaTime Leaderboard and find out who’s burning the most subsidized investor cash on models 🔥💸

wakatime.com/leaders/spend

WakaTime has a new leaderboard for non-AI coding:

wakatime.com/leaders/manual

The AI coding leaderboard is now at wakatime.com/leaders/ai

@gayasskitty_ @alanhamlett you should build your own wakatime instead of paying, should only take a few days

Who hurt her

I #code the most on Thursdays, analyzed using data over the last year, via @WakaTime wakatime.com

I noticed I was relying too much on AI, so I’m training my coding muscle memory again.
Installed WakaTime to track my stats.
1k+ lines today. No AI.
Tomorrow: 5k.
Back to building

New pro leaderboard gets top placement in the weekly WakaTime email. Join the board by enabling the PRO badge on your public profile wakatime.com/settings/profi…

Got to know about Wakatime! A timer tracker you can install on your VS Code to see your workrate. So I installed it weeks ago and it's started tracking the number of hours I have worked, projects worked on and even the highest programming language you code with 💻🚀

here are my "WAKATIME" stats from last week.
i'm actively working on my Perps CEX application

@theo @simpsoka Only one agent? Here's mine for Claude + Codex combined

According to @WakaTime, I use AI to write 83% of my code these days, and recently used it to redesign the @WakaTime dashboards for devs and dev teams, with a new focus on AI metrics instead of time.

I used #Codex 60% of the time and #Claude 40% of the time, switching between the rate limits or when one model got stuck. Yes, they didn't always do things correctly and sometimes introduced security bugs, but thankfully I code reviewed everything, paying very close attention to the backend changes so I noticed when it left PII exposed in the API, made incorrect assumptions in business logic, or just introduced random bugs.

Having a different session code review the AI changes before committing helped, but not as much as I thought it would.

The new feature I'm most proud of: Cost by Agent
It shows your "real" cost by token usage for all AI agents you use so you can see if you're using the full value out of your Claude/Codex/Cursor subscription.

damn wakatime now tracks AI usage

WakaTimeいいね。この数字を増やしていこう。開発に再度慣れよう。

using @WakaTime to measure my AI usage… love it

My AI #programming percentage last year via @WakaTime wakatime.com

Unified AI agent dashboard for Claude, Codex, Cursor, Copilot... why do so many AI companies start with C?