AI Workforce · Module
Agents Studio
Define, test, release and supervise every Digital Employee, skill by skill
Agents Studio is where each Digital Employee is defined, tested, versioned and supervised. Skills are Actions of subscribed modules, autonomy is earned per skill on evidence, and production behaviour changes only through a released version.
The home of every agent
Agents Studio, planned for W1, is where a Digital Employee is defined and supervised. An agent definition holds role, mission, responsibilities, an out-of-scope list, class (executive, manager, specialist or utility), a mandatory owner, a supervisor, skills, knowledge scopes, a model policy, a compute budget, a schedule, escalation rules and a persona reference. Agents are created from a Store template version, with template fields locked and tenant fields editable, or drafted from a role description.
Skills are Actions
A skill is an Action of a subscribed module. The skill picker hides Actions the tenant is not entitled to, entitlement is rechecked at every run, and a lapsed module pauses the skill with a reason. Each skill stores its own autonomy level (A0 to A4), maximum risk tier, conditions and limits. Content from emails, web pages and documents can never authorise R3 or R4 Actions. Before R2+ skills that use connector data, connector health is checked and a degraded connection hands off to a human.
Earned autonomy
The autonomy ladder engine promotes and demotes per skill, and every change is audited. In shadow mode (A1) the agent proposes and people act, and agreement is scored per decision and per field. Eval cases are generated from Action examples and tenant golden tasks, with at least 20 per skill for template agents. The Eval Coverage Score across seven dimensions gates promotion. Automatic demotion follows a critical eval failure, an S3+ incident, an undo spike or a repetition loop, and loop, storm and runaway detectors stop a run and open an incident.
Versions and testing
Agent versions are immutable and pin prompts, skills, pack versions, model policy and persona. A test console runs a draft against a sample input or simulator scenario and shows steps, retrieval, tool calls, policy decisions, cost and latency. Canary releases with automatic rollback, version diffs with eval and cost comparison, and YAML export are planned.
Supervision
Each agent has a desk: current queue, in-flight runs, recent decisions, autonomy per skill, budget burn and incidents, with pause, demote and budget controls. If the owner leaves or loses a permission, the agent loses it too and pauses after a grace period. An "asks from agents" inbox lets an agent request an Action it may not take, and the human executes it. Hindi and Tamil working languages are enabled only after per-language evals pass.
Features
What Agents Studio includes
Agent definition
Role, mission, out-of-scope list, class, mandatory owner, supervisor, skills, scopes, model policy, budget and schedule.
Create from template or description
Template versions with locked fields, or a drafted agent from a role description for human editing.
Skills are subscribed Actions
Unentitled Actions hidden; entitlement rechecked every run; lapsed modules pause the skill.
Per-skill autonomy and risk
A0 to A4, maximum risk tier, conditions and limits per skill.
Tainted-input rule
Content from emails, web and documents cannot authorise R3 or R4 Actions.
Autonomy ladder engine
Audited promotion and demotion rules per skill.
Shadow mode
The agent proposes, people act; agreement scored per decision and per field.
Eval generation and Eval Coverage Score
At least 20 cases per skill; seven dimensions gate promotion.
Automatic demotion and run detectors
Critical failures, incidents, undo spikes, loops and runaway cost stop or demote.
Immutable versions
Pinned prompts, skills, packs, model policy and persona; canary release and rollback.
Test console
Steps, retrieval, tool calls, policy decisions, cost and latency for a test run.
Agent desk
Queue, runs, decisions, autonomy, budget burn and incidents with pause and demote controls.
Owner change safety
Agents lose permissions with their owner and pause after a grace period.
Asks from agents
Reverse delegation inbox where people execute Actions the agent may not take.
Workflow
Define to production
- 1
Create an agent from a template or description
- 2
Pick skills from subscribed Actions
- 3
Set knowledge scopes, model policy, budget and owner
- 4
Run the risk assessment and approval in AI Governance
- 5
Release a version into shadow mode
- 6
Promote skills as evidence passes the gates
AI
AI skills and Digital Employees
Agent from description
Drafts the definition and eval cases; never activates it.
Skill suggestion with permission diff
Shows which Actions need a module or exceed the owner's permissions.
Promotion readiness
Assembles evidence and names the missing criterion.
Test console diagnosis
Explains in plain language why a run took its path.
Handoff note drafting
Writes structured handoff notes for receiving humans.
Digital Employees that use this module
- AI Agent Governance Auditor
They act through the same governed Actions as people; risky steps wait for approval.
Frequently asked questions
Can an agent act on day one?
It starts in shadow mode, proposing while people act. Autonomy rises per skill only after evidence passes the gates and a person approves.
What happens if I cancel CRM?
Skills that use CRM Actions pause with a reason. An agent can only use Actions of modules you subscribe to.
Can agent behaviour change silently?
No. Production behaviour changes only through a released, immutable version.
See Agents Studio in your workflow
Tell us about your team and the outcomes you want. We will walk you through the apps, the Digital Employees and the plan for your industry.