React console, StifleR sign-in, runs with bulk logs, Windows PE, shell choices and agent auto-upgrade #18
Reference in New Issue
Block a user
Delete Branch "dev"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
React console, StifleR-style sign-in, runs with bulk log downloads, Windows PE and remote shell choices.
Console
Runs and jobs
COMPUTERNAME.JobID.yyyy.MM.dd.HHmmss.log.ScriptName.RunID.….log.ScriptName.RunID.….zipwith oneCOMPUTERNAME.JobID.….logper device. The endpoint isPOST /api/executions/{runId}/output/archive.Sign-in and access (as in StifleR)
claim=value) to ExecuteR's own roles, device scopes included.auth-resetandAUTH_FORCE_LOCAL.Windows PE
GET /api/devices/{clientId}/history).initialize, which uses the Service Control Manager APIs.foregroundstill works fromstartnet.cmd.Remote shell
Agent upgrades and the watchdog
ExecuteRWatchdog, about 12 MB) that restarts a dead or stalled agent.Breaking changes
chore!: the license changes to proprietary (Grace Solutions).feat(webui)!: the React console replaces SvelteKit./login→/sign-in. Access comes from group bindings; the old default role has no equivalent.Testing
🤖 Generated with Claude Code
- PUT /api/triggers/{id} edits a trigger in place (script, target, cadence, arguments, name) instead of delete-and-recreate. - POST /api/triggers/{id}/run fires a trigger now against its current target as one execution, leaving its cadence and enabled state alone. - POST /api/triggers/preview returns the next N fire times, evaluated server-side in the schedule's time zone (DST-aware). - Triggers carry an optional Name and the LastRunId of their last firing so the UI can drill straight into that execution. - Validation: bad time zones are reported as such (not as a cron error), enabled one-shots in the past are refused, never-firing crons rejected. - Device-scoped roles can only aim triggers inside their scope (a visible device or a group whose members they can all see; never "all devices"). - Event triggers now pass their captured arguments (they were dropped). - The sweep and run-now share TriggerExecutor; trigger changes are audited under a new "automation" category; deleting a trigger drops its once-per-device run records. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>POST /api/jobs takes ClientIds alongside ClientId/GroupId/GroupIds; the targets are deduplicated, scope-filtered and dispatched under one RunId, which the response now returns. OnlineOnly skips devices that are not online (reported in SkippedOffline) instead of queueing for their return. A lone ClientId keeps its original contract (201 + JobDto, 404/409). Fixes: - A GroupIds-only request was rejected ("Target exactly one of clientId or groupId"), so multi-group runs from the script page never started. - Execution summaries left Dispatched jobs out of every tally; they now count as pending. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>Groups now form a tree (ParentId, at most 8 levels) and gain a Folder kind that holds no devices of its own. A group's effective membership includes every group nested under it, so running, scheduling or scoping a role on a parent reaches its whole subtree. - POST /api/groups/{id}/move re-parents a group; moves into itself or its own subtree, or past the depth limit, are refused. - GroupMembership evaluates every group once per request (one read of groups, static members, devices and, only when needed, inventory) instead of re-reading the fleet per group on the list endpoint. - Group DTOs carry ParentId, DirectMemberCount and OnlineCount; device rows carry their direct GroupIds so the console can draw the tree and filter by node; a device's groups mark ancestors as Inherited. - Deleting a group lifts its children to its parent and disables triggers that targeted it (with the reason recorded). A group that scopes a role is refused: dropping it would silently widen the role to all devices. - Switching a static group to another kind drops its member rows; folders and dynamic groups refuse explicit members; member edits are batched, ignore unknown devices and are audited, as are updates and deletes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>Output objects were sent as PSObject.ToString(), so anything that was not already a string came back as a type name or a terse dump: "System.Collections.Hashtable", "System.Diagnostics.Process (svchost)", "@{Name=widget; Size=42}". Both PowerShell engines now pipe the script's output through `Out-String -Stream -Width 4096`, PowerShell's own formatter: objects arrive as their table or list view (a hashtable's Name/Value rows, properties as columns), still streamed line by line as they are produced, wide enough that tables are not cut short with "…" at 80/120 columns. Strings pass through unchanged; trailing padding is trimmed; the exit code is unaffected. Bash output was already text. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>- GET /api/jobs/{jobId}/output/download: one job's complete stored output as .txt with a header (device, state, exit code, times). - GET /api/executions/{runId}/output/download: every target of a run in one file, a section per device with its state and exit code. - Both stream straight from the database (no size cap, nothing buffered), tag non-output streams ("[ERROR] …"), take ?timestamps=true, name the file script_device-or-run_time.txt, and respect device scope. - Console: the output drawer's download now fetches the full log from the server (it used to save only the lines currently loaded and filtered); runs get Download Output on the Jobs page and on a script's Executions tab. README documents downloads and the new output rendering. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>- Run Script is a tabbed modal (Script, Devices, Groups, Parameters, Review) with the same mechanics from a script (script fixed, opens on Devices) and from devices (selection preselected, opens on Script). Devices are searchable and multi-select with Choose Results. - Starting a run opens /runs/{runId}: one segmented progress bar, counters for Targets, Online, Pending, Running, Succeeded, Failed and Skipped that filter the target list, skipped devices listed, rows drilling into output, Run Again and Download Output. - Jobs opens on Runs (recent runs across scripts with progress and source); the script Executions tab uses the same progress view. - Buttons keep their authored Title Case (no forced capitalize), as StifleR. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>POST /api/executions/{runId}/output/archive streams ScriptName.RunID.yyyy.MM.dd.HHmmss.zip with one COMPUTERNAME.JobID.yyyy.MM.dd.HHmmss.log per chosen job (every job when none are chosen), scoped like the other downloads. The run table gains checkboxes (skipped targets have no log) and Download Logs. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>When a device's hostname or OS caption changes — at enrollment, presence or inventory — record a "device" audit event on its client id (device-renamed "MINWINPC-ABC → LAB-PC-01", device-os-changed "Windows PE 10.0.26100 → Windows 11 10.0.26100.4351"), only when the value actually changes. Every (re)enrollment records device-enrolled with the name and OS it enrolled as, and the bootstrap-succeeded row now carries the OS. GET /api/devices/{clientId}/history returns the trail newest first (devices.view, device scope honored). No schema change. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>GET /api/agent-packages/{sha256} serves one catalog package by content hash (what an upgrade command's DownloadUrl points at). A queued upgrade whose device never came back is cancelled with reason "expired". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>- Catalog: every node imports the upgradable packages it can see (version from the VERSION marker) into <data>/agent-packages/<version>/, offloads them to S3 when agent offload is on, and prunes to KeepVersions, never the newest, an open upgrade's target or a device's rollback target. GET/DELETE /api/agent-versions. - GET /api/agent-packages/{sha256}: anonymous, ranges, no per-address limit; falls back to the install package or the S3 copy. - POST /api/agent-upgrades (devices and nested groups, scope applied) and /rollback queue rows with skip reasons; cancel while queued; list. - Scheduler (with the schedules, SCHEDULE_WORKER): every 15 s it sends the next batch of queued online devices, sized so each starts within StartWithinMinutes (at least 10 a batch, 15 s agent jitter); no-report deadlines, presence-confirmed success, 7-day queue expiry, automatic upgrades (never a downgrade, never a failed target again). - Agent upgrade events on the agent event subject update rows, write Device History (agent-upgraded, agent-rolled-back, agent-upgrade-failed) and tell consoles. Presence records the agent runtime. - Settings › Agent Upgrades (GET/PUT /api/settings/agent-upgrades). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>React console, StifleR sign-in, runs with bulk logs, Windows PE and shell choicesto React console, StifleR sign-in, runs with bulk logs, Windows PE, shell choices and agent auto-upgrade