Three ways to use Agentivity
There are two moments with Agentivity: building a solution, and using it. This page shows the ways to do each, and who does what.
Two roles
Section titled “Two roles”- The person who builds. They know the job to be done. They work in the Studio: they describe, build, test and adjust.
- The person who uses. They have a request. They launch the solution, answer when it asks them something, and receive finished work. They do not need to know how it is built.
In a small company these can be the same person.
Way 1: describe it to the Assistant
Section titled “Way 1: describe it to the Assistant”You say what you need, in your own words, as you would to a colleague. The Assistant asks what it needs to know, shows a plan, then builds a draft: an agent, a team or a workflow. You look at the draft, ask for changes, and save it when it suits you. Nothing is added to your workspace until you save.
This is the fastest way to start, and it needs no technical knowledge.
See Build your first team with the Assistant.
Way 2: build it by hand in the Studio
Section titled “Way 2: build it by hand in the Studio”You create the agent, the team or the workflow yourself, and you set every part: the role, the instructions, the model, the members, the steps. You have full control.
The two ways work together. What the Assistant builds is an ordinary agent, team or workflow: you can open it in its editor and change it by hand. And from an editor, you can ask the Assistant to explain or improve what you built.
See Create an agent, Create a team of agents and Create a workflow.
Way 3: give it to other people
Section titled “Way 3: give it to other people”Once a solution works, other people can use it. There are three ways, from the simplest to the most complete.
| How people reach it | What it is | What it takes |
|---|---|---|
| From the Studio | You open the solution and start it. It works, and it comes back to you when a decision is yours. | Nothing more. |
| A portal | One web page where people start the solutions you made available. | A web application to put next to Agentivity. |
| A VibeApp | An application that adapts to the person who uses it, with your team of AI specialists behind it. | For an application of your own: a developer, and the Agentivity SDK. |
In a VibeApp, the person sets the goal in their own words, and the application handles the rest: the right specialists work on each part, and the screens arrive when a choice is theirs. Trip Planner, one of the showcases, is a VibeApp. In that demo, the bookings and the payment are simulated.
An application does not build anything. It lists what exists, starts an execution, shows what happens and sends the answers of the person. Building stays in the Studio.
See What a VibeApp is and One app for one job, or one portal for all.
Which way to choose
Section titled “Which way to choose”- You are starting: use the Assistant.
- You know exactly what you want, or you want to adjust a detail: work by hand.
- Your colleagues or your customers must use it without seeing the Studio: plan a portal or a VibeApp.