Summary
Edgee launched a team layer on April 28 that gives engineering leaders per-repo and per-PR visibility into how Claude Code, Codex, and OpenCode are being used. The product combines spend attribution, seat controls, GitHub integration, and automatic open-source-model fallback when a developer hits limits or a provider fails.
What changed
Edgee added a team-management product with GitHub-linked usage attribution, spending caps, alerts, and automatic OSS fallback for AI coding workflows.
Why it matters
As coding assistants move from individual experiments into shared infrastructure, orgs need budget controls and operational visibility, not just token compression. Edgee Team turns agent usage into something engineering leadership and finance can actually govern.
Evidence excerpt
Edgee says Team management gives engineering leaders visibility into Claude Code, Codex, and OpenCode usage, including per-repo attribution, spend caps, and automatic OSS fallback.