> ## Documentation Index
> Fetch the complete documentation index at: https://docs.exterview.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Agent Studio

> Where an administrator configures, watches and improves the digital workforce: AI Employees, Scoring Logs and the Activity Log today, with the Agent Catalog, staged rollout, the Swarm Control Plane and fairness gating Upcoming.

## Purpose

**Agent Studio** is where an administrator runs the digital workforce: configuring AI Employees, watching how they perform, and improving them under change control.

Five things happen here, in a loop.

```mermaid theme={null}
%%{init: {'theme':'base','themeVariables':{'primaryColor':'#EEF2FF','primaryBorderColor':'#4B6CFE','primaryTextColor':'#0F172A','lineColor':'#64748B','clusterBkg':'#F8FAFC','clusterBorder':'#E2E8F0'}}}%%
flowchart LR
  L([Library]) --> B([Build: configure])
  B -.-> T(["Test (Upcoming)"])
  T -.-> R([Run])
  B --> R
  R --> G([Govern])
  G --> B
```

*Solid lines are Available today. Dotted lines are Upcoming: staged trial and pilot testing before a change governs real work.*

<Info>
  **Status.** In Exterview today, Studio lives in **Settings → Setup →
  Operations**: AI Employees, Agent Skills and Scoring Logs. The Agent Catalog
  and Agent Lineage are Upcoming. Each section below says what is Available and
  what is Upcoming.
</Info>

## Build

**Available.** Configure how agents work for your organization: the scoring criteria, the hiring pipeline and which agent runs each stage, agent skills and knowledge, and the agent's role for each job. No engineering work, and no blank canvas.

Upcoming: composing your own AI Employees from the [Agent Library](/smaya/capabilities), each configuration a new version with an author, a reason and a diff.

## Deploy

<CardGroup cols={2}>
  <Card title="Locked while in flight" icon="lock">
    **Available.** A job's scoring configuration locks so criteria never change underneath candidates already in progress. Everyone assessed for the job is assessed on the same criteria.
  </Card>

  <Card title="Staged rollout" icon="git-branch">
    **Upcoming.** Move a version through trial, pilot and production, so a
    configuration proves itself on real work before it governs real decisions.
  </Card>

  <Card title="Two-person change control" icon="user-check">
    **Upcoming.** A change to a live AI Employee is made by one person and
    approved by another, and the approval is part of the permanent record.
  </Card>

  <Card title="Rollback and suspend" icon="rotate-ccw">
    **Upcoming.** Restore any version in one action, and suspend any AI Employee without affecting the others.
  </Card>
</CardGroup>

## Monitor

<CardGroup cols={2}>
  <Card title="Activity" icon="activity">
    **Available.** The Activity Log records every action on your account, by a person or by an agent.
  </Card>

  <Card title="Approvals" icon="clipboard-check">
    **Available.** Every write an AI Employee proposes waits on an approval card,
    and the answer is recorded.
  </Card>

  <Card title="Reports and schedules" icon="inbox">
    **Upcoming.** Work that needs a person lands in the [Agent
    Inbox](/smaya/agent-inbox).
  </Card>

  <Card title="Swarm Control Plane" icon="gauge">
    **Upcoming.** A live view of every role run: candidates per stage, calls made, interviews booked and held, reports pending, and exceptions.
  </Card>
</CardGroup>

## Evaluate

<CardGroup cols={2}>
  <Card title="Quality" icon="target">
    **Available.** Automated checks run on every scored output, and their results show in **Scoring Logs**. Upcoming: blocking a version that scores worse than the one in production.
  </Card>

  <Card title="Fairness" icon="scale">
    **Upcoming.** Outcome rates monitored across groups at cohort level, with a configuration change that moves them adversely blocked before release.
  </Card>
</CardGroup>

## Improve

**Upcoming.** Outcomes feed back. Overrides become proposed criteria changes, and each one passes through the same versioned, approved, evaluated path before it applies. Nothing self-modifies in production.

## What is captured

<CardGroup cols={2}>
  <Card title="The decision trail" icon="file-check">
    **Available.** Every score override carries a stated reason, every Decision change asks for a reason, and each score records the model and prompt that produced it. Upcoming: the Decision Room, one permanent record per decision.
  </Card>

  <Card title="The Fairness Register" icon="scale">
    **Upcoming.** A continuous, cohort-level view of outcome rates by stage and group, with alerts when a change moves them.
  </Card>
</CardGroup>

Both are described in [Governance & Control](/smaya/oversight).

## FAQs

<AccordionGroup>
  <Accordion title="Who uses Agent Studio?">
    An administrator or operations owner in your organization. It is a business configuration surface, not a development environment.
  </Accordion>

  <Accordion title="What happens to work already running when we change something?">
    A job's locked scoring configuration does not change underneath candidates
    already in progress. A change applies to new work.
  </Accordion>

  <Accordion title="Is Agent Studio available today?">
    The configuration, AI Employees, Scoring Logs and Activity Log are Available in Exterview. The Agent Catalog, Agent Lineage, the Agent Inbox, staged rollout, two-person change control, the Swarm Control Plane and fairness gating are Upcoming.
  </Accordion>
</AccordionGroup>

## Related

<div className="kb-links">
  *   <span className="kb-ico">
        <Icon icon="id-card" />
      </span>
    [AI Employees](/smaya/ai-employees). What you are configuring here.
  *   <span className="kb-ico">
        <Icon icon="shield-check" />
      </span>
    [Governance & Control](/smaya/oversight). The evidence artifacts in full.
</div>