> For AI agents: the complete documentation index is available at /en/llms.txt, the full documentation bundle is available at /en/llms-full.txt.

# First time with Octop: how the pieces fit

You can start without learning how the process is built. Five pieces are enough: an expert answers, a model does the thinking, a knowledge base is the files it can look up, a connector is an app it can operate, and a channel is how you reach it from WeChat or Feishu.


![Octop web UI](/images/en/ui-chat.png "Web UI")

## What each piece is for


[**Experts**](/en/guide/concepts/agents.md)

Your digital coworkers. Use one for weekly reports, one for research, and one for code. Their memory and files stay separate

[**Models**](/en/guide/guides/llm-providers.md)

The service an expert thinks with. Add an API key once for DeepSeek, OpenAI, Claude, or a local Ollama model

[**Knowledge bases**](/en/guide/concepts/knowledge.md)

Drop in PDFs, Word files, and spreadsheets. Replies list the passages they used

[**Connectors**](/en/guide/concepts/connectors.md)

Authorize Tencent Docs, meetings, mail, or Notion once. Then ask in plain language

[**Channels**](/en/guide/concepts/channels.md)

Reach an expert from Feishu, WeCom, DingTalk, QQ, WeChat, Telegram, or Discord

[**Personas and templates**](/en/guide/concepts/experts-personas.md)

A template sets the job. An MBTI persona sets the voice

## Where one question goes

Suppose you have already authorized Tencent Meeting and uploaded a project proposal to a knowledge base. In Feishu you tell the linked expert: “Check my meetings tomorrow and turn the proposal into a 300-word summary.”

1. **Feishu hands the sentence to that expert.** The channel only carries the message in and the reply out.
2. **The expert looks up tomorrow’s meetings.** It calls the Tencent Meeting connector you authorized.
3. **The expert finds the relevant passages in the knowledge base.** You leave the full document out of the composer.
4. **The model writes the summary from the schedule and those passages.** The tone follows the persona you chose.
5. **The summary returns to Feishu.** You can open the cited document under the reply.

**Conversation** in the web UI and scheduled tasks follow the same path: the message reaches the expert, and the expert uses a knowledge base or connector when the request needs it.

## A practical order


### Send a first message

Install with the [quick start](/en/guide/quickstart.md), then say something to the default expert `main` in **Conversation**.

### Switch to a specialist

Open **Experts → Discover Experts**. **Featured** lists the templates that ship with Octop. Click **Create**. See [Agents](/en/guide/concepts/agents.md).

### Give it files and apps

Upload a [knowledge base](/en/guide/concepts/knowledge.md), or connect one app you already use under [Connectors](/en/guide/concepts/connectors.md).

### Reach it from your phone

Scan a QR code to link [Feishu, DingTalk, WeCom, or QQ](/en/guide/guides/im-channels.md). Add a [scheduled task](/en/guide/guides/cron-jobs.md) when you want a daily push.

## One person or several

One Octop can have multiple sign-in accounts. Experts, chats, and workspaces you create stay visible to you. An administrator manages users and instance settings. Turn on **Share with other users** on an expert so other people on this instance can open that running expert. Turn on **Shared** on a knowledge base so they can read it.

Experts on another Octop appear under **Conversation → Cloud** after you add a [cloud collaboration](/en/guide/guides/cloud-bridge.md) link. When several experts should split one job in a single room, use an [expert team](/en/guide/concepts/expert-teams.md).

## Where your data lives

Chats, secrets, and workspaces stay on this machine under `~/.octop/`. One `octop run` starts the web UI, messaging channels, and schedules together. See [Data directory](/en/guide/configuration/data-directory.md) for each folder. Export with `octop backup` before you move machines.
