Keep up with latest product news

?run=…&step=…), so you can share exactly what you were looking at.ALL_MUST_SUCCEED join without building anything first.401 that came in before a token renewal no longer signs you out of the session. Before, this could freeze the live run view during long runs.h1. Long class names in the palette now wrap at the dots instead of overflowing.sentai-demo.mp4 / .webm).IRIS Relay 0.5.0 installs the full Relay UI through IPM and serves it directly from IRIS at /relay/index.html. No Node.js or Python server is needed outside IRIS. Relay Lite remains available at /relay/lite.html.
The IRIS-served UI includes management views, the 28-operation REST explorer, reviewed configuration changes, scheduled tasks, log paging and similarity search, audit summaries, baseline comparison and Markdown/JSON handover export. Changes use review, fresh-state checks and readback. IRIS authorization still governs each operation. HTTPS is required for remote use; HTTP is allowed only on loopback. The README documents operator roles, SQL grants, shared-origin risks and the tested Normal security configuration.
Reviewed source: 89b9d525f30c61c93ed294f1fe8c7d979df6c4bc. Codex independently ran 64 JavaScript and 29 Python tests on the isolated VPS checkout, with zero skips; GitHub CI and Pages succeeded on this commit. Claude's isolated-cloud validation passed 158 end-to-end checks using local IPM load, including 112 browser checks of the IRIS-served UI. Public registry installation will be verified independently after this release.
AI disclosure: Claude implemented and tested the IRIS-served UI; Codex reviewed, integrated and published it.
v1.0.3: added the AI-Powered Instance Monitor feature (Community Opportunity idea DPI-I-512).
Relay Lite is now served directly by IRIS after installing iris-relay 0.4.1 from IPM: open /relay/index.html over HTTPS (HTTP is allowed only on loopback). It lists log sources, pages through messages.log and rotations, and provides lexical similarity search over a bounded IRIS Vector Search index. The Lite UI needs no Node.js or Python server; the full management UI remains available through the existing Compose/Node setup.
The page requires an IRIS user with %Admin_Operate:U; search SQL permissions and index limits are documented in README. Credentials are blocked outside HTTPS or loopback, stale requests cannot overwrite a newer session, and /relay serves static files with CSP/automatic compilation disabled.
Reviewed source: 34ed98984f15fec85d54036104f1c93d9cdd474d. GitHub CI: 46 JavaScript and 29 Python tests passed. Claude tested local IPM load/uninstall and 15 browser groups in an isolated cloud IRIS; public registry installation will be checked independently after this release. The existing public demo is unchanged.
AI disclosure: Claude implemented and tested Relay Lite; Codex reviewed and published the change.

The image: docker pull ghcr.io/mxsalata/aperture:1.3.0
Changed container repository to the public one so that everyone can see it.

New editors
Clearer screens
Safety
Requires InterSystems IRIS or IRIS for Health 2026.2 or later. Upgrading from 1.0.4 keeps your agent definitions, conversations, settings and audit records.

OpsDeck 0.2.0 delivers the native IRIS-hosted operations console with responsive, available-width layouts.
Highlights:

Key Enhancements:
🧩 Closed Capability Catalog
A single allowlist of approved AI operations. The Copilot cannot invent or execute arbitrary operations.
📋 Rich Capability Metadata
Each capability declares examples, constraints, verification, and undo information, while privileges and risk come from the existing operation registry.
⏱️ Task Catalog
Ask natural-language questions about live IRIS tasks, including suspended tasks, errors, schedules, and run-as users — completely read-only.
🔎 Capability Discovery:
A read-only API exposes the currently approved capabilities and their metadata without exposing handlers or implementation details.
🧵 Structured Execution Trace
Planning and execution produce linked copilot. plan and copilot. execute traces connected to the underlying operation trace.
🛡️ Structured Failure States
Rejections and failures use machine-readable codes such as authorization_failed, resource_protected, verification_failed, and issue_still_detected.
🔐 Defense in Depth
AI output is only a proposal. Parameters are rebuilt server-side, authorization is rechecked, explicit confirmation is required, and every mutation is verified.
Disks and system operation

Migration of administrative areas (Processes, Users and Roles, Tasks, Web Applications, and Security) to the official InterSystems SysAdmin v2 API. Includes a new automated test suite validating read operations and actual mutations via the official API.

certificate-expiry-check (schedule it to be warned before a certificate expires), permissions-inventory and oauth-inventory. Read-only; no secret is ever read.Databases and namespaces

1.2.0: opening an entry of the Messages log now says how often its message was logged and since when, found with IRIS Vector Search, and Show similar entries lists them (nothing is indexed until you ask); in the online demo the index is ready from the start. Dependency updates now arrive monthly and each merged batch is a patch release of its own (1.1.1 was the first). The README links the video walkthrough and names every contest bonus.

