What the React SDK offers, and how to work with it
Ce contenu n’est pas encore disponible dans votre langue.
This page is for developers. It is a map: what the SDK gives you, and where to look when you need more. The pages after it go into each part, with a starting point and a few lines of code.
The source code is the reference. These pages do not list every function.
The idea in one minute
Section titled “The idea in one minute”Your application does three things: it lists what can be launched, it starts an execution, and it shows what the execution sends. The SDK gives you a ready-made piece for each, so that most of your code is your own screens.
What you get
Section titled “What you get”| Part | What it does for you | Read |
|---|---|---|
| The client | Calls the server: list agents, teams and workflows, start an execution, answer a question, stop an execution, read past conversations, upload a file, read and write the rows of a Data Table. | List solutions and start an execution |
| The chat | A complete conversation: messages as they are written, the input box, a stop button, who is working, questions to the person, a notice when the connection is lost. | List solutions and start an execution |
| The team and the workflow, drawn | Shows the members of a team or the steps of a workflow, and lights them up as they work. | Show the team at work |
| Widgets | What an agent can show in the conversation besides text: charts, cards, a form, a choice, a date, a confirmation. Twenty-two are ready. | The widgets an agent can show |
| Your own widgets | A screen of your own that the agent fills in and the person answers: a hotel picker, a payment card, an order summary. | Add your own widgets |
| Themes | One object sets the colours, the shapes and the font of every piece of the SDK. Ready-made themes are included. | Give the app your brand |
The SDK has no screen to create or change an agent, a team or a workflow. That stays in the Studio. See How a VibeApp talks to Agentivity.
Where to find the information
Section titled “Where to find the information”Everything is in three public repositories at github.com/agentivity-labs.
| You look for | Open |
|---|---|
| The list of everything the SDK exports | agentivity_sdk_react, file src/index.ts. It is sorted by part, with a title for each. |
| What a component or a function does | The comment above it in the source. Your editor shows it when you point at the name. |
| An example of use | The folder test of the SDK: one file per component, with small, working cases. |
| A complete application for one job | agentivity_sdk_showcase_tripagency: the Trip Planner. Chat, team view, three custom widgets, themes. |
| A complete application for any solution | agentivity_sdk_showcase_solutions: the portal. List of solutions, chat, past conversations, team and workflow views. |
| What the server accepts | The routes of the API. The SDK calls them for you. |
The two example applications are the best starting point. Each is small: a handful of files.
A way of working
Section titled “A way of working”- Build the solution in the Studio first. Make the agent or the team work in the Execution view before you write any code. An application cannot fix a team that does not work.
- Start from an example application. Copy the portal, or the Trip Planner if your application does one job. See Start a VibeApp with the React SDK.
- Point it at your server and your solution. Check that the conversation works with the ready-made pieces.
- Change what the person sees. Your layout, your brand, then your own widgets where the ready-made ones do not fit.
- Change the team, not the code, when the job changes. A new step or a new specialist is added in the Studio. The application follows.
- Read the checks before you put it online. See Before you put a VibeApp online.
Work with an AI coding assistant
Section titled “Work with an AI coding assistant”The SDK and the two example applications are published with their source. That makes them easy to use with an AI coding assistant: it can read the real code instead of guessing.
- Give it the repositories. Clone the SDK and one example application next to your project, and let the assistant read them.
- Tell it where to start.
src/index.tsfor what exists, the example application for how the pieces fit, the foldertestfor small cases. - Give it the three rules of this section. The application reads, runs and watches, and does not build. The application and the server share one address. The server has no login.
- Ask for one screen at a time, and run it against your server after each change.
The assistant writes the code. You still check the result against a real execution: only an execution shows what your team really sends.
The SDK for Flutter
Section titled “The SDK for Flutter”agentivity_sdk_flutter has the same parts for Flutter applications. These pages use the React SDK.