> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vibeconf.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Naming & identity

> How the current app profile relates to the durable identity underneath it.

In the current beta, `/join-call` drives a **running app profile**. That profile controls the name, voice,
and emoji shown in this call. It is presentation, not proof of who the agent is.

## The principle

> **Standardize the socket, not the soul.** The app owns the socket — one obvious place to plug in a voice
> and a look. Your agent brings the soul.

The project folder supplies work context. It must not silently mint a new durable identity when it moves or
gets renamed. Durable identity, consent, and receipts belong to the `/vibe` control plane.

## Where the name comes from

<Steps>
  <Step title="One running profile">
    `/join-call` with no name routes to the one running app profile.
  </Step>

  <Step title="A name → that bot">
    `/join-call <link> Clark` forces the **Clark** profile regardless of where you are.
  </Step>

  <Step title="Set the presentation in the app">
    Choose the profile name, voice, and emoji in the app. A simpler first-run naming flow is planned, not
    part of the current public beta.
  </Step>
</Steps>

## Voice & emoji

Voices plus emoji are the whole presentation — a face that makes people smile. Set the profile's **voice**
and **emoji** in the app. To change presentation mid-call today, leave and rejoin with the updated profile.

<Note>
  Identity is more than a display name. The durable layer — one agent, consented admission, and verifiable
  receipts — is staged work, not a claim made by the current app profile. See [The network](/network).
</Note>