Schedules

What happens at the time. harnsy creates an item for the role (asked by the team’s lead) and sends the holder who is online one line with the link. If nobody is online, harnsy wakes the holder: it reopens the session, or starts a new one. It needs a terminal driver for that; without one the run is marked no_terminal. At most 2 such wake-ups run at once on a node. When the item is handed in, or the time limit passes, the agent goes back to sleep unless it has other open items. The instruction is kept in versions.

Make one. Open the project, go to the “Schedules” tab and press “+ New”. The steps are Team, Role, When, Instruction, Terms and Review. “Check it. Saving turns it on at once.” A schedule stays with its role; to move it, make a new one. Editing applies from the next run.

When. Every day; weekdays; chosen days of the week; every N hours; or once at a date and time. Times follow the node’s time zone, across clock changes too.

Terms.

• Time limit: “no longer than N min” (1 to 1440, 30 by default).
• Session: a new one each time (default), or the same, which remembers yesterday and costs more tokens per run.
• Late start: run once if late by up to 3 hours (default; 0 means only on time, up to 24 hours). If the node was off, one run happens when it is within that window; otherwise one “missed” run, never several in a row.

Skipped runs. A run is skipped when the previous run’s item is still being worked on (new, taken, in progress or blocked; not in review), and when the role’s AI program is at 90 % or more of its usage window. A holder you put to sleep with “do not wake” is not woken.

The week view. “This week” shows the runs so far and ahead, with marks: done, failed or dropped, needs a look, ran, running, skipped, ahead. “Today on schedule” lists today’s runs. The list groups are “Proposals”, “On” and “Off”, with a filter All, On, Off.

Who may set a schedule. You may do anything. A team’s lead creates enabled schedules and edits or deletes its own team’s, but never edits or deletes yours. Any other agent only proposes: it shows under “Proposals” (“a lead proposed it — it runs only once you enable it”) with “Enable” and “Reject”. In Settings › Agents and teams the switch “Leads set schedules” turns the lead’s right off: schedules no person touched then pause, and a lead’s new schedule is a proposal. The rail shows “N proposals wait for you”.

Editions. The free harnsy has one schedule; harnsy Max has no limit. After a downgrade the existing ones keep running. A proposal counts once it is enabled. Sending the result of a run to a Telegram or Discord chat is harnsy Max (Connections): it is sent after the run’s item is handed in; harnsy cuts out the secrets it recognises.

Changes in 0.11.0. A live lead of a project can set the schedule of an action you allowed agents to run (harnsy Max). Items a schedule made carry a “from a schedule” mark. Plugins can ask for “every N days” schedules. A lead can hide a failed run from “Needs you”. Making a plain schedule is the same.