Recurring work, set once.

Pick a role of a team, say when (every weekday at 9:00, on chosen days, every few hours, or once) and write the instruction. Times follow the machine’s time zone. The schedule belongs to the role, not to one agent.

At its time harnsy puts a task on the board for the role and sends the agent online in that role one line with a link to it. If no agent is online, harnsy raises one: it reopens the role’s own session, starts a fresh one (the default) or the same one again, as you choose, or starts an agent in an empty role. When the task is submitted, or at the time limit you set (30 minutes by default), the agent is stopped again, unless it still has other open tasks.

Edit the instruction and it becomes a new version. The task links to the instruction instead of copying its text, and a run reads the version that was current at its time. The schedule’s page lists all versions.

If the machine was off or the team was paused at the time, the run happens once when it is back, as long as it is no more than 3 hours late (you can change that window). Later than that, one “missed” is recorded. There is never a burst of catch-up runs.

You can create, run, edit and delete any schedule. A team’s lead creates, runs and edits its team’s, but cannot change or delete yours. Any other agent only proposes: a proposal does nothing until the lead or you enable it. In Settings, “Leads set schedules” is the one switch: turn it off and every schedule that only agents have created, enabled or edited pauses, and a lead’s new schedule becomes a proposal.

harnsy allows one schedule. A harnsy Max key removes the limit: set as many as your teams need.