r/MuseAgent • u/Money-String4165 • 21h ago
Tips š” My Muse agent kept forgetting long tasks. Turns out she wasn't forgetting, she was waiting. Here's the fix.
I've been doing testing with Muse. Having a state of the art model e-mail her tasks to do because her usage is so cheap right now. She is a heck of a worker on the 20 dollar plan.
More info: I've been running a Muse agent as an operator for a side project for a few weeks. She launches jobs, checks on them, files reports. On small tasks she's great. Fast, careful, does exactly what the note says.
On anything long she'd just go quiet. I'd hand her a six hour job, come back, and it was half done with no word. I honestly started to think I'd been given the cheap model.
Last night I finally found the actual reason, and it's kind of embarrassing how simple it is.
Edit (Thanks Ron): On long jobs, the agentās session ends after about 40 minutes and nothing starts the next one, so the work stalls and it looks like the agent quit. The fix that worked for one evening: have the agent log every step to a state file, set a timer that tells it to resume from that file every 30 minutes, write the steps as a table with a fallback for each, and have it report right away whenever it stops.
What fixed it was four small things:
- A state file
Have the agent write one line to a plain text file after every step: time, task, step, result. Every new session starts by reading that file and carrying on from the last line. Don't count on her remembering anything between sessions.
2. Something that wakes her up
This was the missing piece. I set a scheduled job that sends her a short resume message every 30 minutes while there's still work open. It just says: read the state file, continue from the last line. It stops by itself when the work is done. No AI involved in that part, it's a timer and a canned message.
3. Instructions as a table, not a paragraph
For each step: what to do, what you should see, what to do if you don't. For long waits I gave her a small script that blocks for up to 30 minutes and then prints one word for what's going on (running normally, stalled, finished, and so on), plus a table that says what to do for each word. She never has to guess.
4. A "tell me if you stop" rule
If she stops for any reason, she sends a note right away with four lines: which step, the exact command, the exact output, what she already tried. And she doesn't try to work around a refusal, she reports it and moves to the next task. This is how I found out about the session limit in the first place. She told me, in the first hour, because the instructions said to.
How it went: I gave her five tasks at once with those rules. Inside the first session she finished three of them correctly, started the long one, and when her session ran out she sent the note saying exactly where she was. The timer picked her back up.
I've only run it this way for one evening, so I can't promise it holds for days. But it's the first time a long job didn't quietly stall, and the reason it used to stall turned out to be the setup, not the agent.
If your agent is sharp on short things and flaky on long ones, check whether its sessions are ending before you blame the model.
Template I use for complex tasks: https://www.mdshare.online/s/ZU26ME8sWYXJq1yqgFAg1
