Assistant specialists

  • Desktop, mobile and web
  • All plans
View as Markdown

What it does

The personal assistant can have specialists: a running coach, a wealth advisor, a home manager. Each specialist is an assistant of its own that you talk to directly, with its own name, its own standing instructions (the equivalent of a CLAUDE.md), its own conversation and its own dossier in the assistant's private memory. They replace the "git repository with a CLAUDE.md that commits after every change" that some users set up by hand to keep a coach's memory.

Video (1 min 18 s): Assistant specialists, shown in the real app. A "Running coach" is created from the assistant panel with its standing instructions, gets its own tab next to the assistant, answers a run report in the short style it was asked for, and its rules, journal and week plan show up in its own dossier of the assistant memory.

Where to find it

  • Desktop: the assistant panel (title bar button "Assistant") always shows a tab strip: the assistant first, then one tab per specialist with its face, a search field from two specialists on. "+" (or "New specialist" when there is none, at the right end of the tab strip) opens the "Specialists" window in the middle of the screen with the "New specialist" form; the pencil of the open tab edits it. Settings > Assistant > Specialists offers the same. Each tab's face carries a status badge, the same as a project agent's: grey until its console was ever opened, green at rest, orange while it works, red when it waits for your answer, and a pill with a number when it finished while you were looking elsewhere ("Finished, not read yet"; it clears once you open its tab). Hovering a tab says its state in words. The title bar "Assistant" button's badge sums up the whole team, open tab or not: red if any of them waits for you, else orange if any works, else the unread pill if any finished, else green. Hovering that button (panel closed) lists the assistant and every specialist with its state in words ("Working", "Finished, not read yet", "Waiting for your answer"); clicking a row opens that conversation.
  • Phone: tapping the Assistant tab asks "Who do you want to talk to?" as soon as one specialist exists; "New specialist", under the list, opens the create form and then the new specialist's conversation. The conversation screen's tab strip has the same "+", and Settings > Specialists lists, creates and edits them.
  • Memory browser: the specialists are notes of the "Specialists" section (folder assistants/).
  • Video tutorial: a small play icon at the right end of the assistant's tab strip, after "+" (tooltip "Watch the video tutorial on YouTube"), opens the video on YouTube in your browser.

How to use it

  1. In the assistant panel, click "New specialist" at the right end of the tab strip (or Settings > Assistant > Specialists > New specialist).
  2. Give it a name ("Running coach"), what it is for, a memory dossier (defaults to the name) and its standing instructions.
  3. Optional: "Agent it speaks as" gives the specialist the know-how and the face of a catalog expert (Agency or community). When you create one, AgentsRoom suggests matching agents on its own from the name and purpose (for example the Running Coach for a running coach), then on "Suggest an agent"; "Browse the catalog" picks any. Without one, the specialist looks and talks like the assistant. Suggestions count against the monthly suggestion allowance.
  4. Optional, desktop only: "Import a folder" picks a folder of notes (for example a git repository used as a memory). Its Markdown and text files go into the dossier, mirroring the folder tree; its root CLAUDE.md, AGENTS.md or GEMINI.md fills the instructions when they are empty; its .claude folder (sub-agents, skills) is imported as claude/. Nothing is written before Save. Importing the same folder again updates the notes instead of duplicating them.
  5. "Save" (bottom right of the form, next to "Cancel"; scroll down past the instructions). Created from the panel, the specialist's tab appears right away next to "Personal assistant", selected, and its own conversation starts after a few seconds. From Settings, "Talk to it" (or pick its tab in the assistant panel).

The instructions apply from the first message of every conversation. When you give the specialist a new standing rule ("from now on..."), it updates its own instructions note (same consent rule as any memory save) and the change applies from its next conversation. Like the assistant, a specialist starts a fresh conversation each day and offers yesterday's.

Triggers: in a trigger's editor, the executor "Assistant" hands the prompt to the assistant or to one specialist instead of starting a new agent. Nothing is spawned, the prompt lands in that conversation like a message from the phone, and the run row opens it in the assistant panel.

One team: hand-overs and shared memory

The assistant and its specialists work as one team serving the same goals:

  • Hand-over: ask the assistant something that is clearly a specialist's field and it offers, in one line, to pass it on ("That is your running coach's field: shall I pass it on?"). On your yes, the request lands in that specialist's tab (desktop and phone), introduced by "Task delegated by <assistant>", and the specialist sends its result back to the assistant. A specialist does the same toward the assistant or another specialist for a request outside its field.
  • Create by asking: the assistant can create a specialist for you ("Shall I create a Cooking specialist?"), only after your yes. It then shows as a new tab. It searches the whole agent catalog (built-in roles, The Agency, community agents and your own agents) to give the specialist an expert's know-how and face; when nothing fits it proposes to create a new agent in My agents, and submits it to the community only if you ask.
  • Shared memory: every assistant sees every dossier of the private memory and reads the others before advising, so advice stays consistent across subjects (a key running session on Thursday leads to a nudge to skip drinks and sleep early on Wednesday; a tight budget becomes one more reason). Each one writes only in its own dossier (plus the shared profile and contacts). Your overall goals belong in the profile folder: every assistant reads them as the common strategy.
  • Moderate messaging: reading the memory always comes first. Messages between assistants are short, never acknowledgements, and capped at 3 per hour to the same assistant and 8 per hour to the whole team.

