AI coding agents are transforming how teams build software. But when your team uses Claude Code, Cursor, and Codex across dozens of projects, you have no visibility into how they're being used, where the friction is, or whether things are getting better or worse over time.
cinsights helps engineering teams track, understand, and improve how their developers work with AI coding agents. Not per-session logs, but patterns across time, across agents, and across your whole team.
Per-project digests - what's working, what's hindering, quick wins, and ambitious ideas. Aggregated across sessions over days or weeks, not a single-run snapshot.
Grounded friction analysis - recurring pain points linked to specific sessions with impact estimates. Copy-paste CLAUDE.md rules and feature recommendations generated from your team's actual friction patterns.
Per-developer profiles - work areas, interaction style, tool preferences, and how each developer uses coding agents. Built from cross-session patterns, not self-reported surveys.
Plus: behavioral patterns that surface how each developer interacts with agents, mood quotes — the actual things developers say to their coding agents when frustrated, amused, or relieved, and quality comparison across the team.
# Install
pip install cinsights
# or: uvx cinsights
# Configure LLM (interactive)
cinsights setup
# No API key? Use Ollama instead:
# ollama pull qwen2.5:14b
# cinsights setup --provider openai --model qwen2.5:14b --base-url http://localhost:11434/v1
# Index local Claude Code / Codex sessions (free, no LLM calls)
cinsights index --source local --hours 8760
# Analyze sessions (shows cost estimate, asks for confirmation)
cinsights analyze --source local
# Generate a project digest
cinsights digest project <my-project> --days 30
# Generate a user digest
cinsights digest user <user-id> --days 30
# Start the web UI
cinsights serveOpen http://localhost:8100. See the getting started guide for the full walkthrough.
| Source | What it reads | Best for |
|---|---|---|
| Local | ~/.claude and ~/.codex session files |
Try in 2 minutes. No external dependencies. |
| Entire.io | Git-based checkpoints across Claude Code, Cursor, Codex | Cross-agent and cross-machine coverage for teams. |
| Phoenix | Arize Phoenix traces | Centralized team observability. |
- Getting started - install, configure, first run
- Concepts - pipeline, quality metrics, scoring, insights, digests
- How it works - what data goes to the LLM, what stays local, cost breakdown
- Configuration - env vars, config file, CLI reference
- FAQ - common questions and troubleshooting
- Sources: Local · Entire.io · Phoenix
- Self-hosting - run cinsights on your infrastructure