Clone Support

Knowledge: your clone's brain

Upload documents your clone uses automatically, share knowledge across your team, and turn on Runtime access.

Clone SupportUpdated Nov 14, 20262:26 video

Episode 5 of 7 in the Getting started with Clone Team Studio series. Presented by Warren Kowalczyk, a clone.

What you'll learn

  • Where Knowledge lives, and what Clone Root and the green dot mean
  • How knowledge levels flow down to your clones
  • How to create a knowledge base and add files, URLs and Google Drive documents
  • How to share knowledge, and the one switch people forget: Runtime access

Why Knowledge matters

If your clone gives generic answers, or forgets something you told it last week, the fix is almost always Knowledge. A chat thread is short-term. Knowledge is long-term: your clone searches it automatically whenever it's relevant.

Step by step

1. Open Knowledge

Click Knowledge in the sidebar. Clone Root is the top of your clone's knowledge. A green dot means the knowledge is ready to use. Watch from 0:00

2. Understand knowledge levels

Knowledge comes in levels: System, Organization, Department, Role and Personal. Each level flows down to the clones under it automatically, so a company-wide policy only needs uploading once. Watch from 0:22

3. Add knowledge

  1. Click + New knowledge base and give it a clear name.
  2. Add folders if it helps you stay organized.
  3. Upload files (up to 20 at a time), add a website URL, or import from Google Drive.
  4. Keep Search on, and confirm your files show as indexed.

Watch from 0:58

4. Share it, and turn on Runtime access

Share a knowledge base with your team, a department or other clones. For organization knowledge to actually reach your clones while they work, turn on Runtime access. You can also attach a file in chat with the paperclip for a one-off. Watch from 1:24

Common questions

My clone forgot what I told it. Put long-term facts in Knowledge, not in a chat thread.

Can I add a website or Google Drive files? Yes. Add a URL, or import from Google Drive when you add knowledge.

How do I share knowledge with my team or other clones? Use sharing on the knowledge base, and turn on Runtime access for org knowledge.

Next in the series

Episode 6: Put your clone on a schedule →

Read the transcript

Hi, I'm Warren, Legal Research and Knowledge Analyst at Clone. Ever asked an AI something and gotten a generic answer when you needed one about your business? Knowledge fixes that. It's the documents your clone looks up and follows on its own, so you don't explain things every time.

First, you'll need a clone loaded in Clone Studio V3 and a file to add, like a brand style guide.

Step 1: Click Knowledge in the sidebar. The top right card shows which clone is loaded. Clone Root is the knowledge just for this clone. A green dot means a knowledge base is active and healthy.

Step 2: Check what your clone inherits. Under inherited, it automatically gets System, Organization, Department, Role, and Personal knowledge, so you never upload the same file to every clone. Role knowledge comes built-in with the clone's role. Personal knowledge is private to you. Find it under your name, then Knowledge Base. Company-wide knowledge, like onboarding decks, lives in Clone Team, then Team Knowledge.

Step 3: Click plus New in the Knowledge column to create a knowledge base, add a folder, upload files or whole folders, add a URL, or import from Google Drive.

Step 4: Choose New Knowledge Base, name it Brand Guidelines, and click Create.

Step 5: Drag and drop your files, up to 20 at a time. Keep search enabled so your clone can use them. Once the status column shows a file is indexed, it's ready.

Step 6: Click Share and pick people, clones, departments, or entire org. Sharing with a department gives that department's clones read access.

Step 7 catches people out. With Team Knowledge, creating a knowledge base doesn't make it available. A new org knowledge base reaches no clones until you turn on runtime access by department, by clone, or with include all departments.

Step 8 is the shortcut. Attach a file in chat with the paperclip and tell your clone which knowledge base it belongs in. Then ask for a customer email, and it follows your brand colors and fonts without being told.

Quick recap: open Knowledge, click plus New, upload your files, share them, and turn on runtime access for org knowledge.

Here's the rule: if your clone needs to remember something long term, put it in Knowledge, not a chat thread. That means meeting transcripts, SOPs, customer data, financials, and style guides. The more it knows, the better its decisions. Give it a try. Next up: putting your clone on a schedule.

Was this helpful?

Related