Studio
The workbench where everything is tuned, reviewed and managed
Agents, skills, integrations, schedules, runs and files in one place. Everything the chat builds is there, with fine-grained settings.
An agent's settings
Every setting has its place, no code
An agent's Settings sort everything into three groups. You know where to look, and an agent created by the chat opens here to be refined.
- Explorer: the agent's files, including its instructions, and its versions.
- Configuration: the model, the proxy, default inputs, connections and schedules.
- AFPS package: skills, integrations, tools and the input and output schemas.
The chat builds, Studio keeps control
Both work on the same agents, with the same rights.
Built by the chat
- Agentscreated by chatting
- Skillswritten from your methods
- Integrationsyour connected tools
- Schedules"every Monday at 8 am"
You keep
- Versionsdraft, published, restorable
- Rights per rolewho builds, runs, sees
- Run historyevery step traced
- Files producedreports, drafts, exports
Settings
Three levels of settings, each in its place
What applies to the whole organization, what belongs to one team and what only concerns you are set in three separate places.
- Organization: users, roles, workspaces, AI models and billing.
- Workspace: its members, its authentication, its API keys and its webhooks.
- Preferences: your personal model keys and MCP access for your coding tools.
What it changes
For your teams
- The dashboard shows recent runs and what failed at a glance.
- Each agent setting has its place: files, model, connections, skills.
- What the chat built shows up here, ready to be refined.
For the organization
- One place for members, roles, models and integrations.
- Each team works in its own space, with its members, API keys and webhooks.
- Every version is visible: draft, published version, comparison.
Frequently asked questions
Do I need to know how to code?
Studio or chat, which one?
What does the dashboard show?
Where are the files produced by agents?
Let's see what it would look like on your side.
Try it on your own in a few minutes, or take thirty minutes with us to scope a first use case.
Let's talk about your case
Thirty minutes with us to scope a first use case and its gain.
Read the code
Apache 2.0. Your technical team can read it all, install it all, keep it all.