1.2.0: opening an entry of the Messages log now says how often its message was logged and since when, found with IRIS Vector Search, and Show similar entries lists them (nothing is indexed until you ask); in the online demo the index is ready from the start. Dependency updates now arrive monthly and each merged batch is a patch release of its own (1.1.1 was the first). The README links the video walkthrough and names every contest bonus.
A regular app, easy to find. On macOS the app now has a Dock icon, so it can't get lost behind the notch any more.
Windows installer. ValhallISC-0.9.3-windows-x86_64-setup.exe installs per user without administrator rights. It adds a Start menu entry, an optional desktop icon and an uninstaller in Installed apps. The standalone executables are still available.
Source control. In namespaces under IRIS source control (for example git-source-control or CCR), checked-out classes and routines are marked:
Documents you can't edit are read-only. Check-out, check-in and commit stay in your usual tools; importing a file still goes through the server's source control hooks.
Profiles window, reviewed.
Harbor 1.1.0 adds IPM installation of the production frontend, bundled gateway dependencies and native extension. Node.js 22.12+ remains required; no npm or compiler is needed on the target host. Follow docs/HARBOR_IPM.md for installation, service setup and lifecycle operations.
The launcher requires explicit origin, cookie, instance and external data settings. It rejects relative or package-contained data locations, including symlinks. The extension installer refuses a route owned by another dispatch class or namespace. It creates no native accounts, credentials, grants or sample tasks. Package resources have application-specific names.
Validation: production build and 341 source tests plus two packaging tests. Isolated IRIS 2026.2/IPM 0.10.8 source and archive installations, native login and extension reads, retained records after uninstall/reinstall, conflicting-route refusal, desktop and 390px browser checks passed. External records remained byte-identical. Existing production data and earlier releases are unchanged.
IPM publication is requested through the existing Open Exchange application. Registry availability and bonus awards are separate from local package validation.
Waypoint 1.1.0 adds IPM installation of the production frontend, bundled gateway dependencies and native extension. Node.js 22.12+ remains required; no npm or compiler is needed on the target host. Follow docs/WAYPOINT_IPM.md for installation, service setup and lifecycle operations.
The launcher requires explicit origin, cookie, instance and external data settings. It rejects relative or package-contained data locations, including symlinks. The extension installer refuses a route owned by another dispatch class or namespace. It creates no native accounts, credentials, grants or sample tasks. Package resources have application-specific names.
Validation: production build and 257 source tests plus two packaging tests. Isolated IRIS 2026.2/IPM 0.10.8 source and archive installations, native login and extension reads, retained records after uninstall/reinstall, conflicting-route refusal, desktop and 390px browser checks passed. External records remained byte-identical. Existing production data and earlier releases are unchanged.
IPM publication is requested through the existing Open Exchange application. Registry availability and bonus awards are separate from local package validation.
Access Atlas can now be deployed through IPM with its compiled frontend, bundled gateway dependencies and native telemetry/log extension. Node.js 22.12+ remains a runtime requirement; npm and a build toolchain are not needed on the target host. Follow docs/IPM.md for installation, configuration and startup.
The launcher requires an explicit instance ID and an external campaign directory. Package uninstall preserves that directory. Installation refuses an existing /api/atlas route owned by a different class or namespace. No users, passwords, native grants or sample records are created by the package.
Validation: production build, 302 application tests and two packaging tests; clean Linux CI rebuild reproduces the committed payload. On isolated IRIS 2026.2/IPM 0.10.8: source and archive installs, native login and capture, telemetry/log reads, campaign save and reopening after uninstall/reinstall, route-conflict refusal, desktop and 390px layouts.
Download access-atlas-1.3.0.tgz for IPM archive loading or the ZIP for source/Docker installation. Community registry publication is requested through the existing Open Exchange application; registry availability and any contest bonus await the publishing process. Existing Docker deployments can remain on their current deployment method. Preserve instance ID and data volumes when upgrading.
Run creation now distinguishes 100 unarchived runs from 1,000 total records. Built-in plans and saved procedures explain when archiving can help and when it cannot. Storage limits, existing records and restoration obligations are unchanged.
Validation: production build and 257 tests passed, including refusal without native calls or writes and successful creation below both limits. The production frontend was checked at desktop and 390px widths using synthetic storage and the real creation guard.
Rebuild only the portal service, preserving the configured instance ID and existing run-data volume. No migration is required.
The interactive access example now follows a role reassignment through comparison and a downloadable training report. Removing SupportTeam leaves ReportingReader's read path visible, with an explicit owner follow-up instead of a claim that all access was revoked.
The new Review outcome view compares two supplied synthetic captures using the application’s graph and comparison functions. Add a reviewer note and export the remaining path, capture times and scope limitations. No IRIS connection, native change, live readback or saved campaign is simulated.
Historical technical-review documents now describe only this application's findings and verification.
Validation: production and example builds; 302 automated tests; 17 browser checks; manual 1280px and 390px layouts; downloaded training report checked. Existing connected workflows, storage and API behavior are unchanged.