An agent is a versioned artifact, not a prompt in a text box.
AEGIS Studio is designed for creating, testing and publishing agents with the same discipline as software. Forms and API come first, with visual authoring to follow.
− Review overdue invoices and propose payments.
+ Review overdue invoices. Propose payments only for vendors verified in this run.
planning-default
− records.search
+ records.search, vendor.verify
− Read AP records
+ Read AP and vendor records
20 turns, $0.50 per run
Published versions never change. Each run pins the exact version it used, so history stays explainable. Sample data.
Know exactly what changed.
When an agent's behavior shifts, the first question is what changed. Here, version 4 adds a tool and a stricter instruction after version 3 proposed a payment to an unverified vendor.
A published version is immutable and has its own digest. Production runs can point only to published versions.
Key capabilities
What goes into an agent.
Instructions
Versioned text with variables, reviewed like code.
Model route
A reference to a route in Intelligence, never a hardcoded vendor.
Tool grants
Which registered tools this agent may ask for. A grant is necessary but does not by itself permit an action.
Requested authority
The Mandate this agent expects. Orchestrator derives its real Mandate from the plan and rejects anything wider.
Limits
Maximum turns, a budget per run and timeouts.
Templates and environments
Starting points, and separate dev, staging and production. Planned for later phases.
Example workflow
From draft to production.
| Release | Scope |
|---|---|
| Phase 1 | API and form-based configuration, immutable versions, single-agent test run |
| Phase 2 | Visual authoring, templates, mock tools, saved tests |
| Phase 3 | Environment promotion rules, Git sync |
Draft
Write the instructions and select a route and tools.
Test against mock tools
Run with synthetic tools so nothing real is touched and no credentials are needed.
Review the diff
See how this draft differs from the current version.
Publish
Create an immutable version with its own digest.
Promote
Move it to production under the rules of that environment.
Technical explanation
Studio has no special powers.
Every Studio action is a call to the public API, and an agent created in Studio is identical to one created in code. That keeps version control, CI and review available to teams who prefer them, and it means the visual tool can never become a side door around policy.
Related capabilities
Help shape the authoring experience.
Early access partners will influence what Studio becomes first.