Skip to Content
persona

Concepts

The words Persona uses, from organizations and projects down to links and chats.

A few nouns cover Persona.

Organizations

Everything lives under an organization, your workspace. Sign-in and organizations come from Clerk. Every request acts for one organization, and every lookup is scoped to it. An id from another organization answers 404, the same as an id that does not exist.

Every member of an organization can do everything in it for now. There are no role checks yet. API keys belong to the organization too.

Projects

A project holds personas, and the WhatsApp numbers and Telegram bots that reach them. A project is one product, brand or team.

A new project comes with its first persona, named after the project. Deleting a project deletes its personas, its numbers and bots, and every chat link on them.

Personas

A persona is an AI agent with its own setup: a model, instructions, skills, MCP servers, apps, a vault, files, notes, automations, webhooks and triggers. Personas goes through each part.

Creating a persona is one database insert. It answers as soon as the request returns. There is no machine to start and no status to wait for.

The persona is the unit of everything. Its memory, files and automations belong to the persona, not to the organization and not to one person. Everyone who talks to a persona shares its memory. When people need privacy from each other, each gets a persona of their own.

A channel is where people reach a persona: WhatsApp, Telegram or the web.

On WhatsApp and Telegram, a link ties one chat to one persona. A chat is one person on one number or bot. A person links their chat by sending a link code: eight characters, good once, for 24 hours. A new code moves the chat to another persona.

Persona has shared WhatsApp numbers and a shared Telegram bot, which serve every project. A project can also add numbers and bots of its own, which serve only that project's personas. See Channels.

Chats

Every conversation is a session, and the eve runtime keeps its whole history. Persona records which sessions exist, which persona each belongs to and where it came from: web, telegram, whatsapp (every WhatsApp number, on Meta or on the legacy Kapso), automation, webhook or trigger, with a copy of every message.

WhereOne session per
Telegrambot, chat and persona
WhatsAppnumber, person and persona
Webchat that the app or a client starts
Automationrun
Webhookcall
Triggerrun, over the app events that waited for it

A Telegram or WhatsApp chat is one long session, until seven idle days end it and the next message starts a new one. Linking the chat to another persona starts a different session. Linking it back continues the old one.

Memory

Each persona has one memory, kept by Supermemory. At the start of a turn the persona recalls what matters for the message. At the end of a turn the conversation is saved. The persona can also save or forget a memory on purpose. Automation, webhook and trigger runs neither recall nor save memory: a run works from its task and its tools.

The persona's notes are separate: texts it writes, finds and reads on purpose, such as a list or a draft.

The vault

The vault holds credentials: a login, a card or an API key. A credential has a title, a description of when to use it, and fields. Each field says if it is secret.

Values never pass through the chat. The person fills them in on a form behind a short link, and the values are stored apart from the credential. The API and the persona's tools return only which fields are filled, never a value.

On this page