# Customize Agents > Four tiers of agents in one picker. - Area: Desktop, mobile and web - Plans: All plans - Last checked against the product: 2026-09-30 - Web page: https://agentsroom.dev/docs/customize-agents ## What it does Four tiers of agents in one picker. **Built-in roles** (14: DevOps, Fullstack, Frontend, Backend, Architect, QA, Marketing, PM, Security, Mobile, Git, SEO, i18n, Brainstormer) plus a **Custom** role whose persona you write. **Experts** from The Agency, a catalogue of 260+ specialists. **Your own agents**: name, category, description, vibe, system prompt and tags, stored at account level so they follow you in every project, with a server-generated avatar and an auto-translated name and description. **Community agents**: agents other users published, reviewed by moderation, credited to their creator's public pseudonym. AgentsRoom also detects agent definitions already on disk (the markdown files with frontmatter your CLI uses, in the project and in your home folder) and offers to import them. ## Where to find it - In a room, **Add agent** opens a casting screen. Its search bar ("Who joins the team? A role, an expert, one of your agents…") returns results grouped as **Your agents**, **Built-in team**, **Experts**, **Community**, **In this project** and **Teams**; before you type, a wall of faces lets you pick one directly. Links under it: **Browse the full catalog**, **Run a team**, **Import from disk**, and **Help me choose an agent** (the [Agent Suggestions](https://agentsroom.dev/docs/agent-suggestions.md) advisor, which here places its pick on the stage instead of creating the agent). - Once someone is picked, the stage shows the avatar in the agent's color with the name field under it, a pencil (**Change role or look**) with a **Role** tab and a **Look** tab, and engine cards: **Provider** (the account is named under it), **Model**, **Reasoning** (only when the model has that lever) and **Workspace**. **Advanced options** opens a separate panel whose badge counts what you changed: **Who gets this agent** (**Team**: saved in the project's agents file and committed, **Only me**: a personal gitignored file), **Capabilities**, **System Prompt**, **Skills & connections**, **CLI launch**. The button reads **Add **. Since 2026-09-30. - **Browse the full catalog** opens the full picker: Core Team / Specialists, **Experts · The Agency**, **Community**. The first three sections carry a **(Tech)** qualifier after their name and a separator sits above **Community**, because only the community catalogue goes beyond software. - **Community** section: **Create your own agent**, **My agents**, the category grid, Popular / Recent sort, and **Top creators** aligned on the right, which opens the [Leaderboard](https://agentsroom.dev/docs/community-leaderboard.md) on its **Agents** board. - Categories are grouped in two families: **Tech & Pro** (Engineering, Product, Design, Marketing, Data, Writing, Ops, Other) and **Lifestyle** (Sport & Health, Learning, Lifestyle). Every category is shown even when empty; an empty one is a dashed **Create the first one** tile that opens the editor with that category already picked. - When an agent search finds nothing: "No agent matches", with **Create my agent**. - Site: the /agents page lists community agents with an install button that opens the desktop app. - Your public pseudonym: Settings > Account. ## How to use it Create a custom agent: 1. **Add agent** > **Community** > **Create your own agent**. Fill **Name**, **Category**, **What it does**, **Vibe** (optional), **System prompt**, **Tags** (optional). **Improve with AI** rewrites the prompt (undoable). 2. Save. The agent is **Private**, listed under **My agents**, usable in all your projects. 3. To share it with everyone, publish it: status becomes **In review**, then **Published** once approved (or **Rejected** with the reviewer's notes). Editing a published agent sends it back to review. Name it yourself: the name field under the avatar is optional and its placeholder shows the name the agent would get otherwise (its role, its template or the expert's name). A name typed there is treated as a deliberate rename and is kept: the title the agent gives its own conversation never replaces it. Leave the field empty and the card keeps the default identity, which the conversation title may take over. Since 2026-09-29. Share with a teammate: drag the agent card into the in-app chat (team channel or direct message); they import it in one click. Prompts, skills, dev commands and SSH connection metadata travel the same way, never secrets. Import on-disk definitions: when a project already has agent definition files, the room offers to import them (also reachable with **Import from disk** in **Add agent**); you pick which ones from a list, nothing is created behind your back. Since 2026-09-29 a description written on several lines in a file's front matter is read properly instead of arriving as `>-`, and nothing is pre-ticked in the list. Run a raw agent: **Advanced options** > **Capabilities** > **Minimal system prompt** (also in the agent's edit window). The agent then gets only its CLI and your project rules (CLAUDE.md, AGENTS.md); AgentsRoom keeps only what makes the tab title and notifications work, plus a team step's handoff and the skills you attached to that agent. No role, no tool guide, no project memory, no pre-filled commit message: MCP tools stay connected but the agent is not told how to use them. Applies at the next launch. Since 2026-09-30. How the persona reaches the agent: at every launch the agent's persona (the text of its built-in role, or your custom system prompt) is read again, so an edit you made to a role's text is honoured on the next launch. A persona of up to about 6,000 characters is written into the CLI's system prompt itself, which is re-sent on every turn, so the agent keeps its role after a context compaction. A longer persona, and the guide to the AgentsRoom tools, stay in a file the agent is told to open with its file-reading tool (not a shell command, whose output is cut short on a long file; a CLI with no such tool, like Codex, reads it through the shell in sections of about 200 lines) and to read again after every compaction. Since 2026-09-19. ## Settings - `minimalSystemPrompt` (agent, `settings_set` with `scope: "agent"`): the **Minimal system prompt** option above, per agent only, default off. - `ignoredAgentDefinitions` (project, read-only): the on-disk definition files you chose not to import; written by the import dialog. ## Agent tools (MCP) - `agents_list` / `agents_get`: the saved agents of a project, including whether a custom system prompt is set and its body. - `settings_list` / `settings_get` / `settings_set` with `scope: "agent"`: read or change one saved agent's options, `minimalSystemPrompt` included. - `agents_save`: create a new project agent or update one (role, provider, model, custom system prompt, skills, capabilities). ## Providers All providers, no difference: a built-in, expert, custom or community agent runs on whichever CLI you assign it (Claude Code, Codex, GitHub Copilot CLI, Antigravity, OpenCode, Aider, Grok Build, Mistral Vibe, Kimi Code, Amp, oh-my-pi, Freebuff, Devin, Cursor). The system prompt is never translated: the persona stays in its author's language. **Minimal system prompt** works on every provider; on Claude Code and oh-my-pi it is appended to the CLI's own system prompt instead of replacing it, so the CLI keeps its native instructions. ## Mobile Partly. The phone's **Add agent** sheet uses the same casting screen: search, **Help me choose an agent**, the stage with **Change role or look**, the **Provider** / **Model** / **Reasoning** cards and **Advanced options** (**Who gets this agent**, capabilities including **Minimal system prompt**, system prompt); workspace, skills, connections and CLI options stay on desktop because they point at files of the computer. The full catalog offers the same tiers (Core Team, Specialists, Experts · The Agency, Community) with search, categories and install, the same **(Tech)** qualifier on the first three and the same **Tech & Pro** / **Lifestyle** grouping of categories; creating or publishing an agent is desktop only ("Create your own agents on desktop"). ## Limits - Custom agents per account: 3 on Free, 10 on Plus, unlimited on Pro. - Publishing requires a public pseudonym and passes moderation; approved agents stay in the catalogue even if the creator deletes their account (credited "Community"). - Likes: one per user per agent, never on your own. Unique installs exclude the creator. Creator badges: bronze at 10 unique installs, silver at 50, gold at 250. The first agent to reach 25 unique installs grants its creator the Plus plan. - Name, description and vibe are translated from an English canonical version; the creator sees their original text. ## Common questions - **Can I build my own coding agent?** Yes, with its own name, prompt, category and avatar, stored at account level and usable in every project. - **Do I get credit for publishing?** Yes: your pseudonym on the card, install and like counters, creator badges, a top-creators leaderboard and a Plus reward at 25 unique installs. - **I already wrote sub-agents for my CLI, do I redo them?** No. AgentsRoom detects them at project and user scope and offers to import them. - **My agent forgot its persona after a context compaction, or only followed part of it.** Fixed on 2026-09-19. Before, the agent was only told to read its role file, and Claude Code in its bypass-permissions mode read it through a shell command that silently returns a short preview of a long file; what it had read then vanished with the first compaction. The persona is now placed in the system prompt when it fits, and the file instructions ask for the CLI's file-reading tool and a re-read after each compaction. Restart the agent to get the new prompt. - **I named my agents after my tasks and they all renamed themselves on the first turn.** Fixed on 2026-09-29: a name typed in the **Name** field at creation now wins over the title the agent gives its conversation. Agents created before the fix keep their old behaviour until you rename them by hand. - **My agent is not about code, which category do I pick?** The **Lifestyle** family: Sport & Health, Learning or Lifestyle. Added on 2026-09-29, because a coach or a tutor used to be filed under Engineering or Other. - **My agent follows AgentsRoom's brief more than my CLAUDE.md, can I turn the brief off?** Yes, per agent: **Minimal system prompt** in **Advanced options**. The tab title and notifications keep working; the agent no longer knows how to use the AgentsRoom tools unless you ask it explicitly. Not available on team steps, which need their full brief. - **Why is my published agent back "In review"?** You edited it; every edit to a published agent is re-moderated. Counters and likes are kept. ## Related - [Agent Templates](https://agentsroom.dev/docs/agent-templates.md): reusable full configurations (provider, model, skills) for your agents. - [Agent Suggestions](https://agentsroom.dev/docs/agent-suggestions.md): the advisor that picks among these tiers from a task description. - [Agent Morphing](https://agentsroom.dev/docs/agent-morphing.md): switch a live agent into any of these roles. - [Team Chat](https://agentsroom.dev/docs/team-chat.md): the chat used to share agents with teammates. - [Skills Library](https://agentsroom.dev/docs/skills-library.md): shared skills, the other marketplace. - [Leaderboard](https://agentsroom.dev/docs/community-leaderboard.md): the **Top creators** button of the Community section and the Agents board it opens.