Part of the TeamAI CLI Usage Guide.
teamai pull commits session and usage counts into the team repo, and teamai workflow commits run records. Turn that off with:
# teamai.yaml
usageReport: falseOne machine overrides it in that scope's config.yaml:
usageReportEnabled: falseteamai doctor says whether reporting is on and where that comes from.
See the team's week:
teamai digest╔════════════════════════════════════════════════════╗
║ 📊 Team AI Weekly Digest ║
║ 2026-10-05 → 2026-10-12 ║
╚════════════════════════════════════════════════════╝
👥 Active members: 4
📈 Session trends (7d vs prior 7d):
Session success: 71% → 80% · 18 ended
Avg prompts/session: 6.2 → 5.4
Avg active duration: 12m → 9m
Avg LLM request cost (est.): $0.042 → $0.031
Cache read share: 40% → 55%
Correction rate: 18% → 11%
🏆 Most Used Skills:
★★★★★ deploy-helper (42 uses)
★★★★☆ code-review (17 uses)
📈 Total skill invocations: 59
🔧 Unique skills used: 2
📝 Session Highlights:
Fix duplicate project-level Hook injection...
📚 New Learnings This Week: 1
• Port conflict on local preview
🤖 Session Autonomy (Human Intervention):
Team avg: 1.20 interventions/session (18 sessions, 22 interventions)
Breakdown: interrupt 8 · reject 6 · correction 8
💬 Lifetime Conversation & Token Usage:
Lifetime human prompts: 320
Lifetime tokens: 1.2M (input 400.0K · output 80.0K · cache read 700.0K · cache write 20.0K)
────────────────────────────────────────────────────
Generated by teamai digest
With no reported data yet, the command prints No team usage data available yet.
A skill use is counted when the agent calls its skill tool, reads a skill's SKILL.md, or the prompt names the skill: /code-review at the start of the prompt, $code-review in Codex, /skill:code-review in Pi. Only skills installed for the tool count, and each skill counts once per prompt. Paths such as /Volumes/External/project and URL components are not skill invocations. Previously recorded usage stays.