Meta Muse Connectors & Tasks: writing clean approval rules in Soul.md.
By Bernard Huang · Updated
Once Muse has access to mail, calendar, or scheduled recurring Tasks, your Soul.md needs explicit read-vs-write confirmation gates.
On this page
Which file governs Connectors, Tasks, and persona?
| Muse surface / file | What belongs here | What happens when misplaced |
|---|---|---|
Soul.md (Personality & Behavior) | Voice rules, truthfulness gates, tool confirmation boundaries, draft-before-send defaults | Putting schedule facts here causes drift; omitting approval rules leaves side effects vague (Soul.md templates →) |
Identity.md (Avatar & Card) | Name, avatar vibe, one-line role description, surface greeting (setup guide →) | Stuffing procedural approval matrices here crowds identity card limits |
Memory.md (Facts & Context) | Working hours, preferred recipients, formatting constants, standing context (privacy guide →) | Storing behavioral prohibitions as memories makes them fragile when you prune memory entries |
| Scheduled Tasks / Connectors | Recurrence timing, permitted external integrations, per-task prompt scope | Asking a Task to “handle my inbox” without dry-run limits leads to premature sends |
Copy-paste Soul.md autonomy & Connector approval block.
Merge this block into your existing Soul.md using the Muse Soul.md Editor (it wraps your rules in reversible markers and lets you download a backup first):
Practical read / draft / execute boundaries for everyday workflows.
| Workflow | Safe automatic step | Require confirmation gate |
|---|---|---|
| Morning brief (Scheduled Task) | Aggregate upcoming events, deadlines, and unread highlights with exact timestamps | Declining invitations, rescheduling meetings, or messaging attendees |
| Email / message triage | Cluster threads by urgency and write editable reply drafts | Hitting send on any external thread or forwarding sensitive attachments |
| Research & side chats | Fork long tangents into Muse Side Chats while keeping the main log clean (troubleshooting guide →) | Overwriting permanent workspace docs or appending unverified claims to shared notes |
Want to compare Muse’s file setup with ChatGPT and Claude? Read Muse vs ChatGPT vs Claude.
Questions people ask.
Should Connector approval rules go in Soul.md or Memory.md?
Put durable confirmation gates and draft-first defaults in Soul.md because Soul.md governs behavior across conversations and Tasks. Keep mutable context (like your work hours or VIP contacts) in Memory.md.
Can Soul.md overwrite existing customizations if I paste an approval block directly?
Replacing all of Soul.md manually will erase existing persona traits unless you merge carefully. Use our Muse Soul.md Editor to preview the merge inside labeled markers and save an original backup first.
How should a Meta Muse scheduled Task report failed lookups?
Add an explicit rule telling Muse to quote tool failures verbatim and leave missing slots blank instead of inferring or smoothing over skipped Connector reads.
Where do I inspect or pause saved facts Muse learned from Connectors?
Inspect and trim Memory.md regularly under Assistant Identity / Memory settings, or audit an export locally with the AgentTune AI Memory Export Reviewer.
What changed.
- First published covering Soul.md vs Identity.md vs Memory.md separation and Connector/Task confirmation gates.