Claude Code, AI dev tooling, and building in the open
By Liran Baba, AI Solutions Architect. Writing about what I learn building tools for AI-assisted development.
Fleet view: every Claude Code agent on one board
One board for every Claude Code session running now or in the last 24 hours: which agents need you, which are working, and how long until each prompt cache goes cold.
Read postHow to track Claude Code costs: /usage, the Console, ccusage, and Claudoscope
Four ways to see what Claude Code is costing you, from the built-in /usage command to per-session dashboards, what each one can and cannot show, and why no estimate matches the invoice exactly.
Read postWhere Claude Code stores your session history, and how to keep it past 30 days
Claude Code writes every session to ~/.claude/projects as JSONL and deletes it after 30 days by default. The directory layout, the cleanupPeriodDays setting, how to find and resume old sessions, and how to search inside them.
Read postClaudoscope 1.0: from a menu bar readout to a lens on Claude Code
Claude Code notifications, cost alerts, an embedded MCP server for querying your own usage, per-session file diffs, and a session index that loads in under a second.
Read postI found my database password in a Claude Code session file
How a leaked credential in a Claude Code session file led to building Claudoscope, a macOS menu bar app for session analytics, cost tracking, and secret detection.
Read post