Tracking AI coding spend like Claude Code per project and client

On October 3, 2026, DEV Community published a post titled “How to track AI coding spend like Claude Code by project and client.” The article targets a common reporting gap for teams that deliver software with Claude Code, Cursor, or raw API keys. Such teams may have a rough sense of their monthly AI spend, but they almost certainly cannot answer a more specific question: “Which project — or which client — consumed that spend?”

The author argues that this question matters whenever any of the work is billed. Hours and licenses already show up on invoices, while AI costs currently hide inside a terminal. The post therefore explains how to break down AI spending generated by Claude Code, Cursor, or direct API key usage and attribute it to specific projects and clients, so that the cost can appear on invoices alongside hours and licenses.

The article is not a general overview of AI pricing; it focuses on attribution — taking raw usage records and assigning them to a project or client. The author describes the mechanics: where the usage data actually lives, how to convert that data into per-project amounts, and how to run the supplied tool with a single command. The tool is written by the author and is presented as a one-command solution.