Crescendo Lab

Agent Lab · Agent Studio

Tested before go-live,
kept up by its team.

Start from a template, write its instructions and save test questions. Once they pass, publish it and colleagues use it on the web or in Slack. After that, the team that uses it makes the changes.

Want to look first? See how an assistant is built.

In plain words

Agent Studio is where AI assistants are built

Agent Studio is where AI assistants are built in Crescendo Agent Lab: write down who it helps, what it does and what it must never do, connect knowledge and systems, publish once the tests pass, and keep a version of every change after that.

Starting point
10 templates, or a blank assistant
Tests
Saved questions, rerun after every change; publishing can require them to pass
Versions
Every save is a version you can restore
Where it is used
Agent Lab web conversations and Slack
Permissions and budget
The same permissions, approvals and budgets as Agent Lab Platform
Cost
Free to sign up; an assistant's model spend is drawn from the workspace's credit

How it is built

From a template to live, in four steps

Every step except the name and the instructions has a default, so you get a first answer and adjust from there.

  1. Pick a template

    IT helpdesk, leave requests, expense claims, meeting scheduling and six more, or start from blank.

  2. Write the instructions

    Who it helps, what it does, and what it must never do. Write it the way you would brief a new colleague.

  3. Test it

    Save questions and good answers as tests and rerun them after every change. Publishing can require them to pass.

  4. Publish

    Before going live you see what is still missing: connections, knowledge, budget, a place to use it. Then publish to the web or Slack.

What an assistant is made of

Besides instructions, an assistant needs knowledge, tools and a schedule

Each is set up in Agent Studio and follows the same permissions.

Knowledge

Documents and Q&A. Search runs with the asker's permissions, so a document they cannot see is never quoted.

Connections

24 integrations added in one click; other systems connect over remote MCP.

Skills

Write a fixed procedure once as a skill, share it across assistants, and keep its version history.

Automations

Run an assistant on a schedule, such as a daily summary on weekdays at 07:30.

Versions

Every save is a version. Restoring one brings it back as a new draft; history is never overwritten.

Who can use it

An assistant can be private to you or shared with the whole workspace.

Who does what

The builders, the team that uses it, and IT each own a part

Once an assistant is live, changing its instructions does not mean going back to whoever built it.

The builders

Engineers, consultants or an internal solution team make the first version.

  • Pick a template, connect systems and knowledge
  • Write the tests that define a right answer
  • Publish the first version

The team that uses it

The people who know the work keep the assistant current.

  • When a rule changes, edit the instructions themselves
  • Rerun the tests, then publish a new version
  • Save a wrong answer's conversation as a test

IT

Sets the limits every assistant shares.

  • Which tools need approval and which never run
  • Budget caps for the workspace and each team
  • A record of every model call and approval

Agent Lab Platform

What an assistant may do is set by the platform

An assistant acts with the asker's own permissions, waits for approval before using a tool, and stops at the budget cap.

FAQ

Agent Studio questions

What is Agent Studio?
The part of Crescendo Agent Lab where AI assistants are built. Start from a template or a blank one, write its instructions, connect knowledge and systems, save test questions, and publish once they pass. Every change is a version you can restore.
Can someone who doesn't code build and adjust an assistant?
Yes. Instructions, test questions and knowledge are written in plain text. Connecting an internal company system usually needs someone with access to that system to set up the connection first.
Where do colleagues use a published assistant?
In Agent Lab's web conversations and in Slack: across a whole Slack workspace or in one channel.
How do I know a change to the instructions didn't break something?
Save questions and what a good answer contains as tests, and rerun them after every change. A workspace can require the tests to pass before publishing, and a conversation that went wrong can be saved as a new test.
Do agents written with another framework have to move into Agent Studio?
No. Agent Studio is one way to build an assistant. An agent you wrote yourself can call models through AI Gateway and gets the same budget caps, records and model allowlist. See how AI Gateway works
How do I start using Agent Studio?
Sign up free: a new workspace has Agent Studio from the start. An assistant's replies call a model, and that spend is drawn from the workspace's balance, so add credit or redeem a code first. If an older workspace does not have Agent Studio yet, contact us. See how credit works

Sign up free, or book a demo

  • We build, test and publish it together
  • See how permissions, approvals and budgets apply to it
  • If you want help rolling out, we plan the first assistant with you
Book a demo

Optional, helps us schedule faster