My Agents
My Agents is where you find the AI assistants your administrator has published for you. Each assistant has a name, a description and a way of speaking, and you can open one to start a conversation.
Names you will see
The same feature appears under different names:
| Where | Name |
|---|---|
| Left sidebar | My Agents |
| The page itself | Your Assistants |
| Studio (for administrators) | Personas |
In this guide, an assistant is the same thing as a persona.
How it differs from other features
- Agent Force AI employees are members of a team that does jobs for you. An assistant is a reusable identity. When someone hires an AI employee, they can start from an assistant as a template. See AI Employees.
- Skills are separate abilities. An assistant only lists which skills it may use.
- Chat is the full conversation experience. See Chat.
Open My Agents
Click My Agents in the left sidebar. You can also open it from See all on the Home page's "Your Assistants" section, or from a conversation in My Work that uses an assistant.
The list page
The title is Your Assistants: "AI assistants built for your work. Click one to start a conversation."
Each card shows:
- A round avatar with the first letter of the name.
- The name and a short description (three lines at most).
- A badge such as 3 skills and a badge such as 2 specialists, when it has them.
- The line "Runs on your default model (BYOK)".
- A pencil icon (Edit this assistant) that opens the assistant in Studio. Saving changes still needs permission.
Click a card, or press Enter on it, to open the assistant.
| Situation | What you see |
|---|---|
| Loading | Three grey placeholder cards |
| Nothing published | "No assistants available — Your administrator hasn't published any assistants for your account yet." |
| The list could not load | The same empty message. Try again later |
The page shows up to 50 assistants and has no search, filters or sorting.
Which assistants you see
- Only published assistants. Drafts are hidden.
- Public assistants are visible to everyone in your organization.
- Personal assistants are visible only to the person who made them.
- Assistants shared with a project do not appear on this page yet.
- The "Access scope" roles that an administrator can tick do not currently limit who sees an assistant.
Open an assistant
Click a card to open /workspace/personas/(id).
The page has a breadcrumb (Nexus › Your Assistants › (name)), a Back to Your Assistants link, a header with the avatar, name and description, a message area, and a message box ("Message (name)…") at the bottom.
Type a message
Click the message box and write your message. Press Enter to send, or Shift+Enter for a new line.
Wait for the reply
Three bouncing dots show while it works.
A new conversation starts with "Start a conversation. (name) is ready to help." Opening the page with a saved conversation link (?session=…) shows that conversation's history.
What works today
Use an assistant in Chat
For real answers, attach the assistant to a chat.
Open Chat
Click Chat in the sidebar and open or start a conversation.
Open the context panel
Click Show context panel in the chat header.
Pick the assistant
In Active attachments, find the Persona row and choose an assistant. If there are none it says "Create one under Personas."
Screenshot placeholderScreenshot to add: The Persona row in Active attachments with an assistant selected.
See Tool and skill modes for the other rows in that panel.
For administrators: where assistants come from
Assistants are created and published in Studio → Personas (/personas).
| Field | What it is |
|---|---|
| Name | Required. The only mandatory field |
| Description | One sentence on who the assistant is and when to use it |
| Visibility | Personal (only you), Public (everyone in the organization) or Project |
| Role archetype | Executive, analyst, coach, support, compliance or custom |
| Voice / tone | None, concise, detailed, empathetic or formal |
| System prompt template | Instructions for how the assistant behaves |
| Communication preferences | Length, formatting and an escalation threshold (0 to 100, default 70) |
| Brand voice anchors and Refusal patterns | Example phrases, and triggers with responses |
| Knowledge bases, Governance policies, Skill access | Lists of IDs the assistant may use |
| Access scope | Developer, operator, viewer or end user |
- Save Draft keeps it hidden. Publish makes it available and saves a numbered version. Unpublish returns it to a draft.
- Five templates can pre-fill the editor: Customer Support Agent, Code Assistant, Data Analyst, HR Assistant and IT Helpdesk.
- Test drive tries the system prompt on its own, without tools or knowledge. It may show "(empty response)" because of a known issue.
- The Channels tab can switch on Workspace, Microsoft Teams, Web Widget, Public URL and API, but no channel is actually deployed yet.
- Only the author or an administrator can edit, publish or delete an assistant.