Settings

  • Specialists themselves are not app settings: they are stored with the account, encrypted, in the assistant memory (folder assistants/, one note assistant-<slug> each), so every computer and the phone list the same ones. Up to 30 per account.
  • botSpecialistRefs (global, internal): which agent plays each specialist on this machine, { [specialistId]: { agentId, conversationStartedAt } }. Machine-local. Removing an entry makes the next use create a new agent.
  • botPanelSpecialistId (global): the tab open in the assistant panel, a specialist id or null for the assistant. Shared by the panel and its detached window.
  • Each specialist can pin its own provider (with its account), model and reasoning effort, plus advanced options (browser access, skills, connections, CLI options, environment variables, MCP servers), exactly like Add Agent. Connections (since 2026-10-09) pin the saved servers, databases and dev commands the specialist may use, like Connections on any agent. Nothing pinned = the assistant's settings (Settings > Assistant > Model). A change to these launch settings (from the pencil, or inherited from Settings > Assistant) restarts the specialist's running console after its current turn; a change of provider or account starts a fresh conversation. Its standing instructions are not a launch setting and apply from the next conversation. The account is a profile of the computer: on a machine where it does not exist, the assistant's default account is used.
  • Trigger field assistantTarget (MCP triggers_save): "main" for the assistant, a specialist id, or an empty string to go back to an agent.

Agent tools (MCP)

Specialists have the bot role: same tools as the assistant, including the private memory (memory_* with scope: "assistant") and assistant_journal. Their notes and journal lines go into their own dossier. triggers_save accepts assistantTarget.

Team tools, reserved to the assistant and its specialists (hidden from every other agent): assistants_list (the team: ids, fields, dossiers, "main" = the assistant), assistants_create (a new specialist, after the user's yes), assistants_delegate({ to, task }) (hand a request over: it lands in that assistant's conversation) and assistants_message({ to, message }) (a short message, rate limited). They need the desktop running. assistants_create accepts agentSource + agentSlug from agents_catalog_search (open to every agent, like agents_create_custom and agents_publish_custom).

Providers

Every provider with an MCP client: same path as the assistant. Providers without an MCP client run a specialist without memory, like the assistant.

Mobile

Talk to a specialist from the Assistant tab picker (each face carries the same status badge as on the desktop, unread pill included, and each row says its state in words on the right; opening a conversation marks it read on the desktop too), create one from that picker ("New specialist", under the list) or the tab strip's "+", create, edit and delete them in Settings. Its advanced options on the phone include browser access, Skills and Connections (since 2026-10-09); CLI options, environment variables and MCP servers stay on desktop. Folder import is desktop only (a phone has no repository to import). Triggers' "Assistant" executor is available in the mobile trigger editor.

Limits

  • Up to 30 specialists, instructions up to 60,000 characters.
  • Import: Markdown and text files only, up to 500 files, 200,000 characters per file; a file that contains a password, a token or a card number is left out and counted.
  • A restricted trigger (untrusted payload) cannot target the assistant: the run is refused, because the assistant holds the private memory.
  • Deleting a specialist removes its instructions and its agent; its dossier and journal stay in the memory.

Common questions

  • Can a specialist look like another agent? Yes: pick an "Agent it speaks as" from the catalog; its avatar and persona replace the assistant's.
  • How do I create a specialist? Open the assistant (title bar button "Assistant"), click "New specialist" at the right end of its tab strip, give it a name, what it is for and its standing instructions, then "Save": its tab appears next to the assistant. Video: https://youtu.be/GZwlRZTb7e8
  • Can I have several assistants? Yes: create specialists in Settings > Assistant > Specialists. Each one has its own tab, instructions and dossier.
  • Where do my CLAUDE.md rules go? Into the specialist's standing instructions. Paste them, or import the folder: the CLAUDE.md fills them automatically.
  • Can I move my running coach out of its git repository? Yes: create a specialist and "Import a folder" on the repository. Scripts and data files are not imported, only notes.
  • Can my assistant pass a request to the right specialist? Yes: it proposes it in one line when the request is clearly that specialist's field, and hands it over on your yes. The task appears in the specialist's tab.
  • Do the specialists know what the others know? Yes: they share the private memory and read each other's dossiers before advising, so the running coach's plan can shape the advice of another specialist. Each one only writes in its own dossier.
  • Will my assistants flood each other with messages? No: they read the shared memory first, and messages between them are capped (3 per hour to the same assistant, 8 per hour in total).
  • How do I know a specialist is working or waiting for me? By the badge on its tab's face: orange while it works, red when it waits for your answer. The title bar "Assistant" button turns orange or red too when any specialist does, even if its tab is not open.
  • How do I see which specialist is working or has finished? Hover the title bar "Assistant" button: a list shows the assistant and each specialist with its state in words ("Working", "Finished, not read yet", "Waiting for your answer"), and a click opens that conversation. A specialist that finished while you looked elsewhere shows a pill with a number on its tab, like a project agent; it clears when you open the tab. On the phone, the "Who do you want to talk to?" list shows the same states.
  • Can a webhook wake my coach? Yes: set the trigger's executor to "Assistant" and pick the specialist.
  • Is there a video that shows it? Yes, a running coach created and used in the real app (1 min 18 s): https://youtu.be/GZwlRZTb7e8

Related