One ask, many Amos: parallel sessions
Your list is never one task. Amo now takes the whole thing at once, opening a separate working session for every job on it, and you can watch all of them move.
Look at what’s actually on your list this morning. The proposal that has to get drafted. The invoice that went out three weeks ago and needs chasing. Tomorrow’s call, unprepped. The DM backlog you keep meaning to clear. That’s four, and the honest count is closer to seven. An assistant that works through a list like that one item at a time is an assistant you’re still waiting on when the day ends.
So Amo, the AI assistant built into Amolfi, stopped taking them one at a time. Hand it the list and the work fans out: a session per task, each with its own Amo on the job, all of them running at once.
Seven jobs, seven Amos
Each one is a genuinely separate job, with its own context and its own task and its own Amo visibly doing it. They sit next to each other on one screen, so a single glance tells you which jobs are still running.
Interrupt any of them
Fanning out a list would be chaos if the sessions went dark until they finished. They don’t. Open any one mid-run and steer it. “Shorter.” “Use the other template.” “Skip that one.” The thread you asked from stays the conductor: Amo keeps track of its own sessions, checks where each has got to, and brings the results back into one place rather than leaving seven answers stranded across seven tabs.
Multiplying the work copies the rules along with it. Every session runs under the same limits a single one does, and whatever comes back arrives as work waiting on your sign-off. You can have seven Amos going at once and every decision still routes through one person.
The difference shows up at the end of the day. The list you handed over in a sentence is sitting in one place, with your name on the next move.