Capturing a 400-Turn Claude Code Session in a Single Image

Comet Cost Intelligence explored whether coding-agent sessions could be represented as recognizable phases and tasks to help organizations understand token spending driven by developer behavior, rather than only model settings or context bloat. After analyzing thousands of Claude Code sessions with a locally run Qwen3-4B model, the team found that sessions could be segmented into recurring activities such as exploration, implementation, validation, and discussion, while also revealing that multiple unrelated tasks within one session can create unnecessary context costs. Small models could make useful semantic judgments but struggled with long-range bookkeeping, so the system processes compressed transcript windows, carries short contextual notes between them, and uses deterministic rules to stitch results together, with validation and versioning intended to ensure stable, reproducible charts. The approach runs continuously on a single GPU at a projected capacity of roughly 1,700 to 2,000 active developers, and its development prioritized proving the underlying concept on real data before finalizing interface design. The authors acknowledge important limitations, including the absence of ground truth for phase labels, difficulty distinguishing developer prompts from agent self-prompting, and uncertainty about whether users unfamiliar with the system will interpret session shapes correctly.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.