For Teams
Built for AI Coding Teams
For engineering teams and delivery heads at software services firms running several client projects and more than one AI coding tool. Coordinate the agents. Account for the work.
The problem
Three Questions Leads Can't Answer
These are coordination and record-keeping problems, not model problems. They get worse with every new tool, repo and client.
Which Client Did This Serve?
AI tool bills arrive per vendor and per organisation. Nothing on the invoice carries a client name.
What Did the Team Actually Run?
Every tool reports in its own console. Terminal runs and local models often appear nowhere.
Are They About to Collide?
Parallel agent sessions reach for the same busy files. Each worktree looks clean until someone tries to merge.
Client reporting
One Report per Client
Map repos and sessions to client engagements and export a per-client summary in minutes.
Client engagement summary
Sample data| Engagement | Repositories | Sessions | Providers | Reported usage | Estimated cost |
|---|---|---|---|---|---|
| Client A | payments-core, ops-admin | 38 | Local runner only | n/a | Infra only |
| Client B | storefront, driver-app | 21 | Anthropic, local | 18 of 21 sessions | Partial |
| Client C | marketing-site | 6 | OpenAI | 6 of 6 sessions | Estimated |
| Unattributed | None | 4 | Unknown | Unknown | Unknown |
Reported Usage
As the agent or vendor reports it.
Estimated Cost
Usage priced at your configured rates.
Vendor Billing
The invoice, reconciled against the other two.
Unknown stays unknown. Sessions without usage data are never counted as zero.
Working together
Everyone on the Same Page
Session Ledger
A record of every observed run: who, which agent, which provider, which repo and branch, how long, and usage where available.
Team Board
Who is running what across the team, with roles and permissions.
Launch Policies and Budgets
Allow-lists and budget checks applied when a session starts.
Agent Approvals
Agents can launch other agents. Every launch waits for a human yes.
Client-Scoped Boundaries
Index, memory, handoffs, skills and exports scoped per client, so one engagement can't retrieve another's context.
Shared-Server Install
Run Foxwel OS on your own office server for the whole team. Your hardware, your keys.
