展示HN：你对Claude Code的使用情况如何？
我与多家公司交流过，它们都有自己的Claude和Codex OTel仪表板，显示每月的支出和使用席位数量。然而，这些仪表板实际上并没有分析工程师如何使用这些工具，以及是否存在改进的空间！这就是我创建<a href="https://www.promptster.ai" rel="nofollow">https://www.promptster.ai</a>的原因。
管理者可以获得代码质量的汇总视图，以及这些与团队工作流程的关联（没有逐个工程师的详细信息）。而工程师则可以获得个性化的指导，帮助他们在保持高产出的同时节省使用令牌。
我们还为个人开发了一个工具，用于测试他们本地的Claude代码设置。这个工具是开源的，完全可以在本地使用。你可以在这里查看：<a href="https://github.com/pa-arth/cc-audit" rel="nofollow">https://github.com/pa-arth/cc-audit</a>。
如果你对这两个工具有任何反馈，或者对购买团队产品感兴趣，请随时联系我！
查看原文
A bunch of companies that I spoke to had their own claude & codex OTel dashboards that showed spend + seats per month.<p>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 <a href="https://www.promptster.ai" rel="nofollow">https://www.promptster.ai</a>.<p>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.<p>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: <a href="https://github.com/pa-arth/cc-audit" rel="nofollow">https://github.com/pa-arth/cc-audit</a>.<p>Would love feedback on either and reach out if you're interested in purchasing the teams product!