NetRatel v0.1.3-beta.3 — software inventory and estate intelligence

This beta adds tenant-scoped software inventory and estate intelligence from
PR #453, implementing
#452. It includes
the beta.2 task-history, Script Library, policy administration and operations
improvements from
PR #451 and
PR #448.

Software inventory

• Updated Windows and Linux native clients collect installed software on their
  first authenticated connection. Tenant scheduling defaults to enabled every
  seven days and is configurable beside Auto Update in tenant settings.
• Open Software Inventory from a client card for a full-screen snapshot,
  collection status and change history. Opening an inventory at least 30 minutes
  old requests a refresh when authorized; Refresh inventory requests one
  explicitly regardless of age. Offline requests remain queued.
• Use Estate → Software Inventory for searchable, sortable, server-paged
  installations, software prevalence with distinct device counts, estate change
  history and filtered CSV export.
• Windows collection reads uninstall registry metadata and available AppX/MSIX
  providers. Linux supports dpkg, rpm, pacman, snap and flatpak when installed.
  Collection never installs packages or reads license keys. macOS software
  inventory is unsupported in this beta.
• Durable, compressed, byte-bounded chunk uploads survive interruption and
  replay. Only a complete successful scan replaces the previous inventory and
  records additions, removals and version changes; partial or superseded scans
  preserve the last complete snapshot.

API and MCP

The shared HTTP/stdio netratel_software tool and SoftwareInventoryClient
provide tenant policy, client status/snapshots, refresh, installations,
prevalence and change history. Reads do not initiate collection. Refresh and
policy changes require explicit confirmation and current delegated operation
authorization. Tenant isolation, application permissions and audit events apply
to inventory reads, exports and mutations.

See the software inventory guide for supported
sources, freshness rules, permissions, limits and API/MCP examples.

Upgrade and testing

Use this release's matching archives, SHA256SUMS, publication.json and
digest-pinned Compose bundle. Follow release installation
and self-hosting. Run the one-shot migrations
service before starting updated API replicas: AddSoftwareInventory adds
inventory tables and indexes. Update API, Web and MCP together, and update
Windows/Linux clients to collect inventory. Existing devices have no snapshot
until the updated client connects. Retain the migration when rolling application
binaries back; removing it deletes inventory and change history.

For owner acceptance, connect an updated Windows and Linux client, verify the
first scan, inspect client and estate views, test filtered export and explicitly
refresh inventory. Confirm partial scans preserve a previous complete snapshot,
offline collection resumes after reconnect, and tenant policy/access controls
behave as documented. Native Windows and distribution-specific package-manager
execution, deployment smoke and published-client runtime acceptance remain
owner-run checks. The Windows desktop proof of concept remains disabled by
default as in beta.1.

The generic hosted release workflows validate source, build native archives and
publish the five images and downloadable assets. publication.json records
build/distribution integrity separately from pending owner functional acceptance.

Full changelog: v0.1.3-beta.2...v0.1.3-beta.3

Distribution verification

Release build and publication passed for commit 9103886b792b62af7851d7d027e7ba6e843f50ed. All 5,424 tag-build tests passed with zero failures or skips. The 15 public assets and all 14 checksum entries were independently downloaded and verified. All five public images passed scans and anonymous digest pulls; the Compose bundle pins their immutable digests. publication.json records complete build/distribution integrity. Native runtime and deployment functional acceptance remain pending owner testing. Stable/latest remains v0.1.2.

NetRatel v0.1.3-beta.2 — task previews and script workspace

Task history

Expand a run directly in the history table for target, tenant, timing, status, exit code and request details. A compact scrolling preview shows final console output when available; the far-right link still opens the complete task/output view. Details load only for the expanded run, with explicit loading, empty, large-output and failed-read states.

Script Library

• Compact single-line tree names, restored nested indentation and folder counts including matching scripts in subfolders.
• Delete beside Save above Monaco; click the script name to rename in place. Name and code save together with the existing source-revision checks.
• A full-screen Monaco dialog with the same rename, Save and Delete controls. Unsaved edits survive moving between normal and full-screen views; failed saves retain the draft.
• Keyboard-selectable names and full-name tooltips.

