Experts: make your first assistant
An expert is who you talk to in Octop. Give each expert one fairly steady job: weekly reports, research, or code review. Each expert keeps its own files, model, and chat history, so switching experts does not mix those threads.
The setup wizard already created a default expert named main. Try one sentence with it, then follow the steps below to add a specialist.

Create a specialist
Open Experts
In the sidebar, open Experts. The tabs are My Experts, My Teams, and Discover Experts.
Start from a template
Open Discover Experts. The page opens on Featured, which lists the templates that ship with Octop. Pick one and click Create. Click New expert on My Experts when you want to write the instructions yourself.
Choose a model and a default mode
Pick the model this expert uses. Under Default Conversation Mode, choose Ask mode (read-only: read files and search the web), Plan mode (write a plan into the workspace), or Craft mode (tools, skills, and connectors). New chats use that default. Chats you already opened keep the mode you last used.
Send a real task
Open Conversation, select the new expert under Experts, and state the job. For example: “Using this week’s meeting notes, draft the Friday status report and start with an outline.”

The Conversation sidebar splits into Experts, Teams, and Cloud. Cloud appears after you add a cloud collaboration link. The sidebar and the @ picker list running experts only.
To create, list, start, and stop experts from the terminal, see Agent commands.
What you can do in chat
- Type
@in the composer to mention another running expert, or a file in the workspace. - Click a skill in chat to insert
/sluginto the composer. - While a reply is still generating, send another message to steer that turn.
- To keep your name, preferences, or hard rules, open Personalization → Memory and edit User profile and Strong memory. When a new memory conflicts with an existing one, Octop asks you to confirm first.


While Octop compacts memory, chat shows a progress banner and pauses send. You can also back up and restore memory storage.
One expert, one job
One account can run as many experts as you need. A practical split:
- Keep a writing expert and a coding expert apart, so the two instruction sets stay separate.
- Keep a Feishu support expert apart from the research expert you use in private chat.
- Run one expert on a cloud model and another on local Ollama.
Select the expert at the top of the page, then configure it under Personalization. An administrator can grant these areas separately under Management → Users, so skills, memory, and channels can be opened one at a time.
The Skill market, Plugin market, and Expert market can run on your own network. Octop calls a small HTTP catalog instead of the public sites. See Skill market and Plugin and expert market.
When you create or edit an expert, you can also attach default knowledge bases and connector instances. New chats for that expert start with them selected. You can still change the selection on a given turn.
Let a teammate open the same expert
Turn on Share with other users when you edit the expert. Other people on this instance can chat with that running expert, and its skills are available in chat. Only the owner can change settings or files. On a shared expert, Share conversation lets other users open that thread. The menu shows Shared while it is on. Hide expert removes an expert from your chat list without deleting it.
To hand someone their own copy of the setup, publish it to the expert market. The original expert keeps running. See Experts and personas.
Start, stop, and delete
Each expert card can start, stop, and reload. A Running expert accepts messages. A Stopped expert does not reply. If startup fails, check the logs.
Stopping an expert ends its active sessions on every connected channel. An in-progress message will not receive a reply. Start it again to continue.
Deleting an expert removes the workspace under ~/.octop/agents/<id>/. The web UI and the CLI both ask you to confirm. This cannot be undone.
When you need an isolated workspace
After an administrator adds a Docker Sandbox or OpenSandbox under Management → Storage, you can pick that backend when you create an expert. The expert runs in the sandbox, and its files stay off the host disk. OpenSandbox creates a remote sandbox when the expert starts and destroys it on stop. Enabling that backend installs the official SDK.
- Sandbox scope chooses how containers are shared: one per expert, one per user, or a fixed sandbox.
- Deleting the expert does not delete the container.
- With a Fixed scope, you can browse container files in the workspace viewer.
In the workspace viewer you can open a Word (.docx) file as Markdown and save it back. Headings, bold, italic, lists, and tables stay. Complex formatting is simplified.
Next steps
Use the library and MBTI to set how an expert thinks and speaks
Upload files so replies cite them
Authorize docs, meetings, or mail, then ask in plain language
A host assigns work and members reply in the same room

