v0.25.0

You could already run agents. This release is about seeing them.

The agent runtime, at a glance

Until now, answering "what is the agent stack actually doing" meant opening runs one at a time. The dashboard now carries widgets that answer the recurring questions directly: how many runs are in each lifecycle state, how many are sitting suspended waiting for a human decision, why terminated runs ended, and what the provider pipeline's success rate and average latency look like over the last week.

None of this required new data — the widgets read what the runtime and the telemetry table were already recording, so they are populated the moment you upgrade, with your existing history behind them.

The widgets need typo3/cms-dashboard installed. They are also opt-in per backend user group: TYPO3 shows a widget only to users whose group has been granted it, so after upgrading, an administrator has to tick the ones a given group should see. Worth deciding deliberately — several of them report instance-wide cost and governance figures.

Governance decisions became something you can query

A guardrail verdict or a denied tool call used to be visible only on the run it happened in. If you wanted to know whether a particular tool was being blocked across the instance, or how often the secret-redaction guardrail was firing, there was nowhere to look.

Those decisions are now written to an append-only audit trail as they happen — guardrail verdicts, tool-gate denials, and blocks the provider itself returned. Three widgets read it: governance blocks over time, denials grouped by reason, and tool usage by name. The record is additive; nothing that was previously recorded stopped being recorded.

The new trail ages out with everything else

The audit trail is covered by the extension's retention model from the start, with its own purge command and its own retention category, so it does not grow without bound.

One caveat if you are upgrading straight to this version: the retention window for governance events was honoured by the purge but had no field in the Extension Configuration form, so it silently used the global window and could not be adjusted. That is fixed in 0.25.1 — if you want to set it explicitly, upgrade past this release.

Installation

composer require netresearch/nr-llm

Publication status

• TER: extensions.typo3.org/extension/nr_llm — 0.25.0 verified
• Packagist: packagist.org/packages/netresearch/nr-llm — 0.25.0 verified
• Documentation: docs.typo3.org/p/netresearch/nr-llm/0.25/en-us/ — render verified

Security

All release artifacts are signed with Sigstore keyless signing.

Verify signatures

cosign verify-blob \
  --bundle nr-llm-0.25.0.zip.sigstore.json \
  --certificate-identity-regexp "https://github.com/netresearch/.*" \
  --certificate-oidc-issuer "https://token.actions.githubusercontent.com" \
  nr-llm-0.25.0.zip

Verify checksums

sha256sum -c checksums.txt

Software Bill of Materials (SBOM)

SBOMs are provided in both SPDX and CycloneDX formats for supply chain transparency.