Builder Portal
A self-service dashboard for developers. View your budgets, efficiency and safety scores, session history, projects, and manage your own access tokens — without needing admin access.
Overview — budgets and scores
The Overview tab shows your current session status and spend against your configured limits.
Budget
Three budget tiers are shown as progress bars:
- Developer budget — your individual daily or monthly spend limit.
- Team budget — shared limit across your team; your share of the pool is shown.
- Total budget — combined view of developer + team spend.
If your budget is running low, click Request more budget to submit a budget increase request to your admin. You'll see estimated time until exhaustion based on your current spend velocity.
Efficiency score
AIControls grades your AI usage across four dimensions:
| Signal | What it measures |
|---|---|
| Cache hit rate | How often your prompts hit the provider's prompt cache |
| Context efficiency | How much of your context window is productive content vs. noise |
| Model appropriateness | Whether you're using a heavier model than the task requires |
| Prompt repetition | Whether you're re-sending the same content across turns |
A letter grade (A–F) summarises the four signals. Lower grades surface specific recommendations to reduce token waste.
Safety score
Tracks policy denials in your recent sessions. A high score means your requests are consistently within policy. Repeated denials on the same tool or operation appear as actionable items — click through to see which policy is firing and why.
Context health
A breakdown of your active session's context window: fill percentage, loop score, latency rot, verbosity, and repeat reads. High loop scores or verbosity suggest starting a new session or compressing context.
Access tokens
The Access Tokens tab is where you create and manage Personal Access Tokens (PATs). PATs are how your AI tools authenticate to the AIControls proxy — they replace direct API keys on your machine.
Each token has a name identifying the tool or machine it's used from, an expiry (30 to 365 days), and a status — tokens marked new have never been used. The token value is only shown once, at creation time.
After creating a token, the setup panel shows ready-to-paste configuration for your tool. Pick which AI product you're setting up (Claude, ChatGPT, Copilot, Azure), and — when your workspace supports both — how you authenticate:
| Mode | How it works |
|---|---|
| Proxy mode | Your AI tool routes all LLM and MCP traffic through the AIControls proxy using the organization's managed key. No personal API key or subscription needed — the token you paste is your PAT. Full governance coverage. |
| Passthrough mode | Your AI tool keeps its own credentials (a claude.ai subscription or personal API key); AIControls intercepts and adds governance on top. Lower setup friction. |
If your workspace has both modes enabled, the panel defaults to Proxy mode — the path that works even without a personal subscription or API key. Switch to Passthrough mode with one click if you'd rather use your own credentials.
See the Claude Code, Cursor, Codex, or GitHub Copilot pages for tool-specific connection details.
Sessions
The Sessions tab lists all sessions associated with your developer identity — status, purpose, spend, and call counts. Each row opens a session detail drawer with the same insights administrators see, scoped to your own sessions:
- Overview — status, purpose, model, spend against budget, and call counts.
- Activity — a timeline of every tool call and LLM request, with websites contacted, documents read, and data queries.
- Insights — detected intent, areas of the codebase touched, attributed tickets, quality signals (committed, verified, focus), and an AI-generated summary of what was worked on.
- Optimization — an efficiency grade, per-model cost breakdown, cache savings, and ranked recommendations for reducing spend.
- Context — context window fill, a token breakdown by segment, and per-turn growth.
- Security — content-safety findings (credentials, PII) and unrecognized tools detected in your session, so you can self-correct before an administrator has to follow up.
Projects
The Projects tab aggregates your session history by project (repository path), with per-project cost, token usage, and activity trends. It's populated automatically from your coding agent's session metadata — no manual tagging required.
Project data appears after your first coding-agent session. If the table is empty, complete a session and refresh.
User profile and activity
The User tab shows your profile (display name, password, role — role changes require an admin) and work patterns derived automatically from your session history: commit cadence, work area focus, language breakdown, and tool usage.
Connected accounts
The Connected Accounts tab manages per-developer credentials for upstream datasources (databases, APIs, internal services) that your AI tools access via MCP. Two types are listed:
- Stored credentials — OAuth tokens or API keys you've connected. Shows status (Connected, Expired, Disconnected), token prefix, and expiry.
- Client-configured — credentials passed as custom headers from your AI tool. AIControls doesn't store these; the card shows the expected header name and setup instructions.
Policy exceptions
The Policy Exceptions tab shows exceptions that have been granted for your identity — operations that would normally be denied by policy but have been explicitly approved. Exceptions are granted by admins and have an expiry date. You cannot create exceptions yourself; they're requested via the HITL approval flow or directly from your admin. See Approval Workflow for how a request moves from submission to grant, including requests that need more than one approver to sign off.