Included beta.2 fixes

Includes PR #448: current interactive instance administrators can manage operator policies without an existing delegated MCP parent policy. Scoped callers keep their bounds, confirmations and immutable audits. Jobs actions and Investigations layout are more compact, and expanded Monitoring alerts use full-width evidence cards.

The Windows desktop proof of concept remains disabled by default, as delivered in beta.1.

Installation and retest

Use the matching archives, SHA256SUMS, publication.json and digest-pinned Compose bundle from the completed publication. Follow release installation. These UX changes add no database migration.

After deployment, expand completed, failed and large-output tasks, then follow the full-output link. Browse a nested script folder, rename a disposable script, edit its code in full screen, return with an unsaved draft, save and reload, then delete the disposable script from the toolbar.

Operator guide · Full release notes · PR #451 · Closes #449 and #450.

Build/distribution integrity is recorded in publication.json separately from owner deployment acceptance.

NetRatel v0.1.3-beta.1 — Windows desktop POC disabled by default

Client fixes

• Disable the unfinished Windows remote-desktop and interactive-helper proof of concept by default. The Client no longer starts its desktop gateway or advertises desktop support unless explicitly opted in.
• During an upgrade, retire the exact NetRatel desktop-helper scheduled task, HKLM Run entry and launcher files; stop only versioned resident desktop-helper processes, without stopping the Client service or terminal.
• Prevent same-session helper replacement loops with a single owner, and apply reconnect backoff even after normal disconnects.
• Keep telemetry, terminal, commands, jobs, file/log transfer and client auto-updates operational.

Canary acceptance

Install the Windows client from the completed release artifacts. Verify the main NetRatel.Client service and terminal stay connected, no resident desktop helpers remain by default, and sample CPU for at least a minute. The optional experimental override is NETRATEL_REMOTE_DESKTOP_POC_ENABLED=true on the Windows Client service; leave it unset for production. See docs/client/computer-use.md.

Issue #442 · PR #443. This prerelease is for owner acceptance, not stable/latest promotion.

NetRatel v0.1.2

NetRatel 0.1.2

Distribution verified: 15 downloadable assets and five immutable container images.

Stable promotion of the tested 0.1.2-beta.5 functionality. This promotion updates the release version and documentation; application behavior is unchanged from beta.5.

Highlights

• AI Ops → Chat: general tenant Netclaw conversations with saved history, starter prompts, formatted responses, copyable code, and existing approval and recovery controls.
• Dashboard and client navigation: compact tenant selection, clear section spacing, online/offline links, button-style alert actions, and reliable exact-client filtering.
• Integration credentials and policies: guided HTTP MCP credential creation, reviewed access edits, atomic policy setup, and compact policy management.
• Optional Windows computer use: permission-controlled observation and input for selected applications, disabled by default.

Installation

Use the Compose bundle with its immutable image digests, SHA256SUMS, and publication.json. Upgrade from beta.5 adds no database migration. Upgrades from 0.1.1 include the migrations delivered during the 0.1.2 beta series.

Full release notes · Installation guide · Release PR #441

Verified source and distribution

Source: 00c46d33fe6f2e60205df494169034459ed3b7e8.

• Required PR validation passed in 17m51s and exact merged-main validation passed in 17m54s, both within the required 20-minute budget.
• PR, main, and tagged source each passed 5,364 regressions and 177 source/release contracts, with zero regression failures or skips.
• The all-target release build passed for CLI/Compose, Linux and Windows MCP, and native Linux, Windows and macOS clients, including the Windows MCP archive checks.
• Publication completed successfully on 29 October 2026 at 20:30:14 Africa/Johannesburg. All five image scans and anonymous digest pulls passed; all 15 public assets were uploaded and verified.
• All 14 checksum entries passed staged verification and public-download readback. The publication record, asset hashes, authenticated build receipt, Compose bundle and five pushed image digests were also independently cross-checked.

The publication record keeps build/distribution integrity and owner deployment acceptance separate.

NetRatel 0.1.2-beta.5

NetRatel 0.1.2-beta.5

