Connecting the app to an ibl.ai organization is **one click in the browser**, or two pasted values. The API token is written straight into the project's environment files and **never passes through the chat** — the coding agent builds with it but never sees it.
**Thirty seconds after you sign in, you are chatting with your own agent**, with users, an admin area, custom user and organization settings, memory, analytics and billing already wired.
## What does the Agentic Vibe starter app include?
The starter is a real application, not a demo page. After sign-in, the home page is a conversation with your agent, with suggested follow-ups, voice input, Canvas and Memory in the composer.
Out of the box, the starter wires up:
- **Sign-in** with ibl.ai SSO, pinned to your organization.
- **A home page that is a chat** with your agent, `/agents` to browse, and `/setup` to pick or create one.
- **Users and admins** — a profile, a User/Admin switch, and an admin area for people, invites, roles, analytics, billing, memory and organization settings.
- **Custom data per user and per organization**, stored on the platform — no database of your own to run.
- **Tests** in Vitest and Playwright, plus a server helper for anything the components don't cover.
The same app reads differently to each person. An administrator sees eight sections; a user sees Home, Agents and Profile. The switch in the top right moves between the two views.
## How do admins manage users in an app built with Agentic Vibe?
Through the platform's own management screens, mounted in your app. The Management panel has seven tabs — Users, Groups, Roles, Policies, Teams, Alerts and Applications — with search, invitations, a role per person and a policy set per person.
None of this is a mock-up to be rebuilt later. Roles and policies are the platform's role-based access control, so what you grant in your app is enforced by the same backend that runs [Agentic OS](/product/agentic-os).
## What are the two skill families in Agentic Vibe 2.0?
Version 2.0 merged the separate `iblai/api` toolkit into `iblai/vibe`, so **one install now carries two families**. Skills named `iblai-vibe-*` mount a visual component in your app; skills named `iblai-api-*` do the same work headlessly over REST, for a script, a CI job or your own backend.
| Kind | What it produces | Skills |
|---|---|---|
| ui | A screen in your app — a page, tab, dialog or widget | 54 |
| api | The exact REST contract, a script or a server route | 66 |
| guide | A decision page that routes you to the right skill | 15 |
| ops | Builds, tests, deploys, releases and upgrades | 11 |
| security | Authorized-use security reviews | 8 |
| Total | One install | 154 |