Fresh captures across the clone-bearing surfaces: schedule rows with
Pause/Edit/Clone showing all four starter cadences, the groups page
with Windows Servers selected (its seeded platform rules in the
builder and Clone in the editor header), a saved Function with its
Clone action, the script editor header, the Script Configuration
strip, and the Access roles table with Clone on every row.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Each surface clones in place: the script editor copies its full current
state (content, engine, parameters, secrets, files, Functions) and
switches to the copy; Functions clone from the editor panel; schedule
rows copy the cadence (assignments stay with the original); group
clones carry rules or, for static groups, the member list; role clones
copy permissions and device scope — but never OIDC claim values, so
identity mappings stay unambiguous — and work on system roles too,
turning Admin/Operator/Viewer into templates. Copies land as
"Name (copy)" with collision-free numbering against unique-name tables.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The README intro finally says what the product is now: cross-platform
agents (Windows/Linux/macOS, x64 + arm64) with three script engines and
per-platform service integration. "Function modules" is Functions in
the remaining prose and gallery, run values are execution values, and
the gallery caption for the define strip reflects Script Configuration.
New capture: the forced first-sign-in password reset (also exercised
live — the shot run set a real password and landed signed in).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The define strip is titled Script Configuration and every section
carries its own header — Parameters, Secrets, Files (S3), Functions —
instead of one mashed headline. Directory file deliveries now refuse a
leaf destination: the server rejects destinations whose last segment
looks like a file path (extension heuristic that tolerates version-like
dots), and the editor shows the same warning inline as you type.
Screenshots refreshed.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Completions now include every file binding as $Files.Name, labeled with
its delivered type (FileInfo, or DirectoryInfo for recursive prefixes),
alongside the existing parameter and $Secrets entries. Fresh captures:
the define strip with a Files (S3) binding, the fully vertical
execution flow, the device header with the copyable client id, and the
network tab titled by interface name with its copyable Interface row.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Scripts declare file bindings in the define strip alongside parameters,
secrets and Functions: S3 objects — or whole prefixes delivered
recursively — that download to the device before execution. The server
lists and presigns everything once at dispatch (shared across group
fan-outs; failures surface before any job rows exist, like secrets),
so agents never hold S3 credentials.
On the device the destination path gets full expansion (%VAR% natively,
$env:/$(...) through a short-lived runspace regardless of engine), items
stream to temp files and move into place, relative keys are checked
against traversal, and every entry lands in a case-insensitive ordered
dictionary: $Files.Name is a FileInfo, or a DirectoryInfo for prefixes.
Per-entry continue-on-failure logs a warning and still runs the script
($Files.Name.Exists reveals what arrived); otherwise delivery failure
fails the job before execution. PowerShell 5 gets the same $Files via
typed literals; bash gets one env var per entry.
The execution flow below the editor is now fully vertical — Execution,
Schedules and Triggers each get a full-width row.
Verified with real HTTP round-trips: single files, recursive directory
trees, 404s under both failure modes, server-side resolution errors,
and path-traversal refusal (9 new tests; suites at 58/63/89, svelte
clean).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Dynamic-group evaluation ran every device''s inventory blob through the
JSON deserializer on every use — fine at dozens of devices, the hot
cost at thousands. A singleton InventoryReportCache now keys parsed
snapshots by the inventory UpdatedUtc: fleet-wide evaluation probes
timestamps only, fetches JSON just for snapshots that changed, parses
those once, and prunes departed devices. Steady-state sweeps touch no
JSON at all.
The device page shows the client id as a single-line copyable chip
right under the device name (breadcrumb shows the hostname now), and
the Identity card drops the redundant wrapped row.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The backend image build context has no assets directory, so the
unconditional ApplicationIcon path broke the container publish (linux
images need no exe icon anyway). Full checkouts — local and the CI
binary jobs — still embed the committed icon.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Standalone setup marks the account (INITIAL_ADMIN_MUST_CHANGE) whenever
the password was left at admin — including a literal "admin" passed via
the flag or kept in the MSI wizard. Valid credentials then return a
must-change signal with no session; the sign-in page flows into a
set-new-password form, and POST /api/auth/change-password (rate-limited,
credential-authenticated, CSRF-exempt like login) sets the password,
clears the flag and completes the sign-in in one step. The endpoint
doubles as self-service password change for any local account.
Also: platform groups now work from the moment of enrollment — the rule
field bag falls back to the device row''s OS caption/version before the
first inventory snapshot lands, so on-agent-ready triggers scoped to
platform groups can''t race the first inventory report.
Covered end to end: login returns must-change without a cookie, wrong
current password refused, the change issues a full admin session, and
re-login uses the new password cleanly.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
No flags needed: setup writes the admin/admin sign-in by default (the
flags remain as overrides), prints the first sign-in guidance, and the
server MSI wizard matches with lowercase admin/admin defaults.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Adapters now report the OS interface name — NetConnectionID joined from
Win32_NetworkAdapter on Windows ("Ethernet0"), NetworkInterface.Name on
unix ("eth0"/"en0") with the hardware description kept separately. The
device Network tab titles each adapter by interface, shows a copyable
Interface row, and rules gain a network.interface field.
The unix agent also reports os.edition: Workstation when the device
boots to a graphical session (default systemd target, installed desktop
sessions as fallback; macOS always), Server otherwise — powering two
new default groups, Linux Servers and Linux Workstations, alongside the
Linux umbrella.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
README covers the CIDR operators and os.platform field, the seeded
platform groups and starter cadences, triggers on scripts, the Script
Engine selector with pop-out/IntelliSense and the vertical execution
flow, the ExecuteR-Server rename with setup flags and in-code
nats-server download, the server MSI, bundled agent delivery, and the
win-arm64 addition to the CI matrix. Fresh captures: the new editor
layout, the execution flow with a live trigger, groups with the
default platform groups, starter schedules and the Functions rename.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
win-arm64 joins the agent RID set (published and zipped alongside the
five existing platforms in CI and releases), and the binaries artifact
now carries Server-*.msi.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
setup now lives fully in the binary to suit every platform: it accepts
--admin-user/--admin-password (written into appsettings.json on first
run only), downloads nats-server for the current OS/architecture when
the sidecar is absent (zip/tar.gz, BCL only), and wires
AGENT_PACKAGE_PATH at the bundled agent-package directory. Bundles ship
Agent.msi + Agent.zip + VERSION next to the server, so the URL install
command works immediately instead of reporting Missing. Direct binaries
are named ExecuteR-Server(.exe); container names are unchanged. The
committed icon (assets/icons/app.ico) embeds in every build, CI
included.
New Windows installer (src/Installer.Server): harvests the whole
bundle, shows an Administrator account page (defaults Admin/Admin,
ADMINUSERNAME/ADMINPASSWORD properties for silent installs), then runs
the binary''s own `setup` and `service install` — idempotent, so
upgrades and repairs never overwrite existing configuration. Uninstall
stops and removes the service. Verified end to end: MSI carries all 169
files, setup from a bare directory downloaded the sidecar, and the
booted server answered ready (db+nats+signing), signed in Admin/Admin,
served the SPA and reported the bundled Agent.msi with version and
SHA-256.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The fixture app ran the real ScheduleWorker, whose 30-second tick could
steal a due schedule between a test seeding the schedule and its
assignments — firing with zero assignments and advancing NextRunUtc, so
the test''s deterministic manual sweep found nothing due. SCHEDULE_WORKER=0
(set by the fixture) now skips registering the hosted service.
Also anchors the content root to the binary''s directory whenever a
setup-generated appsettings.json sits next to it, so the standalone
server behaves identically however it is launched — console from any
directory, SCM service, or systemd.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The editor now owns the page: full width with a toolbar (optional
IntelliSense toggle and a pop-out that fills the window, Esc restores).
IntelliSense is a curated offline provider — common cmdlets, keywords,
automatic variables, snippets, plus the script's own parameters and
$Secrets bindings — no language server. Below the editor everything
flows vertically: an Execution card (target + Execution values, the
new name for run values), Schedules, and Triggers; group fan-out and
Output sit full width underneath so output finally has room.
Triggers belong to scripts now (run on agent ready / registration,
scoped to a group or all devices) — the card lives on the script page
and the Groups page drops its trigger section.
Engine selection is labeled Script Engine with short names
(PowerShell 7 / PowerShell 5 / Bash) and a one-line hint describing
the selected engine's platform behavior. Function modules are simply
Functions everywhere.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Every deployment starts with four dynamic groups (Windows Servers,
Windows Workstations, Linux, macOS — driven by os.platform) and four
common cadences (hourly, daily 1 AM, weekdays 7 AM, weekly Sunday 2 AM,
UTC). Each family seeds only while its table is empty, so operator
edits and deletions are never recreated.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
New in/not-in CIDR operators evaluate device IPs against comma-separated
ranges using the BCL System.Net.IPNetwork (IPv4 and IPv6; bare IPs mean
equality; host bits in the base address are normalized, so 10.20.4.99/24
matches the same network as 10.20.4.0/24). Not-in is universal across
multi-homed devices: every address must be outside.
os.platform (windows/linux/macos) derives from the OS caption so rules
and the default platform groups can target an OS family without caption
gymnastics.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>