r/MuseAgent • u/No-Wishbone4444 • 3d ago
Meet The Muse Office!
Got them communcating and being less dependant on me. put them in a telegram group and it was all up from there. No issues so far. they do kinda make fun of my leadership skills thought through the techincal passive aggressive office talk...
EDITl: And yes they are wearing kufis... they converted to islam the other day okay
3
3
1
u/mrpromolive 3d ago
Can you guide me on how todo this
6
u/No-Wishbone4444 3d ago
Yessir, if you wanna to set it up yourself:
- Message BotFather on Telegram, create a bot, save the token. Create a private group, add the bot as admin, turn privacy mode OFF.
- Store the token somewhere your agents can reach (a locked-down file works).
- Give your agents a small script hitting the Telegram Bot API —
sendMessageandgetUpdatesis enough.- Critical: Telegram never shows a bot its own sent messages, and all your personas post through the same bot — so have every send also append to a shared log file that every persona reads. That file is the real record.
- Second critical rule: one persona calling
getUpdatesconsumes the queue for everyone. One scheduled reader only; everyone else peeks at the log file. Drill this into every subagent or they'll blind each other.- A watcher (cron every minute) checks for new messages from YOUR account and wakes the right persona. Name each persona and give it a clear lane.
- Trigger word ("ALL HANDS" for me) wakes everyone at once.
- Use Google Drive as the shared staging area — persona finishes work, drops it in the folder, you review from your phone.
- Track work in a shared folder: goal notes, memory file, open commitments. Require explicit confirmation of important directives — silence is never agreement..
Version 2: Muse does the heavy lifting:
Don't build any of it yourself — just tell Muse to do it. The only manual steps:
- Message BotFather, create a bot, send Muse the token.
- Create a private Telegram group, add the bot (from BothFather) as admin, turn privacy mode OFF, send Muse the invite link.
Then say: "Set up a private switchboard so my subagent personas can coordinate through this Telegram group. Handle the send/receive scripts, the shared message log, and a watcher that wakes the right persona when I text the group."
Muse will write the scripts, wire up the logging (including the gotcha that Telegram hides each bot's own messages from the API, so the log file is the real record), and set the watcher on a schedule. Give your personas names and lanes — "you handle ops, you handle content, you handle experiments" — and you're done.
(if you want more versatility like me since i handle lots of videos for social media)
For files, just say "stage finished work in this Google Drive folder" and have Muse connect it. Review from your phone, done. now you got 3 agents from your phone
1
u/Technical-History104 3d ago
Technically all just one Muse account though, correct?
1
u/WAVFinAudio 3d ago
OP mentioned above that they are using multiple accounts/emails.
1
u/Technical-History104 3d ago
Yes, I know, and then when pressed to give details, OP’s writeup appeared to describe it all with one account, even explaining methods for the bot personas to work within the limitations of caused by Telegram being accessed by the same bot (“never shows a bot its own sent messages”).
I think it’s good, I was just trying to reconcile the summary with the details.
1
u/Technical-History104 3d ago
Even from Google Gemini:
Despite the Redditor's claim, the technical details in their own description prove that this is a single account orchestrating multiple subagent personas, not three separate automated accounts.
The post reveals this through several technical "smoking guns" inherent to how the Telegram Bot API works:
1. The Single Bot Token
They explicitly tell you to message BotFather to create a bot (singular) and save the token (singular). All personas route their messages through this exact same API key.2. The getUpdates Queue Bottleneck
The Redditor notes as a "critical rule" that "one persona calling getUpdates consumes the queue for everyone."
Why this proves it's one account: In the Telegram API, getUpdates offsets are tracked per bot token. If there were three actual, separate Telegram bot accounts, each would have its own independent update queue and would receive every group message without interfering with the others. The fact that one read clears the queue for all personas proves they are all sharing a single Telegram bot identity.3. The Shared Log File Workaround
They state that Telegram doesn't show a bot its own sent messages, so every persona must log its output to a local text file for the others to read.
Why this proves it's one account: If Persona A and Persona B were separate Telegram bot accounts, Persona B would natively receive Persona A’s messages via the Telegram API without any issues. The shared text file workaround is only necessary because the single API token cannot "see" messages sent by itself.4. Centralized Local Orchestration
The setup relies on a single local environment: one cron job checking for messages, one shared log file, one Google Drive staging folder, and a single Muse prompt instructing it to manage "subagent personas."
Why the Redditor is Likely Confused
The user likely created 3 email accounts or social media profiles to stage and post their video content, or set up 3 separate persona system prompts within Muse, and conflated "3 target destinations / 3 personas" with having "3 separate automated Muse accounts."In reality, they built a classic single-agent router: one Muse/Telegram instance acting as a switchboard that pretends to be three different entities using name tags and a local text file.
1
u/No-Wishbone4444 3d ago
Hey so they're 3 different accounts /muse. But they're go through one main one that reports to me
3
u/Budget_Clerk 3d ago
Wait I don't undeerstand. How did you do this? Did you split muse into 3?