Muse Task HubUnofficial guide

Work · Community report

Rebuild side-chat bots from a Notion export

After moving a bot setup into Notion, one X user says Muse's main chat read it and recreated all their side-chat bots, personas and routines included. Chat transcripts were left out of the export. This page gives a prompt and checks for rebuilding side-chat bots without losing instructions along the way.

What you can get

What it is

Side chats recreated from a Notion description

A set of recreated side-chat bots plus a persona-and-routine checklist you have compared line by line with the Notion export. It is not a full copy of past chat history.

It came back right when

  • Every bot in the Notion export appears as its own side chat
  • Each side chat's persona and instructions match its Notion entry
  • Routines run at the times and for the targets you confirmed

The checks are editorial, not from the source.

Illustration — suggested task flow, not an execution result
  1. Prepare

    A Notion page or export describing each bot's persona, instructions and routines

  2. Ask and review

    Make sure the Notion export holds, for each bot, its name, persona, instructions and routines in plain text; the post's export left out full chat transcripts, so treat old history as gone.

  3. Check the result

    Every bot in the Notion export appears as its own side chat

The source case

@kylegibson2 reports having another assistant send everything it held to Notion, except a full transcript of each bot chat. By their account, they then had Muse's main chat look at that Notion material and replicate it, and it made all the bots as side chats with their personas and routines. The post names no bots, says nothing about how many there were, and shows neither the Notion pages nor the result, so how closely the rebuilt bots matched the originals rests on the author's word. Past conversation history was left out by the author's own description.

A public report by someone outside this library. Not independently reproduced here.

From the source

Source excerpt

I had grok bot send everything (except a 100% transcript of each bot chat) it has to Notion. Then I had Muse main chat look at Notion and replicate all of it. It made all the bots (side chats) with their personas and routines.

@kylegibson2 · Read it at the source · checked

Quoted from the original posts. Not written by this guide, and not a result produced here.

Suggested prompt

Bring A Notion page or export describing each bot's persona, instructions and routines, A list of which bots you actually want rebuilt, Your approval for any routine that sends, posts or contacts someone. Source community report, checked 2026-11-07.

Written by this guide as a starting point, not quoted from the source. Your edits stay in this browser.

What you need

You supply

  • A Notion page or export describing each bot's persona, instructions and routines
  • A list of which bots you actually want rebuilt
  • Your approval for any routine that sends, posts or contacts someone

How to try it

Editorial, not from the source

  1. Make sure the Notion export holds, for each bot, its name, persona, instructions and routines in plain text; the post's export left out full chat transcripts, so treat old history as gone.
  2. Ask Muse's main chat to read the export and return a table of every bot it found, before it creates anything.
  3. Fix anything in the table that is wrong or missing in Notion first, so the source and the rebuild stay in step.
  4. Approve the rebuild and have it create the side chats one at a time, showing the persona and routine text it used for each.
  5. Compare each side chat with its Notion entry, and send each one a short test message to see whether the tone and instructions came through.
  6. Switch on routines that message or post anything only after you have checked their timing and target.

What the post describes

@kylegibson2 describes a two-stage move, posted as a reply in a thread. Another assistant wrote what it held to Notion, minus a full transcript of each bot chat, and then Muse's main chat was pointed at Notion and asked to replicate it. The result they report is short: "It made all the bots (side chats) with their personas and routines."

The post gives no bot names, count, prompt or screenshots, so the method here is editorial, built around the two things the author did report: the Notion page as the go-between and the main chat as the place where the side chats were created.

Shaping the Notion export

A rebuild can only be as good as what the export says. As a general practice, give each bot its own Notion heading or page with the same fields in the same order: name, persona, tone, standing instructions, and routines written as what happens, when and how often. Short labeled fields are easier to check against the rebuilt side chat than a long free-form summary.

Leave transcripts out unless you really need them. The author's export skipped them, and rebuilding from a persona description is a different job from carrying past conversations over.

Checking each rebuilt side chat

Ask for the setup text of each side chat after it is created and read it next to its Notion entry. Wording drift shows up most in tone and in conditions such as "only on weekdays" or "ask before posting". A one-line test message per bot shows quickly whether the persona came through.

Routines deserve their own pass. Check the timing and the target of anything that runs on its own before you rely on it, since the post does not say how the rebuilt routines behaved.

Limits and confirmation points

Limits to confirm

  • The post does not name the bots, give a count or show the Notion pages, the prompts or the rebuilt side chats.
  • Full chat transcripts were not exported, according to the author, so earlier conversation history did not carry over.
  • No detail is given on how the routines run or whether any of them worked after the rebuild.
  • This is an attributed community report, not reproduced by this guide. The suggested workflow and checks are editorial guidance, not a recovered conversation or guaranteed product capability.

If it goes wrong

Editorial, not from the source

A rebuilt side chat sounds different from the original bot
Compare its setup text with the Notion persona, put any missing tone or rule into the Notion entry, and ask for that one side chat to be updated from it.
Some bots from the export are missing
Ask the main chat to list every bot it found in Notion and check that against your own list; split a long page into one section per bot if entries are being merged.
A routine runs at the wrong time or not at all
Pause it, restate the schedule and target in plain words, and confirm it again before letting it run unattended.

Common questions

Can Muse rebuild side-chat bots from Notion?

One user reports that Muse's main chat looked at their Notion material and made all the bots as side chats with their personas and routines. The post shows no screenshots or details, and this guide has not reproduced it.

Does chat history carry over?

Not in the reported case. The author says the export covered everything except a full transcript of each bot chat, so earlier conversations were not part of the rebuild.

Should I rebuild all the bots at once?

The author reports all of them being made from one request. As an editorial suggestion, approving a list first and creating them one at a time makes it easier to spot a persona or routine that came out wrong.

What should the Notion page contain?

At minimum each bot's name, persona, instructions and routines. The post does not show the author's page layout; consistent labeled fields per bot are a general practice that makes comparison easier.

Next

Related to this task

  • Plan a cross-tool chat handoff A limited cross-tool handoff plan and a tested non-sensitive example with explicit access and retention boundaries.
  • Save daily industry research to Notion A Notion database of daily industry research picks, each with a source link, summary and content idea for you to check; not verified reporting or publish-ready content.

More in Work

  • Write a professional summary of your work history A draft professional summary and a list of claims to verify; not a finished resume, and not a guarantee that any employer will read it the way you intend.
  • Build a workflow dashboard in a Space A workflow dashboard spec and a checked first version that shows your calendar, mail and portfolio summaries. It is not a replacement for those apps and has no permission to send, trade or run commands on your computer.
  • Build an animated usage tracker space A personal usage tracker space with a progress visual and an animated character; a fun display of your own usage, not an official billing or quota record.

Every work task

Get recurring task recommendations — ask your own agent to check for relevant updates.