However, none of the dashboards actually analyzed how the engineers worked with the tools and if there were any areas for improvement! That's why I created https://www.promptster.ai.
Managers get aggregate level view of code quality and how that ties with team workflows (nothing on a per-engineer level). While engineers get personalized coaching on how they can save tokens while keeping output high.
We also have a tool built for individuals to test their local claude code setups. It's open-source and completely local. You can check that out here: https://github.com/pa-arth/cc-audit.
Would love feedback on either and reach out if you're interested in purchasing the teams product!
But honestly, it is extremely rare thing not using codex, or cluade code or any other agent.
I do think, however, that holding out on it is a losing proposition. It's a very useful productivity tool if you know how to use it and those who don't will be left behind.