This beta adds a dedicated Netclaw chat workspace and improves the landing
dashboard's layout and client navigation.

AI Ops Chat

• AI Ops → Chat opens a tenant-scoped conversation using the tenant's existing
  enabled Netclaw connection. Send the first question without choosing systems,
  a title or investigation prompts.
• A responsive workspace provides separate chat history, title search, starter
  prompts, a multiline composer, formatted assistant replies and copyable code.
• Saved transcripts, live output, tool decisions, interrupted-request recovery
  and archive handling reuse the existing durable Netclaw conversation pipeline.
• General chat attaches tenant scope and platform instructions, without selected
  system observations, alert context or investigation prompt snapshots. Actual
  tool calls continue to use the configured Netclaw and NetRatel permissions.
• Connection setup links preserve the tenant. Global search distinguishes chats
  from investigations and opens each in the correct workspace.

See Netclaw AI operations
for the operator workflow and permissions.

Dashboard and clients

• The active-alert and recent-job sections have a consistent 20px gap, and the
  dashboard tenant selector is compact and left aligned.
• Online clients and Offline clients link to the client directory with
  the selected tenant and corresponding presence filter applied.
• Alert-row Alerts and Client actions use outlined buttons with icons.
• Client links carry an exact tenant and client filter. Legacy UUID search links
  also resolve, and directory filters remain represented in browser navigation.

Installation and validation

Use the matching archives, SHA256SUMS and publication.json from the completed
beta release.
The Compose archive pins the five published container images by digest. Follow
release installation and
self-hosting for an existing installation.

This update adds no database migration. General chats and investigations share
the existing conversation storage while retaining separate history lists. The
source includes focused payload, persistence, authorization, navigation and
component regressions. The publication record identifies completed distribution
verification separately from owner deployment acceptance.

Tracked in #437, #438 and #439.

NetRatel 0.1.2-beta.4

NetRatel 0.1.2-beta.4

Addresses #431,
#432,
#433 and
#434.

HTTP MCP creation now follows Connection → Server access → Tenant access →
Policies → Review & create. Each selected tenant gets one approved base policy;
server permissions get a separate Server access base. All access and narrower
choices expose supported operations, paths, execution/onboarding limits and exact
expiry. A responsive grouped review shows the connection, grants and policies
together. Credential and policies commit atomically, with a bounded encrypted
one-time-secret handoff for a lost response. Existing access editing reviews
and reconciles the corresponding base policies alongside grant changes.

Policy management shows active bases with nested client/operation exceptions.
Explicit deny wins; children remain inside their parent's identity, scope,
operation ceiling, lifecycle and expiry. Named tenants and searchable principal,
client and catalog operation choices replace identifier entry. Actions read
Edit, Disable, Revoke and Delete. Single and bulk deletion retain immutable
audit/tombstone history while removing effective access and ordinary inventory.
Explicit legacy consolidation preserves exact rule restrictions and reports
conflicts for separate review. Historical inactive records remain available
through the history filters; migrations do not rewrite existing grants.

Run the supplied migrations before starting the new API/Web. The product version
remains controlled solely by Directory.Build.props; use the matching verified
publication and digest-pinned Compose bundle described in
release installation.

Focused source, component and PostgreSQL checks cover setup transactions,
secret recovery, policy hierarchy/lifecycle and legacy consolidation. Public
build/distribution integrity and owner deployment acceptance are separate states.
Owner retesting should reconnect with a new credential, read an approved tenant,
inspect an onboarding preview, exercise a scoped deny and cleanup, and check the
review screen in light/dark and narrow/wide layouts. Runtime connectivity,
capability and owner acceptance are not inferred from saving policies.

See HTTP MCP setup and
policy management.

NetRatel 0.1.2-beta.3

NetRatel 0.1.2-beta.3

Addresses credential access editing and creation follow-up #429.

Credential access

The Details page passed the literal string detail.Id into the access editor's
string parameter. Its request-history GET therefore used an invalid credential
identifier and returned HTTP 400 with review_credential_id_invalid, which the
editor replaced with a generic loading error. The page now passes the selected
credential's actual ID. This binding affects both local and OIDC accounts.

