Skip to content

v0.3.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 02 Aug 20:16
· 55 commits to main since this release
v0.3.0
This tag was signed with the committer’s verified signature.
CybotTM Sebastian Mendel
SSH Key Fingerprint: BsdGvKi3Med56Wy4VisZQhWin20c4hORHHUxNM9bVlw
Verified
Learn about vigilant mode.
10e76ea
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

A TYPO3 site assembled from site sets has no sys_template record, so the static TypoScript include this extension shipped never ran and the content element had no rendering definition — TYPO3 rendered its yellow "has no rendering definition" placeholder instead of the assistant. That is the configuration TYPO3 14 steers projects towards, and it is where this extension could not be used at all. 0.3.0 closes that, and fixes a defect it uncovered in the shipped system prompt.

Site set netresearch/browser-ai

Add it to the dependencies of your site package's set, or to the site's own config.yaml:

name: my-vendor/my-site
dependencies:
  - netresearch/browser-ai

TYPO3 12.4 is unaffected: the static template include is unchanged and remains the mechanism there.

Three settings, now editable per site

contextSelector, contextUsageLimit and systemPrompt are typed site settings, editable under Site Management › Sites › Settings and settable in a site's settings.yaml. The last two previously had no interface at all — they could only be reached through TypoScript constants.

Fixed: the system prompt arrived truncated

On a site loading the extension through the set, the shipped prompt reached the model as its first sentence only. The two that carry the grounding rule and the prompt-injection guard were dropped without any warning — the opposite of what the prompt exists to do.

TYPO3 hands site settings to TypoScript by serialising them into constants text, one key = value line per setting, so a value containing a newline breaks across lines and everything after the first is lost. No setting type avoids this, text included. The prompt is therefore one line now, and the setting is declared string rather than text so a multiline editing field does not invite an override that would be truncated the same way. If you override systemPrompt, keep it on one line.

Upgrading

No migration. On 13.4 and 14.3, add the set as shown above; a site still using sys_template needs no change at all.

Full changelog: https://github.com/netresearch/t3x-nr-browser-ai/blob/main/CHANGELOG.md

Assets 12
Loading