The Automations page: one Edit panel and Run now

[suleimansh]

The Automations page gets one Edit panel for every row, two groups of rows, a real switch, one line that says where a row stands, and a "Run now" button.

👤

• Editing a skill's row and editing a row I made looked different, and the pace could be set in two places. Now every row has one "Edit", and it opens one panel with the same parts: what it does, when it runs, how many at once, what its runs publish.
• A skill's row shows what it does greyed. A row I made lets me change its prompt and its shell line there. "Remove" is only on rows I made.
• My rows and the project's rows are two groups.
• A real on/off switch, and one clear line per row: on or off, when it last ran, "No work", "Last run failed".
• A "Run now" button on every row.

🤖 automated · Opus 5.5, effort high

The page

• A project's rows come in two groups: "Your automations" (made with "New automation") and "From the project's skills". A group shows only when it has rows. A row of yours says "only on this machine" or "shared with the project".
• The checkbox is a switch.
• One line says where a row stands: "On" or "Off"; "Last ran 3h ago", which opens that run, or "Never ran"; and, while it is on, what the scheduler last decided: "No work", "Not due yet", "One is already running", "Next: today 10:00". A failed last run is "Last run failed 3h ago", in red.
• A second, quieter line keeps the row's picks: when it runs, how many at once, what its runs publish.

One Edit panel

• A skill's row: what it does is greyed (its words, its shell line, and where they are changed). Its pace may follow the skill, as before. Nothing of it changes a tracked file.
• A row you made: the prompt and the shell line (with "Try it") are in the same panel, with the same pace control, the number of agents and the publish level. One Save sends only what changed.
• One place for the pace. For a row you made, the pace you pick is the automation's own and goes into its file with its words; this machine keeps only a time of day. Before, the form set the file's pace and the row's Edit set a second one for this machine.
• When Save wrote a row's file, the panel says so before it closes: what is left to commit for a shared row, and that the row shows the change once the scheduler has looked.
• A Save that stops midway says what was saved already.
• A prompt made longer by hand than the panel can send (4000 characters) does not hold the row's picks: they save without the words.
• When a row's file was changed by hand, the panel still opens: it says why the words cannot be changed here and leaves them alone.
• "Remove" is inside the panel, and asks first.
• One panel or form is open at a time. While one holds a change that is not saved, the other "Edit" buttons and "New automation" wait, and Escape does not close it.
• The "New automation" form has the same fields for what it does and when it runs, so a time of day can be picked there too.

Run now

• "Run now" starts one run of the row at once: agent-scheduler now <command>. It needs no scheduler running.
• It does not ask the switch, the pace or the quota: a person asked for the run.
• A row with a shell line starts only when the line prints something, and the run is handed what it printed. When it prints nothing the row says "Nothing started. No work: its shell line printed nothing."
• How many at once still holds ("One is already running"), and so does "its skill is not on main yet".
• The run counts as the row's last start, like any run of it: its pace counts from it. So "Run now" at 09:00 on a row that runs every day at 10:00 is that day's run.
• The dashboard waits 30 seconds for a command. So the shell line has 10 seconds here, and a start that is not ready within 20 seconds is given up before anything is written.
• The run started is the row's last run at once, on the page too.
• A "Run now" that is still starting holds no other row's switch.

Under it

• The scheduler lists each row's last run (which run, when, whether it failed) where it listed only a failed one.
• A run that could not be started leaves no record that says "running". This holds for the scheduler's own starts too.
• A shell line that runs out of its time says "it took longer than N seconds", where it said only that the command failed.
• The page's top line says "Every row starts switched off: it runs on this machine only once you switch it on here." It said every pick is this machine's, which is no longer true of a shared row's pace.
• The dashboard offers its modules a Switch.

Checked

• One fresh reviewer read the whole change and found ten things; each is fixed or listed under Known, with a test for each fix.
• On a rig of my own in a real browser (own port, own settings folder): made a row with a time of day, "Run now" started a real agent that answered, edited its prompt, pace and number in one Save, removed it; saved a pace and a publish level on a skill's row; "Run now" on a row whose shell line prints nothing.

Known

• If the dashboard ends "Run now" in the last moment, after the run's record is written and before the run starts, the record says "running" until the scheduler looks again (it then closes it). The 20 seconds above make this rare. The row then says "No answer in time. A run may have started all the same", not that nothing started.
• A row's file-side words (its description, its pace without a time of day) still show on the row only once the scheduler has looked. The next pull request makes them show at once.

DECISIONS.md

In packages/agent-scheduler/DECISIONS.md. The first only writes down the pick above (one place for the pace):

A row has one place for its pace on the Automations page, whoever made it: its Edit panel, the same for every row. For a row a person made, the pace picked there is the automation's own, saved into its file with its prompt and its check, and their machine keeps only a time of day. For a row a skill brings, it is that machine's pick, and the skill's pace is one of the choices. Picked over two places, the automation's pace in one form and the machine's pick in another, which a person could not tell apart.

The second is new, for "Run now":

A person may start one run of a row at once, from the Automations page: whatever its switch, without waiting for its pace, and whatever quota is left, as for any run a person starts. A row with a check still starts only when the check finds work, and its run is handed what the check printed; the number of agents at once holds, and so does that its skill is where a run's checkout starts. The run counts as the row's last start, so its pace counts from it. Picked over starting the command from the launcher: that run gets neither the row's publish pick nor what its check found.

And the dashboard-part bullet names the new command (now).

Logic files not updated

By the person's choice the LOGIC.md files are not updated in this pull request (#2038). They are brought in line later, in one pass.