Access loading, review and save failures now show the failing stage, HTTP status,
safe failure code and available correlation reference. Matching Web/API log
events contain safe diagnostic fields. Failed initialization still withholds the
editable snapshot until current grants, authority and any pending review have
loaded together; retries recover the same submitted review.

Credential creation follows Connection → Server access → Tenant access →
Review & create. Server and tenant permissions have separate selectors,
selection counts and labelled information popovers. Either individual scope may
be empty, with at least one permission required overall. Back/Next retains the
draft and successful creation retains the one-time secret acknowledgement.

See the updated HTTP MCP setup guide.

Verification scope

The rendered page regression reproduces the literal-ID request before the fix
and covers reopening credentials with small and multi-tenant grant sets. Focused
API tests exercise the actual invalid-ID response contract and local/OIDC
review/application without replacing the secret or exact expiry. Browser fixture
coverage checks the revised wizard in light/dark and narrow layouts.

These checks do not establish authenticated acceptance on an owner deployment.
Public distribution integrity and owner functional acceptance remain separate
states in the release publication record.

NetRatel 0.1.2-beta.2

Changes

Manage existing HTTP MCP credential access in the browser

Open Integrations → API & MCP credentials → Details → Configured access → Edit access to maintain an existing credential.

• Add another authorized tenant to the same credential.
• Change or remove tenant permissions and edit server-level permissions independently.
• Review the complete resulting access before applying it.
• Apply an eligible owner's explicit approval, or complete another administrator's review in the browser. Reopening the editor recovers pending requests, and approved requests are applied automatically.
• Refresh saved grant counts, Details and current admission after application.

Grant edits preserve the credential ID, saved secret, connection purpose, canonical MCP URL and exact UTC expiry. Operation policies remain a separate, explicitly reviewed prerequisite.

The setup and Netclaw guides explain credential scopes, the browser editing workflow, pending-review recovery and the alternative MCP request/approve/resume workflow.

Implemented in #427, resolving #426, with the documentation foundation in #425.

Opt-in Windows computer use

Includes #424: provider-neutral computer use through the enrolled Windows Client gateway and existing interactive Remote Support helper. It provides separate view/control permissions, explicit application/window selection, bounded observations and actions, durable ownership and audit, cancellation, pause, manual takeover and session cleanup. The feature includes an optional Cua Driver provider, a limited native Windows provider, setup documentation and an owner-run Windows canary procedure.

Computer use is disabled by default on both API and Client. The optional Cua Driver sidecar is installed separately from the normal Client archive.

Release validation correction

Includes #428: corrects the credential Details regression's asynchronous close/reopen synchronization while preserving the saved-grant, admission and stale-response checks. The v0.1.2-beta.1 build stopped before package or image publication; its tag is retained unchanged. This beta contains the corrected source.

Retesting credential access

1. Record an existing HTTP MCP credential's ID, exact expiry, tenant grants and server permissions.
2. Add a second authorized tenant through Edit access, review and apply.
3. Reload Details and confirm the saved counts and retained grants.
4. Verify that the existing client still authenticates with its saved secret and can perform the separately approved read in each tenant.
5. Remove only the second tenant's access and confirm the first tenant remains usable.
6. Change or remove an existing tenant permission and verify that other tenant grants are unchanged.
7. Change server-level permissions independently and confirm that the credential ID, secret and exact expiry remain unchanged.
8. Exercise pending review, reopening and failed-save recovery.

Distribution and acceptance

The hosted publication workflow supplies the deployment bundle, CLI and MCP packages, native Client archives, SBOMs, SHA256SUMS and publication.json. The publication record identifies the exact public source commit and immutable image digests.

Build and distribution integrity are verified separately from owner functional acceptance. Functional acceptance, including the Windows desktop canary, remains pending owner retesting.

Setup: HTTP MCP guide · Netclaw guide

NetRatel 0.1.2-beta.1

Release build failed; installable packages and container images were not published. The tagged build stopped on a component-test close/reopen synchronization failure. A corrected 0.1.2-beta.2 release is being prepared. This tag is retained unchanged for traceability.

Changes

