The dashboard now polls the aggregate every 15s (on top of the
immediate NATS-event refresh) so it stays current while watched. The
Add Device no-expiry option is gated to the Multiple devices scope - a
single device is a one-time enrollment and always keeps the 24-hour
expiry. Add-device screenshot refreshed on the multi scope.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The dashboard is rebuilt as a quiet, information-dense overview: KPI
tiles (devices, jobs/30d, success rate, failures), a job-outcome donut,
a 14-day executions timeline, and bar lists for script engine, exit
codes, top targets and most-run scripts, plus a fleet-platform donut
and a latest-executions list that drills into each job. A live
deployment banner rolls up NATS job.state events into an N-of-M
progress bar so a group run shows progress as it lands. All charts are
small hand-rolled SVG components - no chart dependency.
Backed by a new GET /api/dashboard aggregate (one read across jobs,
devices and scripts, 30-day window). Devices now show an OS-type icon
(Windows / Apple / Tux) on the list and detail header, derived with the
same normalization as the backend platform field. The dev seed gains
Linux and macOS devices and ~90 jobs spread across engines, states,
exit codes and 14 days so the charts and icons have something to show.
Screenshots refreshed.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Extracts an IPtySession seam behind the shell manager. ConPtySession
keeps the Windows ConPTY path; a new UnixPtySession drives a
forkpty-backed PTY on Linux/macOS - forkpty does openpty + fork +
setsid + TIOCSCTTY + dup2 in one native call, so the shell gets a real
controlling terminal (job control and Ctrl-C work). The forked child
touches only pre-marshaled execve/_exit pointers, so no managed
allocation or JIT happens after the fork. ShellManager and
ShellCommandListener are no longer Windows-gated; they honor the same
AllowRemoteShell policy everywhere and resolve $SHELL/bash/zsh/sh on
unix, pwsh/powershell on Windows.
Verified: agent builds both target frameworks, publishes for linux-x64,
60 agent tests pass, solution green.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Standalone setup fixes the jetstream double-nesting (store_dir is the
parent), moves the database to data/db and logs to ./logs; the agent
logs to ./Logs next to its binary. Both MSIs install under
ExecuteR\Server and ExecuteR\Agent, binaries carry ExecuteR
Server/Agent product metadata with dateversion-shortcommit as the
product version, and shipped bundles drop pdbs and the staticwebassets
manifest.
Execution reworks: targets are an add-one-or-more chip list (devices
and groups mix; each run lands in one per-device list with focusable
output), the script page gains a History section, the device page's
tab becomes Execution History grouped by script, and JOB_HISTORY_LIMIT
(default 200 per device, 0 off) prunes old jobs plus their stored
output. Functions drops the Module name placeholder and only opens the
editor on selection or New function.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The first-sign-in reset now presents only while the password is
literally the built-in default - a custom install-time password signs
straight in and clears a stale must-change flag. Bootstrap tokens
accept validMinutes 0 for no expiry (pipelines), mirrored by a No
expiry checkbox in the Add Device modal and a Never display in
Settings. Both MSI dialogs lose the literal ampersands (NoPrefix
labels render & as-is), get much shorter texts with real line
spacing, and the network page relayouts with room to breathe.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
MSIs, ZIPs and checksum files rename to ExecuteR-Agent-* and
ExecuteR-Server-* across the packaging scripts, the CI staging/upload
globs and the release asset filter. The agent-package bundle names the
server serves (Agent.msi, Agent-<rid>.zip) are internal delivery paths
and stay unchanged. Takes effect on the next release build.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The Networking section opened with "plain HTTP only, will not be
added", written before Self-Signed TLS became the default and
contradicting the subsection right below it. It now states the actual
model - encrypted listener by default, public termination at the edge
- and recommends Nginx UI as the edge.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>