Feature: monthly schedules and concurrent sessions while tasks run

[paulkuo123]

Before filing

• I searched existing issues and this isn't a duplicate

Area

Chat UI (src/)

Problem

OpenMausBot currently supports one-time and repeating schedules on selected weekdays, but it does not support calendar-month schedules. This makes it difficult to automate work that should run once per month, such as a monthly report, billing review, inventory check, or planning reminder.

There is also a usability limitation in the chat UI: while a bot task is running, the New session button is disabled. This prevents the user from starting a separate conversation/session to handle another task, forcing them to wait for the current task to finish or interrupt it.

A daily or weekly approximation is not equivalent to a calendar-month recurrence, and disabling new sessions during long-running work prevents useful parallel workflows. I searched the existing issues and did not find requests covering these two capabilities together.

Proposal

Please consider adding both of these capabilities to Tasks & routines / Chat UI:

1. Monthly schedules

• Add a Monthly schedule option.
• Choose a day of the month (1–31) and a local time.
• Use the paired computer's local timezone, like the existing schedules.
• Define deterministic behavior when a month does not contain the selected day (for example, run on the last day of that month, or make the policy explicit in the UI).
• Keep the existing once/daily behavior unchanged.

2. Concurrent sessions while a task is running

• Keep New session available while another task is running.
• Allow a new session to start and process an unrelated task without waiting for the current task to finish.
• Keep each session's transcript, task state, approvals, tool activity, and output isolated so events cannot cross over between sessions.
• If a particular bot or resource cannot safely run two turns at once, queue the second task with a clear queued status rather than disabling session creation; tasks assigned to other available bots should be able to run concurrently.
• Cancelling or failing one task must not cancel or corrupt another session's task.

Please update the relevant schedule/session types and API, desktop UI, calendar/session views, compatibility clients where needed, and automated tests.

Alternatives considered

• Recreating a one-time routine every month.
• Approximating a month with a daily or weekly schedule.
• Waiting for a running task to finish before opening another session.
• Using an external cron job, webhook, or separate app, which is less integrated with OpenMausBot.

For concurrency, a safe first version could allow unlimited new sessions but serialize work per bot/resource where necessary, with explicit queued/running indicators.