Manage existing HTTP MCP credential access in the browser

Open Integrations → API & MCP credentials → Details → Configured access → Edit access to maintain an existing credential.

• Add another authorized tenant to the same credential.
• Change or remove tenant permissions and edit server-level permissions independently.
• Review the complete resulting access before applying it.
• Apply an eligible owner's explicit approval, or complete another administrator's review in the browser. Reopening the editor recovers pending requests, and approved requests are applied automatically.
• Refresh saved grant counts, Details and current admission after application.

Grant edits preserve the credential ID, saved secret, connection purpose, canonical MCP URL and exact UTC expiry. Operation policies remain a separate, explicitly reviewed prerequisite.

The setup and Netclaw guides explain credential scopes, the browser editing workflow, pending-review recovery and the alternative MCP request/approve/resume workflow.

Implemented in #427, resolving #426, with the documentation foundation in #425.

Opt-in Windows computer use

Includes #424: provider-neutral computer use through the enrolled Windows Client gateway and existing interactive Remote Support helper. It provides separate view/control permissions, explicit application/window selection, bounded observations and actions, durable ownership and audit, cancellation, pause, manual takeover and session cleanup. The feature includes an optional Cua Driver provider, a limited native Windows provider, setup documentation and an owner-run Windows canary procedure.

Computer use is disabled by default on both API and Client. The optional Cua Driver sidecar is installed separately from the normal Client archive.

Retesting credential access

1. Record an existing HTTP MCP credential's ID, exact expiry, tenant grants and server permissions.
2. Add a second authorized tenant through Edit access, review and apply.
3. Reload Details and confirm the saved counts and retained grants.
4. Verify that the existing client still authenticates with its saved secret and can perform the separately approved read in each tenant.
5. Remove only the second tenant's access and confirm the first tenant remains usable.
6. Change or remove an existing tenant permission and verify that other tenant grants are unchanged.
7. Change server-level permissions independently and confirm that the credential ID, secret and exact expiry remain unchanged.
8. Exercise pending review, reopening and failed-save recovery.

Distribution and acceptance

The hosted publication workflow supplies the deployment bundle, CLI and MCP packages, native Client archives, SBOMs, SHA256SUMS and publication.json. The publication record identifies the exact public source commit and immutable image digests.

Build and distribution integrity are verified separately from owner functional acceptance. Functional acceptance, including the Windows desktop canary, remains pending owner retesting.

Setup: HTTP MCP guide · Netclaw guide

NetRatel v0.1.1

NetRatel 0.1.1

NetRatel 0.1.1 is a stable release with a focused update to the operator
experience and current documentation.

Operator experience

• Integration credentials: a structured details dialog groups connection
  metadata, lifecycle dates, tenant and server permissions, current admission,
  and policy details. Status chips, expandable sections and responsive scrolling
  make the information easier to inspect. Existing permission and credential
  checks remain in place.
• Flow history: History opens a dialog immediately, with loading and error
  states, published versions, recent runs and selected-run results. Closing it
  preserves the flow list and returns keyboard focus to the invoking control.
• Client management: update attempt details expand below their summary in a
  full-width MudBlazor panel. Version observations, server confirmation and
  automation metadata have space to wrap without stretching the table columns.
• Monitoring: Active alerts initially selects Firing, including tenant
  links. Pending, Unknown, Suppressed and All states remain explicit choices,
  and deliberately supplied state filters are respected.

Documentation

The README links to the current releases without a pinned RC or beta. Obsolete
test-campaign runbooks and their dated requirements have been removed from
maintained guides. Product setup, operations, authentication and release
verification instructions remain available through the
documentation index.

Installation and upgrade

Download the matching Compose or native-client archives, SHA256SUMS and
publication.json from the GitHub release.
Use the image digests included in the completed Compose bundle and retain the
existing configuration and persistent state. Follow
release installation and the
self-hosting guide.

This update introduces no database migrations or MCP/API contract changes.
The existing generic workflows validate the source, build the downloadable
artifacts, and publish the five container images with their checksums and
publication record. Release distribution and deployment acceptance are recorded
separately; publishing does not change an installation's rollout controls.